Upscale a video to 1080p

October 7, 2026 (October 22, 2026)

Table of contents

  1. Request Headers
  2. Request Body
  3. Responses
  4. Model
  5. Examples
  6. Try It

Turn a 720p clip made by this API into 1080p: 1280×720 becomes 1920×1080 and 720×1280 becomes 1080×1920. The clip keeps its length and aspect ratio, and the result has a new mediaId. The job runs on the account that made the clip.

The source is a video mediaId from POST /videos, POST /videos/extend or POST /videos/edit. A clip that is already 1080p is refused with 400.

To take the visible Gemini ✦ off the result (see Watermark), use our watermark remover. It works when the source is a clip as made by POST /videos, not when the source was extended or edited.

Cost

An upscale uses the clip’s full length in seconds again from the account’s monthly Vids video allowance: upscaling an 8-second clip uses 8 seconds. Upscale works on clips of up to 20 seconds, the same limit as the Vids editor. A 20-second clip came back fine. Our 30-second clip came back with its frames out of order, three times out of three, so the API refuses clips longer than 20 seconds with 400 before anything is charged. For a longer 1080p clip, make and extend it at 1080p.

Upscale once, at the end: if the finished clip is 20 seconds or less, make, extend and edit it at 720p, then upscale it.

In our tests a 1080p clip behaves like a 720p clip that was upscaled, and it takes about twice as long to make. When you extend or edit a 1080p clip, Google seems to work on a 720p copy and then upscale the result again. Each round makes faces and small details softer. So:

  • Make, extend and edit your clips at 720p.
  • When the clip is finished, upscale it once with POST /videos/upscale. Upscale takes clips of up to 20 seconds.
  • Pick 1080p from the start for a single clip that you won’t extend or edit. A clip longer than 20 seconds can’t be upscaled, so for a long 1080p clip, extend at 720p and set resolution: "1080p" on the last extend only, or extend at 1080p throughout and accept softer faces.

Sync, async and webhooks

  • Every generation runs as a job on our side, with up to 5 minutes for Google’s answer, so a slow answer is never lost.
  • Sync (the default): the POST waits for the job and answers 200 with the finished job record, or the job’s error code. A video usually takes 20 to 100 seconds, an image about 10. If the job is still running after about 100 seconds, the POST answers 202 with the job as it stands: fetch the result with GET /jobs/jobid. Always check status: only completed has a result.
  • Async: pass async: true. The POST answers 202 at once with the job in status: "processing". Poll GET /jobs/jobid or wait for the webhook.
  • replyUrl receives one POST of the final job record, as JSON, when the job completes or fails, for sync and async requests alike. It does not make a request async.
  • Each account runs at most maxJobs jobs at a time (default 3, range 1 to 10, set with POST /accounts). GET /jobs shows what is running. Job records are kept for 7 days.

https://api.useapi.net/v1/google-vids/videos/upscale

Request Headers 
Authorization: Bearer {API token}
Content-Type: application/json
# Alternatively you can use multipart/form-data
# Content-Type: multipart/form-data
Request Body 
{
  "mediaId": "user:[email protected]:eyJ1IjoiaHR0…",
  "async": true,
  "replyUrl": "https://your-domain.com/webhook",
  "replyRef": "boat-1080p"
}
  • mediaId is required, the video mediaId of a 720p clip of up to 20 seconds, from a finished job’s result.
  • async is optional, true to answer 202 at once and run the job in the background. Default: false.
  • replyUrl is optional, a public http(s) URL that receives one POST of the job record when the job completes or fails. It works with sync and async requests.
    Callback body has the same JSON shape as GET /jobs/jobid response.
    Maximum length: 1024 characters.
  • replyRef is optional, your own reference echoed back in the job record.
    Maximum length: 1024 characters.
Responses

  • 200 OK — sync mode, a 3-second 720p clip upscaled to 1080p, charged 3 seconds.

    {
  "jobid": "j1007101456724115154v-u12345-email:[email protected]:google-vids",
  "type": "video",
  "mode": "upscale",
  "email": "[email protected]",
  "status": "completed",
  "created": "2026-10-07T06:27:55.554Z",
  "request": {
    "mediaId": "user:[email protected]:eyJ1IjoiaHR0…"
  },
  "updated": "2026-10-07T06:28:19.945Z",
  "completed": "2026-10-07T06:28:19.945Z",
  "result": {
    "mediaId": "user:[email protected]:eyJ1IjoiaHR0…",
    "width": 1920,
    "height": 1080,
    "duration": 3,
    "resolution": "1080p",
    "aspectRatio": "landscape",
    "model": "/flix/upsample_video/v1",
    "quota": {
      "video": {
        "limit": 10000,
        "left": 9624,
        "resetAt": "2026-11-01T07:00:00.000Z"
      }
    },
    "elapsedMs": 24339
  }
}

  • 202 Accepted — the job is running: with async: true at once, in sync mode after about 100 seconds of waiting. Fetch the result with GET /jobs/jobid (or wait for the webhook).

  • 400 Bad Request — mediaId is missing or invalid, the clip is already 1080p, or it is longer than 20 seconds.

    {
  "error": "This clip is already 1080p",
  "code": 400
}

    {
  "error": "Parameter mediaId is required",
  "code": 400
}

  • 401 Unauthorized

    Invalid API token.

    {
  "error": "useapi.net ⁝ Unauthorized",
  "code": 401
}

  • 403 Forbidden — the mediaId was issued to a different API token, or the account has Google Workspace smart features turned off.

    {
  "error": "video id does not belong to this API token",
  "code": 403
}

  • 404 Not Found — the account that made the clip is no longer connected.

    {
  "error": "Account [email protected] (from the video id) is not configured",
  "code": 404
}

  • 429 Too Many Requests — the account is running maxJobs jobs, the month’s video allowance is used up, or Google is limiting the account for a minute.

    {
  "error": "Account [email protected] is running 3 of 3 jobs (maxJobs). Wait for one to finish, or raise maxJobs with POST /accounts",
  "code": 429
}

    Once Google refuses a job because the account’s monthly video allowance is used up, the API keeps Google’s reset time on the account (exhaustedUntil in GET /accounts) and gives it no video jobs until then. A request that must run on that account is answered at once with 429, with no job created and no call to Google. retryAt is when to try again. If the account’s plan changed, GET /accounts/email reads its allowance again and lets it take jobs right away.

    {
  "error": "Account [email protected] has used up this month's Google Vids video allowance. It resets at 2026-11-01T07:00:00.000Z. If its plan changed, call GET /accounts/[email protected] to refresh it",
  "code": 429,
  "retryAt": "2026-11-01T07:00:00.000Z"
}

    A job that Google itself refuses for its allowance (the first refusal, or a job that needs more than the account has left) fails with error.code 429, error.retryAt set to the reset time, and error.quota with what was left (limit, left, resetAt). An account with some allowance left still takes smaller jobs.

  • 504 Gateway Timeout — Google did not answer within 5 minutes: run it again.

  • 596 Account Error

    Google reported the account as signed out. While we re-check it, the answer is the first message below. Retry in about a minute. If it stays signed out, the account is paused, you receive an email, and the answer becomes the second message until you re-add it via Setup Google Vids.

    {
  "error": "Google reported this account as signed out. We are re-checking it — please retry in about a minute. If it stays signed out, you will receive a re-add email.",
  "code": 596
}

    {
  "error": "Account [email protected]: Google signed this account out. Re-add it at https://useapi.net/docs/start-here/setup-google-vids",
  "code": 596
}
Model

The job record, mode: "upscale". GET /jobs/jobid and the replyUrl webhook return the same shape.

{ // TypeScript, all fields are optional
  jobid: string                  // j<time><random><v|i>-u<id>-email:<email>-bot:google-vids
  type: 'video' | 'image'
  mode?: 'text' | 'image' | 'ingredients' | 'extend' | 'upscale' | 'edit'   // video jobs only
  email: string                  // the account the job runs on
  status: 'processing' | 'completed' | 'failed'
  created: string                // ISO 8601, when the job was accepted
  updated?: string               // ISO 8601, the last status change
  completed?: string             // ISO 8601, when the job completed or failed
  request: Record<string, unknown>   // your request body as sent (ids as strings)
  replyUrl?: string
  replyRef?: string
  error?: {                      // status 'failed'
    code: number                 // 400 | 403 | 404 | 422 | 429 | 500 | 502 | 503 | 504 | 596, see GET /jobs/{jobid}
    message: string
    retryAt?: string             // code 429: ISO 8601, when to try again
    quota?: {                    // code 429 for allowance: Google's counter for this kind of job when it refused it
      limit: number              // monthly limit (seconds of video, or images)
      left: number               // what was left, 0 when used up
      resetAt: string            // ISO 8601, when the allowance resets
    }
  }
  result?: {                     // status 'completed'
    mediaId: string              // download it with GET /media/{mediaId}. A video: extend / upscale / edit it. An image: use it as startImage, referenceImage_N or avatar image
    width: number
    height: number
    duration?: number            // video: length of the whole clip in seconds
    resolution?: '720p' | '1080p'              // video
    aspectRatio?: 'landscape' | 'portrait'     // video
    model: string | null         // Google's backend path, e.g. /flix/generate_videos_omni_t2v_psq/v1
    quota: {                     // what the account has left after this job
      video?: { limit: number, left: number, resetAt: string }   // seconds, video jobs
      image?: { limit: number, left: number, resetAt: string }   // images, image jobs
    }
    elapsedMs: number            // how long Google took
  }
}
Examples 
  • curl -X POST "https://api.useapi.net/v1/google-vids/videos/upscale" \
   -H "Content-Type: application/json" \
   -H "Authorization: Bearer …" \
   -d '{
     "mediaId": "user:[email protected]:eyJ1IjoiaHR0…"
   }'

  • const token = "API token";
const mediaId = "mediaId of a 720p clip made by this API";
const apiUrl = "https://api.useapi.net/v1/google-vids/videos/upscale";
const response = await fetch(apiUrl, {
  method: "POST",
  headers: {
    "Content-Type": "application/json",
    "Authorization": `Bearer ${token}`,
  },
  body: JSON.stringify({ mediaId })
});
const job = await response.json();
console.log("response", response.status, job.result ?? job.error ?? job);

  • import requests
token = "API token"
mediaId = "mediaId of a 720p clip made by this API"
apiUrl = "https://api.useapi.net/v1/google-vids/videos/upscale"
headers = {
    "Content-Type": "application/json",
    "Authorization" : f"Bearer {token}"
}
response = requests.post(apiUrl, headers=headers, json={"mediaId": mediaId})
print(response, response.json())
Try It