Veo 3.1 4K needs an 8-second clip; Sume's Veo rows stop at 720p

Google's Veo 3.1 gives 1080p and 4K only at 8 seconds, and Veo 3.1 Lite has no 4K at all (read 2026-10-10). Sume's Veo rows are fixed at 720p, so no Veo resolution above 720p is available through Sume.

If you want 4K from Sume, the row that lists it is gemini-omni-flash-1.1, which accepts 360p, 720p, 1080p and 4K.

Google's resolution and duration rules

The Gemini API Veo page (read 2026-10-10) lists durations of 4, 6 and 8 seconds, 720p by default, and 1080p and 4K only at 8 seconds. Aspect ratios are 16:9 and 9:16. Latency is 11 seconds to 6 minutes. The output carries a SynthID watermark.

So a 4-second Veo clip at Google is always 720p.

What Sume's Veo rows do

Sume's Veo request builder accepts only 720p. Durations are 4, 6 and 8 seconds, with 16:9 or 9:16. The audio flag defaults to on. Billing is Google list times 1.25, so an 8-second 720p clip with audio bills $4.00 on veo-3.1, $1.00 on veo-3.1-fast and $0.50 on veo-3.1-lite.

These rows appear only when the environment switch is on and GET /v1/videos/models returns the id. Check the catalog before you commit.

Shorter clips cost proportionally less because the rate is per second. At the same 720p with audio, a 4-second clip bills $2.00 on veo-3.1, $0.50 on veo-3.1-fast and $0.25 on veo-3.1-lite, and a 6-second clip bills $3.00, $0.75 and $0.375. Turning audio off lowers the rate to $0.25, $0.10 and $0.0375 per second. Because the output is 720p at every length, the price is the only thing that changes between 4, 6 and 8 seconds, not the pixel count.

Rows on Sume that reach higher resolutions

Per the Video Generation docs, Gemini Omni Flash 1.1 goes to 4K for 3 to 10 seconds. At 4K, Sume bills $0.375 per second (list $0.30 times 1.25), so an 8-second 4K clip bills $3.00. Seedance 2.5, Wan 3.0 and Seedance 2 reach 1080p, and MiniMax H3 bills 2K and 4K upscales if the request includes them.

The table fixes the length at 8 seconds and the resolution at each row's highest. Prices are Sume billed rates, list times 1.25. Seedance 2.5 is the expensive end because it bills by video tokens, so its 1080p second costs far more than Wan's. Veo is shown at 720p because that is all Sume's rows run, and it appears only if your catalog lists it.

Reading the catalog and choosing

The supported_resolutions field in GET /v1/videos/models is the only dependable source. Send a resolution that is in that list for the row, or the request fails validation. Do not assume that a resolution Google supports at 8 seconds exists on Sume, because the Veo builder in the API code accepts 720p and nothing else.

For 1080p at Veo's 8-second length, Wan 3.0 is the inexpensive stand-in on Sume. For a 4K master, Omni is the only listed row. For the Veo look itself, and for any Veo output above 720p, use Google directly.

One more point on length: Google ties its higher resolutions to the 8-second setting, so a short 4-second Veo test tells you nothing about 1080p or 4K quality. On Sume, Omni accepts 4K at any length from 3 to 10 seconds, so you can test a 3-second 4K clip for $1.125 before you commit to a longer one.