Skip to main content
POST
Upscale a video
The video counterpart of image upscaling: the video is enlarged, nothing about its content is directed. Returns on the same request, so expect it to be slow for anything long.

Authorizations

Authorization
string
header
required

API key in format: Bearer inf_***

Body

application/json
model
string
required

Slug of the upscale model to run, as listed by GET /v1/models. Must be an upscale-modality model that accepts a video input and is served by FAL; an image upscaler is rejected with 400 and directed to POST /v1/images/upscale.

video_url
string
required

Source video to upscale, as a URL or a data URI. Required.

Example:

"https://example.com/clip.mp4"

scale
number

Upscale factor. Forwarded onto whichever of the model's own input fields is named scale, upscale_factor or upscaling_factor; silently ignored by a model that declares none of them. Omit to use the model's own default.

Example:

2

Response

The upscaled video. data normally holds a single artifact.

created
integer
required

Unix timestamp, in seconds, of when the result was produced.

Example:

1713204900

data
object[]
required

One entry per produced artifact, in the order the provider returned them.

credits_used
number
required

Credits actually settled for this request (1 credit = $0.01). Settled against measured compute for per_second models, clamped to the amount reserved before the call, so it is never larger than the hold. May be fractional.

Example:

12.5