Output tokens in a 3 to 10 second Omni clip: 17,376 to 57,920

A 3-second Gemini Omni Flash clip at 720p is 17,376 output tokens and a 10-second clip is 57,920, because Google's pricing page says billing is based on output tokens at 5,792 tokens per second of 720p video. At Google's $17.50 per million output tokens that is $0.30 for 3 seconds and $1.01 for 10 seconds. On Sume the same lengths cost $0.375 and $1.25 at 720p, because Sume bills a flat rate per output second instead of counting tokens.

Why the token view is useful

If you read Google's usage metadata, you see tokens, not seconds. Multiplying seconds by 5,792 lets you predict a bill before a job runs and check it after. The same multiplication is how you spot a clip that came back longer or shorter than you requested. Sume's 3 to 10 second window for Omni is the same range Google's docs give for the 3 to 10 second continuations when you extend a video, so the table below covers every length you can submit as one job on Sume.

The table

Each row multiplies the length by 5,792 tokens, then by $17.50 per million tokens for the Google column. The Sume column is the length times $0.125, which is Sume's 720p rate (the $0.10 provider list times 1.25).

What the table does not cover

The 5,792 figure is stated for 720p only. Google's Omni page lists 360p, 1080p and 4K outputs as well, and describes 1080p and 4K as upscaled, but its pricing page gives no token count for those, so this post does not extend the token column past 720p. For other resolutions use the Sume rates directly: $0.0375, $0.1875 and $0.375 per second at 360p, 1080p and 4K.

Google's pricing page also lists an input price of $1.50 per million tokens for text, image, video and audio input. Sume's docs describe its Omni billing as the provider list times 1.25 for each output second, so the billed quantity on Sume is output seconds.

Using the table for a budget

Suppose a campaign needs 40 clips of 6 seconds. Google's column gives $0.6082 a clip, so 40 clips is $24.33. Sume's column gives $0.75 a clip, so 40 clips is $30.00. The difference of $5.67 is the cost of a flat per-second rate, a single workspace balance, and a model id that stays callable after Google's preview ids end. If the campaign is only drafts, the 360p rate of $0.0375 a second brings the same 40 clips to $9.00.

A quick check in code terms

To confirm any row, take the length in seconds, multiply by 5,792, divide by 1,000,000 and multiply by 17.50. For 7 seconds that is 40,544 tokens, 0.040544 million, and $0.7095. Round at the end, not at each step, or a 100-clip batch drifts by a few cents.

On Sume, skip the token step: read usage.cost from the completed poll response and compare it with length x rate. If they differ, the job produced a different length than you asked for.