Veo 3.1 Cost per Accepted Video: Calculate Duration, Resolution, and Retries
A practical Veo 3.1 cost calculator using official Gemini API rates, with one-attempt prices, retry scenarios, multi-shot budgeting, and production-cost boundaries.
Contents
You may have calculated that one eight-second Fast clip at 1080p costs only $0.96 and treated that as the price of a usable shot. If the third generation is the first one you approve, the bill is already $2.88; add several shots and the gap grows quickly. By the end of this guide, you can calculate cost shot by shot, set a retry stop-loss, and decide which tier and resolution to test first for your delivery specifications.
Use this formula to calculate the real cost of an accepted video
The generation cost of a deliverable video is not final runtime multiplied by one rate; it is the total of every billable attempt across every shot.
Cost of one successful generation:
billable seconds × the per-second rate for the selected tier and resolution
Generation cost of an accepted video:
Σ (billable seconds per shot × per-second rate × billable attempts)
For example, one eight-second Fast generation at 1080p costs 8 × $0.12 = $0.96. If the third result is the first usable one, that shot costs $0.96 × 3 = $2.88 to generate.
A “billable attempt” here means a version that was generated successfully and incurred a charge. A request that never produces a video is different from a generated result that you later reject during review.
Choose a tier by scenario: what should you test first when cost matters?
For a cost-first workflow, test Lite first for 720p or 1080p and Fast first for 4k; move to another tier only when the current choice does not pass your acceptance criteria.
| Your scenario | Test first | Why | When to change |
|---|---|---|---|
| High-volume drafts, social experiments, or internal previews at 720p/1080p | Lite | At $0.05/sec for 720p and $0.08/sec for 1080p, it has the lowest official rate of the three tiers | Test Fast if Lite cannot meet your criteria for subject, motion, composition, or consistency |
| You need 1080p and want room to iterate without starting at the highest rate | Fast | Its 1080p rate is $0.12/sec, versus $0.40/sec for Standard | If Fast reaches your stop-loss without passing, revise the prompt or shot design first; test Standard only if you still need another tier comparison |
| The final deliverable explicitly requires 4k | Fast | Fast costs $0.30/sec at 4k; Lite does not support 4k, and Standard costs $0.60/sec | Test the same shot with Standard only when Fast misses specific acceptance criteria; do not default every shot to Standard |
| You need scene extension, last-frame control, or integration with a legacy pipeline | Veo 3.1 | Google lists these as specific Veo 3.1 use cases | If you do not need these capabilities, compare Gemini Omni Flash before committing to a Veo 3.1 workflow |
This is a cost-first test order, not a quality ranking. A lower rate does not guarantee approval, and a higher rate does not guarantee success on the first attempt. Write the acceptance criteria first, then find the least expensive workflow that actually meets them.
Official rates set the floor for every attempt
As of September 24, 2026, paid Veo 3.1 usage in the Gemini API is billed per second, with both tier and resolution determining the cost. Check the official Google pricing page again before approving a production budget because prices and model status can change.
| Tier | Model ID | 720p | 1080p | 4k |
|---|---|---|---|---|
| Standard | veo-3.1-generate-preview | $0.40/sec | $0.40/sec | $0.60/sec |
| Fast | veo-3.1-fast-generate-preview | $0.10/sec | $0.12/sec | $0.30/sec |
| Lite | veo-3.1-lite-generate-preview | $0.05/sec | $0.08/sec | Not supported |
Four conclusions directly affect the budget:
- Standard costs the same at 720p and 1080p. If delivery genuinely requires 1080p, there is no API-price reason to fall back to 720p.
- Fast rises from $0.12/sec at 1080p to $0.30/sec at 4k, a 2.5× increase.
- Lite does not support 4k, so a 4k project must be budgeted with Fast or Standard.
- The listed prices are for video with audio by default; there is no published no-audio discount you can safely subtract.
None of the three Veo 3.1 model IDs has a free tier. Google also says that when certain audio-processing problems prevent a video from being generated, charging applies only when a video is generated successfully. A generated version you later discard should still be recorded according to the actual bill.
Eight-second shots: what do one, three, and five attempts cost?
A small per-attempt price can become a large line item because the bill grows in direct proportion to billable attempts. Eight seconds is used only to make the arithmetic easy; it is not a claim about a fixed or maximum generation length.
| Tier | 8 sec at 720p | 8 sec at 1080p | 8 sec at 4k |
|---|---|---|---|
| Standard | $3.20 | $3.20 | $4.80 |
| Fast | $0.80 | $0.96 | $2.40 |
| Lite | $0.40 | $0.64 | Not supported |
For an eight-second 1080p shot, retry scenarios look like this:
| Billable attempts | Standard | Fast | Lite |
|---|---|---|---|
| 1 | $3.20 | $0.96 | $0.64 |
| 3 | $9.60 | $2.88 | $1.92 |
| 5 | $16.00 | $4.80 | $3.20 |
The table cannot tell you which tier has better quality. It can answer a more useful budgeting question: how many paid attempts are you willing to fund for one shot? If you cap Fast 1080p at five attempts, the API budget for that shot is $4.80. Once the cap is reached, change the prompt, redesign the shot, or change the workflow instead of generating without a limit.
Multi-shot videos must be calculated shot by shot
Multiplying a final 32-second runtime by one rate misses the cost of every discarded version. A useful production sheet needs one row per shot, not just one row for the whole project.
Suppose a project contains four eight-second shots, all generated with Fast at 1080p for $0.12/sec. The shots require 1, 2, 3, and 4 billable attempts respectively:
| Shot | Seconds | Attempts, example | Calculation | Cost |
|---|---|---|---|---|
| A | 8 | 1 | 8 × $0.12 × 1 | $0.96 |
| B | 8 | 2 | 8 × $0.12 × 2 | $1.92 |
| C | 8 | 3 | 8 × $0.12 × 3 | $2.88 |
| D | 8 | 4 | 8 × $0.12 × 4 | $3.84 |
| Total | 32 accepted seconds | 10 shot attempts | $9.60 |
A one-pass calculation for 32 seconds would be $3.84; the shot-level calculation is $9.60. The extra $5.76 comes from additional versions, not from a longer finished video.
Set three retry limits when you do not know the acceptance rate
Do not borrow an imaginary “industry-average retry rate”; define target, stress, and stop-loss scenarios for each shot. This shows the cash range before production begins and tells the team when it must stop and change the plan.
- Target scenario: the number of attempts you consider reasonable for an ordinary shot.
- Stress scenario: a higher cap for difficult motion or an important hero shot.
- Stop-loss scenario: the hard limit after which you change the prompt, redesign the shot, change resolution, or test another tier.
For the same eight-second Fast 1080p shot, one, three, and five attempts cost $0.96, $2.88, and $4.80. You might set three attempts as the target and five as the stop-loss. Every attempt after the fifth adds another $0.96 without guaranteeing that the result will be closer to approval.
Important shots can receive a higher cap, but the cap should be written into the budget before generation starts. Otherwise, “the attempt is cheap” can turn into unlimited retries whose total exceeds a higher-priced alternative.
Choose resolution by delivery need: do not make every draft 4k
Unless 4k is a real delivery need, use the lowest resolution that lets you evaluate the shot and reserve 4k for selected final assets. This lowers both the first attempt and every failed retry that follows it.
Using the official prices checked on September 24, 2026:
- Standard: 720p and 1080p cost the same; 4k costs 50% more.
- Fast: 1080p costs 1.2× the 720p rate; 4k costs 2.5× the 1080p rate.
- Lite: 1080p costs 1.6× the 720p rate; 4k is not supported.
With Standard, 720p and 1080p have the same API price if your workflow supports 1080p. Fast is different: an eight-second shot rises from $0.96 at 1080p to $2.40 at 4k. At five attempts, the comparison is $4.80 versus $12.00.
For social posts, internal previews, or composition checks without a hard 4k need, do not upgrade every intermediate version merely for consistency. Apply 4k only to approved shots when the delivery channel truly needs it.
Put the API bill back into the full production budget
Generation is only one production cost; editing, sound, captions, and human review belong in the same budget. When generation is inexpensive, selection and editing may cost more. With high resolution and many retries, the API bill can become a major line item.
Record at least these fields for every shot:
| Field | What you should enter |
|---|---|
| Shot ID | A, B, C, or the storyboard name |
| Billable seconds | The seconds shown in the actual billing record |
| Tier and resolution | Standard, Fast, or Lite; 720p, 1080p, or 4k |
| Current rate | The per-second price from the official page |
| Target / stop-loss attempts | The planned attempt count and hard cap |
| Actual billable attempts | Based on request results and billing records |
| Shot generation cost | seconds × rate × billable attempts |
| Acceptance result | accepted, revise, or abandoned |
At project level:
full production budget = total generation cost + editing + voice/music + captions/localization + human review + storage and other costs
When comparing two workflows, do not compare only the per-second rates. Put actual attempt counts, human selection time, and post-production costs into the same sheet to see which workflow truly costs less.
Use your own records for the numbers public pricing cannot provide
Public pricing tells you the rate per second, but it cannot supply your retry rate, acceptance rate, taxes, or actual billing-rounding behavior. Those variables directly affect the final budget and should come from request logs and invoices.
Google’s public pricing information does not publish a universal average retry count or promise that any tier will pass review on the first attempt. The one-, three-, and five-attempt examples in this article are budgeting scenarios, not model success rates.
For actual reconciliation, use durations supported by the current request, billable seconds shown in your account, real billable attempts, and your own acceptance history. After several projects, group attempts by shot type—people, products, complex motion, or dialogue—to make the next estimate more accurate.
Add taxes, exchange rates, card fees, and platform fees separately. Do not mix Gemini API, Vertex AI, Flow, Gemini app subscriptions, or third-party API prices in one rate table because their billing models may differ.
Frequently asked questions
How much does Veo 3.1 cost per second?
Using Gemini API prices checked on September 24, 2026, default video-with-audio rates range from $0.05/sec for Lite at 720p to $0.60/sec for Standard at 4k. The exact rate depends on tier and resolution.
Is it cheaper without audio?
The official pricing page lists default prices with audio and does not publish a no-audio discount that can be used in this calculation. Do not subtract an audio charge unless the current official page explicitly lists a separate rate.
Are failed generations billed?
Google says that when certain audio-processing problems prevent a video from being generated, charging applies only when the video is generated successfully. A successfully generated clip that later fails your creative review is a different case and should be counted according to the actual bill.
Is there a Veo 3.1 free tier?
The current official pricing table shows no free tier for any of the three Veo 3.1 model IDs. Budget testing as paid attempts.
Build your budget in four steps
Start with the delivery specification, calculate one attempt, and then set a retry stop-loss. Use this sequence:
- Write down the duration, resolution, and acceptance criteria for every shot.
- Choose the first tier to test using the cost-first order and calculate its per-attempt price.
- Calculate one-, three-, and five-attempt scenarios, then set a hard cap for important shots.
- Record actual billing and acceptance shot by shot, and add editing, sound, captions, and human labor.
If the total is too high, first remove unnecessary 4k generations and unlimited retries; then consider another tier or redesigning the shot. That optimizes the cost of a deliverable video, not a deceptively low one-attempt price that retries can multiply.
