Upscale Images

January 2, 2026 (November 18, 2026)

Table of contents

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

Upscale a previously generated image to 2K or 4K resolution. This endpoint uses Google Flow’s native image upscaling capabilities.

Seeing “Upscaling failed” in Flow? Why Google Flow upscales fail and how to fix it.

Important:

  • 2k works on every plan, including free accounts.
  • 4k requires a Google AI Ultra subscription. Every other plan, free, Plus and Pro alike, is limited to 2k and a 4k request answers 400 with 4k upscaling is not available for this account. The request is refused before a reCAPTCHA token is solved, so it costs you nothing — raising captchaRetry will not change the outcome.
  • Both resolutions are free of Google Flow credits.

https://api.useapi.net/v1/google-flow/images/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

{
  "mediaGenerationId": "user:12345-email:6a6f...-image:CAMaJDMx...",
  "resolution": "2k"
}
  • mediaGenerationId is required. The mediaGenerationId from a previously generated image via POST /images.
  • resolution is optional. Target resolution for upscaling (default: 2k). Supported values: 2k, 4k.
  • captchaToken, captchaRetry, captchaOrder are optional, mutually exclusive captcha parameters. See Captcha Parameters for details.

Responses

  • 200 OK

    Image upscaled successfully. Returns base64-encoded image data.

    {
      "encodedImage": "/9j/4AAQSkZJRgABAQAAAQ...base64 encoded image data...",
      "media": {
        "name": "3c9d5e7a-...redacted...",
        "projectId": "9f63078c-...redacted...",
        "workflowId": "b0b8b280-...redacted...",
        "workflowStepId": "CAI",
        "mediaMetadata": {
          "createTime": "2026-11-15T22:35:07.248288Z",
          "mediaBlobSize": "3215872",
          "visibility": "PRIVATE"
        }
      },
      "captcha": {
        "service": "AntiCaptcha",
        "taskId": "618254930",
        "durationMs": 3500,
        "attempts": [
          {
            "service": "AntiCaptcha",
            "taskId": "618254930",
            "durationMs": 3500,
            "success": true
          }
        ]
      }
    }
    
  • 400 Bad Request

    Invalid request (missing or invalid mediaGenerationId), or 4k on an account without Google AI Ultra.

    {
      "error": "4k upscaling is not available for this account",
      "code": 400
    }
    
  • 401 Unauthorized

    Invalid API token.

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

    Google rejected the captcha on every try. We retry with a fresh captcha as many times as you allow (captchaRetry, default 5, or the providers in captchaOrder) and return this 403 only when all of them were rejected. The top-level error starts with captcha_quality:, for example "captcha_quality: PUBLIC_ERROR_UNUSUAL_ACTIVITY after 5 attempts. Google refused all 5 captcha tokens for user@example.com, so nothing was generated and no Google Flow credits were used (5 captcha solves were spent). Google is flagging this account's requests as unusual activity. If it keeps happening, use another account, or leave out email so the API picks one. See GET /accounts/captcha-stats summary.by_account". A 429 with PUBLIC_ERROR_UNUSUAL_ACTIVITY_TOO_MUCH_TRAFFIC reads the same way.

    Two 403s are not a captcha problem, and we answer them after one try instead of retrying. PUBLIC_ERROR_MODEL_ACCESS_DENIED in the response means Google refused the model on that account, so raising captchaRetry or adding providers will not help. Check that the account’s plan includes the model. Since 2026-09-23 Google no longer offers veo-3.1-lite-low-priority to invited members of an Ultra $199 family plan — only the family manager’s account keeps it.

    PUBLIC_ERROR_USER_MINOR means Google treats the Google account as belonging to someone under 18, and Google Flow is not available to such accounts. The error says so in plain words. No captcha or retry changes it: use another Google account, or have this one’s age verified with Google first. With email omitted, the load balancer sets such an account aside for 1 hour, then tries it again.

    Nothing was created when this happens. Google checks the captcha before it starts generating, so no Google credits were used and you can resubmit straight away. Your captcha provider still bills each solve.

    The usual cause is the Google account, not the captcha provider. Google gives each account its own trust level. On a trusted account it accepts about 9 in 10 captchas, on a distrusted one about 3 in 10, whichever provider solved them. Most customers have a few distrusted accounts among many good ones.

    To see which accounts are affected, use GET /accounts/captcha-stats. Its summary.by_account shows, for each of your Google accounts, how many captchas were tried and what share Google accepted. GET account/stats with bot=google-flow also shows how many requests each account finished with each response code.

    • If one or a few accounts are far below the others, the API already sends them less work: when you leave out email, each captcha Google rejected on an account in the last 15 minutes lowers its chance of being picked, for generations and for image uploads. They still get some work, so an account that recovers gets its full share back. If you pin requests with email, move them to your other accounts yourself. Replace an account that stays low for more than a day or two.
    • If all your accounts drop at the same time, it’s the captcha provider. Configure at least two providers with POST /accounts/captcha-providers, and the API will start with whichever one Google accepts best.

    A higher captchaRetry gets more requests through on a distrusted account, but every extra try is another paid solve.

  • 404 Not Found

    Account not found or image not found.

    {
      "error": "Google Flow account john@gmail.com not found",
      "code": 404
    }
    
  • 429 Too Many Requests

    Google returns several RESOURCE_EXHAUSTED 429 variants. Check the reason field and respond accordingly:

    Reason Meaning Scope What to do Cooldown
    PUBLIC_ERROR_
    USER_REQUESTS_THROTTLED
    Google is throttling the account (the token was fine). Uploads and generation are metered separately All models on the account — or uploads only, when POST /assets triggered it Run fewer parallel requests, or switch accounts. From POST /assets, retrying the same one rarely clears it ~30 min. From POST /assets, treat it as a minimum — it can persist
    PUBLIC_ERROR_
    USER_QUOTA_REACHED
    Account’s overall Flow quota cap All models on the account Add accounts, or omit email to load-balance ~30 min
    PUBLIC_ERROR_
    PER_MODEL_DAILY_QUOTA_REACHED
    Per-model daily quota Only that model, on that account Switch model, or wait Next UTC midnight
    PUBLIC_ERROR_
    UNUSUAL_ACTIVITY_TOO_MUCH_TRAFFIC
    Google rejected the captcha on every try (we already retried). Usually a distrusted Google account, sometimes the provider Per request Check which accounts are affected in captcha-stats. Rest or replace those accounts. Add a second provider if all accounts drop together 60s

    Every 429 returns the cooldown two ways — an HTTP Retry-After: <seconds> header and a body retryAfter: <ISO timestamp> field. Honor it before retrying.

    When email is omitted, the first three reasons quarantine the account and the load balancer routes around it. If every account is quarantined for the model you get 429 with error: "no_eligible_account". Routing details: GET /jobs › Load Balancing Algorithm.

    Captcha-quality failures prefix the top-level error with captcha_quality: (e.g. "captcha_quality: PUBLIC_ERROR_UNUSUAL_ACTIVITY_TOO_MUCH_TRAFFIC after 3 attempts") so you can detect them without parsing the nested body.

  • 503 Service Unavailable

    503 has two distinct causes — check the response body to tell them apart.

    A transient Google-side outage. Wait 5-10 seconds and retry.

    {
      "error": {
        "code": 503,
        "message": "Service temporarily unavailable.",
        "status": "UNAVAILABLE"
      }
    }
    

    A captcha-provider failure — the top-level error is prefixed Captcha service failed:. The problem is your captcha provider (check its API key and balance), not Google. Don’t retry until the provider is back.

    {
      "error": "Captcha service failed: ERROR_ZERO_BALANCE",
      "code": 503
    }
    

    Google can also fail an upscale with its own server error and no reason, most often on 4K upscales sent in large batches. Nothing was made and no Google Flow credits were used. Retry later, or upscale to 2K.

    {
      "error": "Google could not upscale this image right now (its server error, HTTP 500, gave no reason): nothing was made and no Google Flow credits were used. Retry later, or upscale to 2K",
      "code": 503
    }
    

Model

The upscaled image as Base64 JPEG data, Google’s record of it and the captcha used.

The upscaled image, field by field, and the type it uses (FlowCaptcha)
  • encodedImage - Base64-encoded upscaled image data (JPEG format)
  • media - Google’s record of the upscaled image (left out when it could not be read)
  • captcha - Captcha metadata for debugging/research
  • captcha.service - Provider that returned the successful token
  • captcha.taskId - Task ID from the captcha service
  • captcha.durationMs - Total time for all captcha attempts
  • captcha.attempts - Array of all captcha attempts (including failures)
{
  encodedImage: string                // Base64-encoded image (decode and save as .jpg)
  media?: {                           // Google's record of the upscaled image (left out when it could not be read)
    name: string                      // Google's media id of the upscaled image
    projectId: string                 // the Google Flow project the image is in
    workflowId?: string               // the Google Flow workflow (project item) that holds the image
    workflowStepId?: string           // the workflow step
    mediaMetadata: {                  // Google's record of the file
      createTime?: string             // ISO 8601 time Google created the upscale
      mediaBlobSize?: string          // the file's size in bytes, as a string
      visibility?: string             // "PRIVATE"
    }
  }
  captcha: FlowCaptcha                // the captcha solved for this request (described below)
}

When the request fails:

{
  error: string                       // what went wrong, e.g. "PUBLIC_ERROR_USER_QUOTA_REACHED (HTTP 429)"
  code: number                        // the HTTP status
  retryAfter?: string                 // ISO 8601 time to retry after, on a 429 (the Retry-After header carries the same in seconds)
  response?: {                        // Google's answer, when Google or the captcha refused the request
    error?: {                         // Google's error
      code: number                    // HTTP status Google answered
      message: string                 // the error message, e.g. "flow.google.com SPrCad failed"
      status: string                  // Google's status name, e.g. "RESOURCE_EXHAUSTED"
      details: Array<{                // Google's error details
        '@type': string               // the type name of the detail
        reason: string                // Google's reason code, e.g. "PUBLIC_ERROR_USER_QUOTA_REACHED"
      }>
    }
    captcha: FlowCaptcha              // the captcha tried or used
  }
}

The type used above:

FlowCaptcha: the captcha in the answer above.

{
  service?: string                           // the provider whose token Google accepted: `CapSolver`, `AntiCaptcha`,
                                             // `YesCaptcha`, `CapMonster`, `SolveCaptcha`, `2Captcha`, `EzCaptcha` or
                                             // `UserProvided`. Always on a success answer
  taskId?: string                            // that provider's task id (none for `UserProvided`)
  durationMs?: number                        // ms from the first solve to the token used. Always on a success answer
  error?: string                             // why no captcha token could be had, on a failed request
  attempts: Array<{                          // every solve tried, in order, failed ones included
    service: string                          // the provider asked
    taskId?: string                          // that provider's task id
    durationMs: number                       // how long this solve took, in ms
    success: boolean                         // true when the provider returned a token (Google may still have refused it)
    error?: string                           // why the solve failed
    userAgent?: string                       // the browser user agent the provider solved with, when it reports one
    secChUa?: string                         // the Sec-CH-UA value the provider solved with, when it reports one (may be empty)
    cost?: string                            // the provider's price for this solve, as the provider reports it
    ip?: string                              // the IP address the provider reports for this solve
    createTime?: number                      // Unix time the provider started the solve, as it reports it
    endTime?: number                         // Unix time the provider finished the solve, as it reports it
    solveCount?: number                      // the provider's own solve counter for this task
  }>
}

Examples

  • # First generate an image
    curl -X POST \
         -H "Authorization: Bearer YOUR_API_TOKEN" \
         -H "Content-Type: application/json" \
         -d '{"prompt": "A beautiful sunset over mountains"}' \
         "https://api.useapi.net/v1/google-flow/images" > generate.json
    
    # Extract mediaGenerationId from the response
    MEDIA_ID=$(jq -r '.media[0].image.generatedImage.mediaGenerationId' generate.json)
    
    # Upscale the image to 2K
    curl -X POST \
         -H "Authorization: Bearer YOUR_API_TOKEN" \
         -H "Content-Type: application/json" \
         -d "{\"mediaGenerationId\": \"$MEDIA_ID\", \"resolution\": \"2k\"}" \
         "https://api.useapi.net/v1/google-flow/images/upscale" > upscale.json
    
    # Decode base64 and save as image
    jq -r '.encodedImage' upscale.json | base64 -d > upscaled_image.jpg
    
  • const token = 'YOUR_API_TOKEN';
    
    // First generate an image
    const generateResponse = await fetch('https://api.useapi.net/v1/google-flow/images', {
      method: 'POST',
      headers: {
        'Authorization': `Bearer ${token}`,
        'Content-Type': 'application/json'
      },
      body: JSON.stringify({
        prompt: 'A beautiful sunset over mountains'
      })
    });
    
    const generated = await generateResponse.json();
    const mediaGenerationId = generated.media[0].image.generatedImage.mediaGenerationId;
    
    // Upscale the image
    const upscaleResponse = await fetch('https://api.useapi.net/v1/google-flow/images/upscale', {
      method: 'POST',
      headers: {
        'Authorization': `Bearer ${token}`,
        'Content-Type': 'application/json'
      },
      body: JSON.stringify({
        mediaGenerationId,
        resolution: '2k'
      })
    });
    
    const upscaled = await upscaleResponse.json();
    
    // Decode base64 and save
    const buffer = Buffer.from(upscaled.encodedImage, 'base64');
    require('fs').writeFileSync('upscaled_image.jpg', buffer);
    console.log('Upscaled image saved!');
    
  • import requests
    import base64
    
    token = 'YOUR_API_TOKEN'
    headers = {
        'Authorization': f'Bearer {token}',
        'Content-Type': 'application/json'
    }
    
    # First generate an image
    generate_response = requests.post(
        'https://api.useapi.net/v1/google-flow/images',
        headers=headers,
        json={'prompt': 'A beautiful sunset over mountains'}
    )
    generated = generate_response.json()
    media_generation_id = generated['media'][0]['image']['generatedImage']['mediaGenerationId']
    
    # Upscale the image
    upscale_response = requests.post(
        'https://api.useapi.net/v1/google-flow/images/upscale',
        headers=headers,
        json={
            'mediaGenerationId': media_generation_id,
            'resolution': '2k'
        }
    )
    upscaled = upscale_response.json()
    
    # Decode base64 and save
    image_data = base64.b64decode(upscaled['encodedImage'])
    with open('upscaled_image.jpg', 'wb') as f:
        f.write(image_data)
    print('Upscaled image saved!')
    

Try It