Flow 4K costs 50 credits and needs Ultra; Sume lists 4K per second

In Google Flow, 1080p upscaling of Gemini Omni Flash clips is free for Google AI Plus, Pro and Ultra subscribers, while 4K upscaling costs 50 credits and is limited to Ultra. On Sume there is no plan gate on resolution: gemini-omni-flash-1.1 accepts resolution: "4K" and bills $0.375 a second, so an 8-second 4K clip is $3.00.

Flow's rules are from the credits page, the resolution list from the Omni Flash API page, and the API rates from Google's pricing page, all read 2026-10-02.

What does Google say about Omni 1080p and 4K?

The Omni Flash API page lists 360p, 720p (the default), 1080p and 4K, and describes 1080p and 4K as upscaled output. Clips run 3 to 10 seconds, in 16:9 (default) or 9:16. So the higher resolutions are a post-step on a generated clip, not a different native render, and that is the reason Flow can price them separately from generation.

Google's pricing page puts 720p video at about $0.10 a second. I could not confirm a published 1080p or 4K per-second API rate on the pages I fetched, so none is quoted for Google here.

What does Sume charge by resolution?

Sume lists the same four resolutions. Rates are provider list times 1.25 per output second, and the catalog's pricing_skus field is the source of truth. The figures below are the catalog rates at the time of writing.

When does the Flow plan gate matter?

If you are on Plus or Pro, 4K in Flow is simply not on the menu per the credits page. A team that needs 4K masters for a store listing or a broadcast slot can still get them from Sume by sending resolution: "4K", at a visible dollar price. If you are on Ultra, 50 credits per 4K upscale may be cheap for the occasional hero clip; whether it beats $3.00 depends on what your credits cost, which is plan-specific.

Check the aspect ratio too. Omni Flash does only 16:9 and 9:16, and our 4K clip length post walks through what the 4K tier does to length.

How do I request 4K from Sume?

Pass the catalog token 4K in uppercase. The call reserves the cost before generation starts, so a balance that cannot cover $3.00 fails fast with 402 insufficient_credits instead of failing partway.

curl -X POST https://api.sume.com/v1/video-router/generate \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: omni-4k-001" \
  -d '{
    "model": "gemini-omni-flash-1.1",
    "prompt": "Slow orbit around a sneaker on a white plinth, studio light",
    "duration": 8,
    "resolution": "4K",
    "aspect_ratio": "16:9",
    "mode": "async"
  }'

How do the clip lengths line up?

Google lists Omni Flash clips at 3 to 10 seconds, with extension adding 3 to 10 seconds at a time up to a 40-second total. Sume's Video Router lists the same 3 to 10 seconds for the model and has no extend call, so a longer 4K piece on Sume is several separate clips joined in an edit, each billed at the 4K rate.

At $0.375 a second that is $15.00 for a 40-second 4K sequence on Sume. On Flow, extension and the 4K upscale are separate credit lines on the credits page, and the page I read does not combine them into one price, so no Flow total is quoted here.

What should you not assume?

Do not assume a 4K clip has more detail than a 1080p one for every shot, since Google calls both upscaled. Preview at 720p first, then rerun the chosen prompt at 4K, and read the rates from the catalog rather than from this table if the date has moved on.