Veo 3.1 price as a multiple of Sume's Omni rate: 3.2x, 0.8x, 0.4x
At 720p Veo 3.1 Standard is 3.2x Sume's Omni rate, Fast is 0.8x and Lite 0.4x. The ratios at 1080p and 4K are in one table, with the Oct 22 caveat.

At 720p, Google's Veo 3.1 Standard list price of $0.40 per second is 3.2 times Sume's Gemini Omni Flash rate of $0.125, Veo 3.1 Fast at $0.10 is 0.8 times it, and Veo 3.1 Lite at $0.05 is 0.4 times it. Ratios let you rank the options without re-doing arithmetic each time a price moves. All three Veo preview ids also shut down on October 22, 2026, so the ratios describe the next two weeks, not a long-term choice.
Where the inputs come from
Google's pricing page lists Veo 3.1 Standard at $0.40 (720p and 1080p) and $0.60 (4K) per second, Fast at $0.10 (720p), $0.12 (1080p) and $0.30 (4K), and Lite at $0.05 (720p) and $0.08 (1080p) with no 4K, with audio included by default. Sume's Omni rates are the provider list of $0.10, $0.15 and $0.30 times 1.25: $0.125, $0.1875 and $0.375 a second.
The ratio table
A ratio above 1.00x means the Veo tier costs more per second than Sume's Omni row at the same resolution. Below 1.00x, Veo is cheaper at Google's list.
| Veo tier | Resolution | Veo per second | Sume Omni per second | Veo / Omni |
|---|---|---|---|---|
| Veo 3.1 Standard | 720p | $0.40 | $0.125 | 3.20x |
| Veo 3.1 Standard | 1080p | $0.40 | $0.1875 | 2.13x |
| Veo 3.1 Standard | 4K | $0.60 | $0.375 | 1.60x |
| Veo 3.1 Fast | 720p | $0.10 | $0.125 | 0.80x |
| Veo 3.1 Fast | 1080p | $0.12 | $0.1875 | 0.64x |
| Veo 3.1 Fast | 4K | $0.30 | $0.375 | 0.80x |
| Veo 3.1 Lite | 720p | $0.05 | $0.125 | 0.40x |
| Veo 3.1 Lite | 1080p | $0.08 | $0.1875 | 0.43x |
How to read it
Standard is the only tier that costs more than Omni on Sume at every resolution it offers: 3.2x at 720p, 2.13x at 1080p and 1.6x at 4K. Fast is cheaper on paper at each resolution (0.8x, 0.64x, 0.8x). Lite is the cheapest at 0.4x and 0.43x, but it has no 4K row.
These are list-against-Sume ratios, so they include Sume's 25 percent. They also compare per second, not per clip: Veo and Omni differ in which lengths they accept, and a clip you cannot request is a price you cannot pay.
A worked example
Take a 30-second spot at 1080p. Veo 3.1 Fast at Google's list is 30 x $0.12 = $3.60. Veo 3.1 Standard is 30 x $0.40 = $12.00. Sume's Omni row is 30 x $0.1875 = $5.625, which rounds to $5.63. Because Omni on Sume takes 3 to 10 seconds per job, that spot is at least three jobs, for example 10 + 10 + 10 seconds, and the three clips are joined afterward. The ratio table tells you which line wins per second; the clip-length limit tells you how many jobs it takes.
What the ratios cannot tell you
They say nothing about quality. Google's video page recommends Gemini Omni Flash as the default and positions Veo 3.1 for work that needs video extension, frame-specific generation and image-based direction. If you rely on those features, a cheaper ratio is not a reason to switch.
They also depend on a model Sume does not list. Sume has no Veo row, so the practical decision on Sume is among its own listed models. Use the ratios to judge what the move costs you relative to Google's list, then test one clip on gemini-omni-flash-1.1 before moving a pipeline.
Sources
Related posts
More in Comparisons
- Veo 3.1 Standard, Fast and Lite per-second prices vs Sume rows
Google lists Veo 3.1 at $0.05 to $0.60 per second. Sume's catalog has no Veo row, so this compares Google's prices with Wan 3.0, Omni Flash and Kling on Sume.
- Vidu Q4 Preview takes 15 reference images: Sume rows take 9 or 10
Vidu Q4 Preview accepts 1 to 15 reference images. On Sume the largest documented image-reference cap is 10 (Wan 3.0, Omni); H3 takes 9.
- Vidu Q4 Preview makes 16 s clips: which Sume rows go past 10 s?
Vidu Q4 Preview runs 3 to 16 seconds. On Sume, Wan 3.0 (2 to 30 s) and Seedance 2.5 (4 to 30 s) go past 16; Omni stops at 10 s. Prices for 16 s inside.
- Vidu Q4 Preview takes 3 audio references: which Sume rows take audio
Vidu Q4 Preview accepts up to 3 mp3 voice references of 3 to 12 s. On Sume, Seedance 2.x, Wan 3.0 and the MiniMax H3 rows take audio references; Omni does not.
Written by Sume