Veo 3.1 Lite 1080p at 8 cents a second vs Sume 1080p models

Google lists Veo 3.1 Lite 1080p at $0.08 a second. Here is the same 10-second 1080p clip priced on Veo tiers and on Sume models, with the gaps stated plainly.

4 min readSume
All posts

Veo 3.1 Lite is cheaper per second at 1080p than every Sume row in the table below. Google's pricing page lists Lite 1080p at $0.08 a second, and the lowest 1080p rate among the Sume models compared here is $0.14 a second for Kling Video v3 Pro with audio off. If you only need the cheapest 1080p seconds, that is Google. If you need a model that Sume actually runs, the table shows the cost of a 10-second clip.

Ten seconds at 1080p, side by side

Google's prices are list prices per second and include audio by default, per the page. Sume bills the provider list price times 1.25, and the Sume rows below apply that factor to the list rates in the repository price tables.

10-second 1080p clip, prices read 2026-10-06
ModelPer second10 seconds
Veo 3.1 Lite (Google)$0.08$0.80
Veo 3.1 Fast (Google)$0.12$1.20
Veo 3.1 Standard (Google)$0.40$4.00
Kling Video v3 Pro on Sume, audio off$0.14$1.40
Kling Video v3 Pro on Sume, audio on$0.21$2.10
Gemini Omni Flash 1.1 on Sume$0.1875$1.875
MiniMax H3 Max on Sume$0.20$2.00
Wan 3.0 on Sume$0.25$2.50

What the cheaper row does not tell you

A price per second is also not a price per usable clip. Retakes multiply the cost, so a model that lands the shot in one try at $0.20 a second can beat a cheaper model that needs three.

  • Google's page lists no 4K rate for Veo 3.1 Lite.
  • Sume does not run any Veo model, so none of the Google rows can be bought through Sume.
  • Gemini Omni Flash 1.1 takes 3 to 10 seconds per job on Sume; check each model's limits in the models endpoint before you batch.

When Sume is the right side of the table

Choose by what you need around the clip. Sume gives one API key, a shared job envelope, and finishing tools after generation: trim, captions and timeline assembly. If your pipeline already lives on Google's API and 1080p seconds are the only metric, stay there. If you also assemble and caption on one invoice, price the whole pipeline, not one row.

Method

Each Google figure is copied from the pricing page on the day of reading. Each Sume figure is the repository list rate multiplied by 1.25 and is rounded to a tenth of a cent only where the arithmetic produces one. The current Sume price for any job is quoted by the catalog endpoint, so confirm it there before you budget a batch. None of the rows includes retakes, upscaling, captions or assembly, which Sume bills as separate jobs.

Sources

Related posts

More in Comparisons

All Comparisons posts

Written by Sume