1,000 seconds of Omni Flash: Google about $101, Sume $37.50 to $375

1,000 seconds of Gemini Omni Flash video costs about $101.36 at Google's published 720p rate, and between $37.50 and $375.00 on Sume depending on the resolution you pick. The Google figure is arithmetic on the pricing page: Google bills output tokens at $17.50 per million and says a second of 720p video is 5,792 tokens, so 1,000 seconds is 5,792,000 tokens, and 5.792 million tokens times $17.50 is $101.36. Sume bills per output second instead of per token.

Google's side: tokens, then dollars

Google's pricing page states the conversion only for 720p, where it calls the effective price approximately $0.10 per second. It does not publish a token count for 360p, 1080p or 4K, so those cells below are left to the Sume rows rather than guessed for Google.

• Output video rate: $17.50 per 1 million tokens (Google pricing page, read 2026-10-08).
• 720p conversion: 5,792 tokens per second of video.
• 1,000 s x 5,792 = 5,792,000 tokens; 5.792 x $17.50 = $101.36.

Sume's side: four rates

Sume's docs say it bills the provider list times 1.25 for each output second, as a function of resolution. The provider list in Sume's price table is $0.03, $0.10, $0.15 and $0.30 a second at 360p, 720p, 1080p and 4K, so the Sume rates are $0.0375, $0.125, $0.1875 and $0.375.

Reading the gap

At 720p the Sume figure is $125.00 against about $101.36 at Google's list, a difference of $23.64 per 1,000 seconds. Sume bills 25 percent over the provider list, and the provider list in Sume's price table is $0.10 a second, slightly under Google's token arithmetic. What Sume adds is one workspace balance, one API shape shared with the other video models, and job records you can read with GET /v1/usage.

Resolution moves the Sume price more than the vendor choice does. The same thousand seconds at 360p is $37.50, a third of the 720p figure, and 4K is three times it. If you are drafting, draft at 360p.

A worked split

Most real budgets are not a single resolution. Say 600 of the 1,000 seconds are 360p drafts and 400 are 1080p finals. The drafts cost 600 x $0.0375 = $22.50, the finals cost 400 x $0.1875 = $75.00, and the total is $97.50 on Sume. That is below the $101.36 Google figure for 1,000 seconds at 720p, because a draft-and-final plan never pays the middle price for the whole thousand seconds.

The comparison is not apples to apples, since Google's page gives the token conversion only for 720p. It still shows the practical point: the rate card matters less than how many seconds you render at the expensive rung.

Before you budget

Per-clip length is capped at 10 seconds on Sume, so 1,000 seconds is at least 100 jobs. Each job reserves its price at submit and the poll response reports usage.cost, so sum that field across a batch instead of trusting the table. Both vendors can change prices; re-read the Google page and the Sume catalog before committing a quarter's budget.