Veo 3.1 Lite at 720p: eight drafts cost the same as one Standard clip
At Google's listed rates, one 8-second Veo 3.1 Standard clip costs $3.20 and eight Lite 720p clips cost the same. Here is the draft-then-final math.

On the Gemini API pricing page, Veo 3.1 Standard is $0.40 per second at 720p and Veo 3.1 Lite is $0.05, so eight Lite 720p drafts cost the same as one Standard 720p clip of the same length. For an 8-second clip that is $3.20 for one Standard render against $0.40 for each Lite draft.
| Tier | 720p per second | 1080p per second | 8 s at 720p | 8 s at 1080p |
|---|---|---|---|---|
| Standard | $0.40 | $0.40 | $3.20 | $3.20 |
| Fast | $0.10 | $0.12 | $0.80 | $0.96 |
| Lite | $0.05 | $0.08 | $0.40 | $0.64 |
Lite is half of Fast at 720p, not at 1080p
Google's March 31 announcement says Lite costs under 50% of Veo 3.1 Fast. The pricing rows show exactly half at 720p ($0.05 against $0.10) and two thirds at 1080p ($0.08 against $0.12). If you plan to ship at 1080p, price your drafts at 1080p as well, or the saving is smaller than the headline suggests. The Veo docs also say 1080p needs an 8-second clip, so a 1080p draft is never shorter than 8 seconds.
The draft-then-final pattern
The arithmetic only helps if the draft predicts the final. A workable loop is:
- Generate several cheap drafts of the same brief, each with a different prompt variation.
- Review them silently for framing, motion and product visibility.
- Re-render only the winner on the final tier.
- Cap the number of drafts per brief, because eight drafts already equal one final at 720p.
A worked example
Suppose a campaign needs one final 8-second clip at 720p. Eight Lite drafts cost $3.20, the same as one Standard clip. Adding a Standard final brings the total to $6.40, which is also what two blind Standard renders cost. The difference is that the drafts show you eight options and the final render is a deliberate choice.
The pattern breaks when the final needs something Lite does not offer. The pricing rows show no 4K for Lite, and Standard and Fast carry the 4K rates, so a 4K deliverable cannot be drafted on the cheap tier at its final resolution. In that case, draft composition on Lite and render the final on a tier that has the resolution.
Failed requests
The pricing page says Veo is charged only on success, so a failed draft does not add to the spend. The limit on this math is that a successful draft you throw away still costs its full price.
The same loop on Sume
Sume reserves the cost at submit, at provider list times 1.25, and usage.cost on the poll response is the billable amount. Read each model's pricing_skus from GET /v1/videos/models, pick the cheapest model that supports your final aspect ratio for drafts, and compare that to your final model before you start the loop. Details are in Video generation.
Sources
Related posts
More in Pricing
- Video API billing terms checklist: expiry, refunds, storage
Higgsfield's API post lists pay-as-you-go USD, no charge for failed requests, funds expiring in one year and files kept 7 days. A buyer checklist built on it.
- How Sume pricing works: plans, one wallet, published model rates
Sume plans set access and concurrency. Usage draws from one prepaid wallet at each model's published USD rate, for generation, the Agent, Formats, and the API.
- AI avatar video API pricing: cost per second and per minute
Sume bills AI avatar video per second by quality tier, with separate rates when you send a product image. Per-minute costs for standard, plus, and max.
- AI video generation cost per video: what one Sume API run cost
To see what one Sume run or video job cost, call GET /v1/usage with run_id or job_id and read debited_usd: the wallet deduction, agent turns included.
Written by Sume