Gemini Omni Flash 1.1 4K video price: $3.75 for a 10-second clip

A 10-second 4K clip from gemini-omni-flash-1.1 costs $3.75 on Sume; the same clip at 720p is $1.25 and at 360p $0.38. Omni is the one model in the Video Router with 360p to 4K tiers, with clips of 3 to 10 seconds.

Price per tier

The provider list price is $0.03 per second at 360p, $0.10 at 720p, $0.15 at 1080p and $0.30 at 4K. Sume adds its 1.25 margin and rounds each job up to the cent.

Picking a tier

The 360p tier is exactly 30 percent of the 720p price, which makes it a cheap way to check motion and framing before you commit. 4K costs three times 720p, so use it only for the clip you will ship.

Audio is included at every tier, see the audio post.

Longer than 10 seconds

Omni's cap is 10 seconds per clip. A 40-second 4K sequence is four jobs, $15.00 in total, before any edit pass. The Video Router docs describe the model's modes, and the video models docs list its limits.

For 4K at lower cost per clip, compare the other 4K option.

• Draft at 360p, final at the tier you ship.
• Round-ups explain the odd cents.
• One job is at most 10 seconds.

A cost-aware workflow

A sensible Omni workflow is three passes. Draft the idea at 360p for about 38 cents per 10 seconds, check the motion at 720p for $1.25, then render the keeper at 4K for $3.75. Total for one approved 10-second clip is $5.38 if you draft once and check once, which is less than a single 30-second Seedance 2.5 clip at 720p.

If a clip is rejected at 720p, you have spent only the draft and the check, not the 4K price. The reverse mistake is costly: rendering at 4K first and iterating there costs three times as much per attempt. Prices here exclude any edit or timeline steps you run afterwards.

How these numbers were produced

The figures are Sume's billed-amount estimates for gemini-omni-flash-1.1 on 2026-10-06, at 360p, 720p, 1080p and 4K for 3, 8 and 10 seconds. The tables show whole cents.

These are estimates of the billed amount for the stated settings. Anything not in the table, such as a different frame shape, a reference input or a changed quality tier, can change the number, so run the estimate for your own request before a large batch. Where this page and the public API pricing list disagree, the pricing page and the live quote win.