Google Veo Pricing 2026: Flow Credits, Free Access and API Cost
Google Veo pricing depends on where you generate the video and how many attempts it takes to get usable footage. Veo 3.1 is available through Google Flow credits, paid Google AI subscriptions and usage-based developer billing. Those routes use different billing units, so comparing only the headline price can be misleading.
This guide separates the access routes, then goes one step further: it shows how retries change the effective cost of a finished clip. The examples use Google’s current published prices and deliberately treat retry counts as adjustable assumptions rather than pretending there is one universal Veo rejection rate.
If you want to generate AI video without dealing directly with Google’s subscription and API structure, you can also try the DIY AI Video Generator.
| Veo access route | Current starting point | Billing unit | Best fit |
|---|---|---|---|
| Google Flow free access | £0 with 50 daily Flow credits | Credits per generation | Trying Veo without committing to a subscription |
| Google AI subscription | From £4.49/month in the UK | Daily credits plus monthly Flow allowance | Manual creation and larger batches |
| Extra AI credits | Available to eligible Plus, Pro and Ultra subscribers | Purchased credit packs | Projects that exceed the included allowance |
| Gemini API | From $0.05 per generated second for Veo 3.1 Lite with audio | US dollars per generated second | Apps, automation and repeatable pipelines |
The number to calculate is cost per usable clip
A pricing table tells you what one generation costs. A production budget needs another variable: how many generations you expect to make before accepting one.
A clip can render successfully and still be rejected because the subject changes, the movement is wrong, continuity breaks, text is malformed, or the camera does something you cannot use in the edit. That is different from a technical generation failure.
Google notes that some API generation failures caused by audio processing are not billed. A successfully generated video that you decide not to use is different: it has still consumed a generation.
For Flow:
credits per usable clip = credits per generation × attempts per accepted clip
For the API:
cost per usable clip = seconds × price per second × attempts per accepted clip
The retry number is yours. If your workflow usually gets an acceptable result on the second attempt, enter two. If a difficult character-consistency shot normally takes five attempts, budget five. Don’t substitute somebody else’s anecdotal rejection rate for your own production data.
Veo retry cost calculator: worked examples
These scenarios show why two people using the same Veo model can end up with very different real costs. The attempt counts below are assumptions for calculation, not measured Veo rejection rates.
| Workflow | One attempt | 2 attempts per usable clip | 3 attempts | 5 attempts |
|---|---|---|---|---|
| Flow Lite, non-Ultra | 10 credits | 20 credits | 30 credits | 50 credits |
| Flow Fast, non-Ultra | 20 credits | 40 credits | 60 credits | 100 credits |
| Flow Quality | 100 credits | 200 credits | 300 credits | 500 credits |
| API Lite, 8s, 1080p with audio | $0.64 | $1.28 | $1.92 | $3.20 |
| API Fast, 8s, 1080p with audio | $0.96 | $1.92 | $2.88 | $4.80 |
| API Standard, 8s, 1080p with audio | $3.20 | $6.40 | $9.60 | $16.00 |
| API Standard, 8s, 4K with audio | $4.80 | $9.60 | $14.40 | $24.00 |
Consider a project that needs 10 usable eight-second clips. You choose Veo 3.1 Fast at 1080p through the API and assume three attempts for every clip you keep.
- 10 finished clips
- 3 assumed attempts per clip
- 30 generated clips
- 8 seconds each
- $0.12 per second
- Estimated generation spend: $28.80
If every first attempt worked, the same finished footage would cost $9.60. At five attempts per accepted clip, it would cost $48. The published model rate never changed. The production economics did.
The equivalent Flow calculation is just as useful. Ten accepted clips on non-Ultra Fast with three attempts each require 30 generations, or 600 Flow credits. Switch the same workflow to Quality, and the requirement becomes 3,000 credits.
Cheapest Google Veo route for each type of work
| What you need | Sensible starting route | Cost issue to watch |
|---|---|---|
| Learn Veo without paying | Free Flow | The daily allowance cannot be banked indefinitely |
| A few clips spread across several days | Free Flow | Your production schedule has to fit the daily refresh |
| A small batch in one sitting | Google AI Plus | 200 monthly credits disappear quickly if shots require retries |
| Regular manual video production | Google AI Pro | Track accepted clips rather than total generations |
| High-volume manual Flow use | Google AI Ultra | Capacity only has value if you use it before expiry |
| Automated or product-integrated generation | Gemini API | Retry loops need explicit spend limits |
For a broader comparison of no-cost options, see our best free AI video generators. Veo’s free allowance is useful, but daily credits are only one part of deciding whether a free workflow is practical.
Google AI subscription pricing and Flow credits
Google’s current UK prices are £4.49 per month for AI Plus, £18.99 for AI Pro, £79.99 for the lower Ultra tier and £189.99 for the higher Ultra tier. The monthly Flow allowances are 200, 1,000, 10,000 and 25,000 credits respectively.
This guide has an important change from the earlier version. Google’s current Flow credit documentation says subscribers still receive 50 daily Flow credits and receive their subscription credits in addition. The monthly allowance does not replace the daily allocation.
| Plan | UK monthly price | Daily Flow credits | Extra monthly Flow credits |
|---|---|---|---|
| No Google AI subscription | £0 | 50 | None |
| Google AI Plus | £4.49 | 50 | 200 |
| Google AI Pro | £18.99 | 50 | 1,000 |
| Google AI Ultra 5x | £79.99 | 50 | 10,000 |
| Google AI Ultra 20x | £189.99 | 50 | 25,000 |
Do not add 50 × 30 to the monthly allowance and treat the result as a conventional monthly credit balance. The 50-credit allocation refreshes daily, and unused daily credits do not roll over. Monthly subscription credits refresh with the billing cycle and also do not roll into the next cycle.
The practical distinction is scheduling. A creator working a little every day can extract substantial value from the daily allocation. Someone who needs 40 generations on Friday afternoon needs enough credits available then.
Google Flow pricing per Veo 3.1 generation
Flow currently offers Veo 3.1 Lite, Fast and Quality. Lite and Fast support 4, 6 and 8-second generations in common text-to-video and first-frame workflows. Some features require eight seconds. Quality is an eight-second generation.
| Veo 3.1 model | Non-Ultra cost | Ultra cost | Typical supported duration |
|---|---|---|---|
| Lite | 10 credits | 5 credits | 4, 6 or 8 seconds |
| Fast | 20 credits | 10 credits | 4, 6 or 8 seconds |
| Quality | 100 credits | 100 credits | 8 seconds |
Flow charges per generation, not simply per prompt. One request can trigger more than one generation, so check the displayed charge before running a batch.
Also check the active model every time cost matters. A Quality generation costs 100 credits compared with 10 for Lite on a non-Ultra account. An unnoticed model change can therefore have a much larger effect on the balance than shaving a generation or two from a project.
Is Google Veo 3.1 free?
Yes. Google Flow currently gives non-subscribers 50 Flow credits per day. At the current Veo 3.1 credit rates, that can cover five Lite generations or two Fast generations with 10 credits remaining.
Free users can’t save several days of unused credits for one large batch. The daily allowance expires rather than rolling forward. Google also warns that non-subscribers may have restricted video generation during peak periods.
The Gemini Developer API has no equivalent free Veo 3.1 generation tier. Budget programmatic Veo usage as paid usage from the start.
Google Veo 3.1 API pricing per second
The Gemini API uses a much cleaner billing unit than Flow: generated seconds. The current default Veo 3.1 API outputs include generated audio.
| Veo 3.1 API model | 720p with audio | 1080p with audio | 4K with audio |
|---|---|---|---|
| Standard | $0.40/sec | $0.40/sec | $0.60/sec |
| Fast | $0.10/sec | $0.12/sec | $0.30/sec |
| Lite | $0.05/sec | $0.08/sec | Not supported |
At 1080p, an eight-second Lite clip is $0.64, Fast is $0.96, and Standard is $3.20 before creative retries. An eight-second 4K Standard generation is $4.80.
Duration can change the API cost, but not every configuration supports shorter clips
Veo 3.1 API generation supports 4-, 6-, and 8-second durations, but with important restrictions. At 720p, shorter generations can reduce spend directly because billing is per second. Higher-resolution and reference-driven workflows narrow that choice.
| API workflow | Supported duration to budget around | Why it affects cost |
|---|---|---|
| 720p text-to-video | 4, 6 or 8 seconds | A four-second test costs half as much as an eight-second generation at the same per-second rate |
| 1080p output | 8 seconds | You cannot use a four-second render simply to halve the bill |
| 4K Standard/Fast | 8 seconds | The highest per-second rates also require the full eight-second duration |
| Reference-image workflows | 8 seconds | The workflow constraint removes shorter draft generations |
| Video extension | Model-specific restrictions apply | Extension should be budgeted separately from a simple short text-to-video test |
This creates a useful drafting strategy for API users. If a 720p four-second generation supports the feature you need, prove the prompt, motion, and scene direction cheaply before moving to an eight-second, higher-resolution output. Do not assume that shortcut works for every Veo feature.
Flow credits and API dollars solve different problems
| Factor | Google Flow | Gemini API |
|---|---|---|
| Billing unit | Credits per generation | US dollars per generated second |
| Best suited to | Manual creative work | Apps and automated workflows |
| Main budgeting variable | Generations per accepted clip | Seconds × attempts per accepted clip |
| Natural spending control | Available credit balance | Your own budgets and retry limits |
| Main waste risk | Expired allowance or unnecessary generations | Automated retries and unnecessarily expensive settings |
Assigning a fixed cash value to one Flow credit creates false precision. A subscription includes other Google products, daily credits sit alongside monthly credits, and Ultra changes the credit charge for some Veo models. Keep credits and API dollars separate, then compare what each route costs for the finished clips you need.
The production costs most Veo pricing tables miss
- Creative retries: a completed render may still be unsuitable for the final edit.
- Multiple generations: Flow pricing applies per generation, and some requests can create more than one.
- Resolution restrictions: the API requires eight-second generation for 1080p and 4K, so you cannot always reduce cost with a shorter clip.
- Model selection: accidentally generating with Quality instead of Lite or Fast can consume credits much faster.
- Credit expiry: unused daily and subscription Flow credits do not accumulate indefinitely.
- Automation: an API workflow needs a maximum retry count and spend guardrail. Otherwise, an unsuccessful creative loop can continue generating paid clips.
- Upscaling: Flow currently lists 1080p upscaling at zero credits for Plus, Pro and Ultra subscribers, while 4K upscaling is restricted to Ultra and costs credits.
A recurring problem in real production workflows is treating “generated successfully” and “usable” as the same event. They are not. Reference drift, unwanted motion and continuity errors can all turn a technically successful output into footage that never reaches the timeline.
Until you have your own data, use an explicit retry assumption. Once you have completed several projects, replace that assumption with your actual number of generations divided by accepted clips.
See more of our reporting in Google Top Stories, AI Overviews and AI Mode.
Which Google Veo plan makes sense?
Start with free Flow if you are still learning Veo. Fifty daily credits are enough to test Lite and Fast without committing to a monthly subscription. The constraint is scheduling, not headline cost.
AI Plus is useful when you need a modest extra pool. You receive the daily allocation plus 200 subscription credits each month. It is less attractive if your normal workflow takes several attempts to get a keeper.
AI Pro gives regular creators more room. The 1,000 monthly credits provide considerably more batch capacity without moving to Ultra pricing, and Google currently allows eligible Plus, Pro and Ultra subscribers to buy extra AI credits in supported regions.
Ultra changes the Flow economics for Lite and Fast. Those models use fewer credits per generation for Ultra subscribers. Quality remains expensive at 100 credits, so a retry-heavy Quality workflow can still consume a large balance.
Use the API when generation belongs inside a product or automated pipeline. The pricing is easier to model because it is based on seconds, but you must control retries yourself. For a wider capability comparison before committing to Veo, see our best AI video generators.
Google Veo pricing FAQs
How much does Google Veo cost per video?
There is no single per-video price. In Flow, Veo 3.1 currently costs 10 to 100 credits per generation for non-Ultra users, depending on the model. Through the Gemini API, an eight-second 1080p video with audio costs $0.64 on Lite, $0.96 on Fast or $3.20 on Standard before retries.
How much is Google Veo per month?
You can use Veo through free Google Flow access. UK Google AI subscriptions currently cost £4.49 per month for Plus, £18.99 for Pro, £79.99 for Ultra 5x and £189.99 for Ultra 20x. API use is billed separately and isn’t included in a fixed monthly Veo subscription.
Do paid Google AI subscribers still get the 50 daily Flow credits?
Yes. Google’s current Flow documentation says users receive 50 Flow credits per day with or without a subscription. Plus, Pro and Ultra then receive additional monthly Flow credits.
How many Flow credits does one Veo video use?
Veo 3.1 Lite currently costs 10 credits per generation for non-Ultra users and 5 for Ultra. Fast costs 20 credits per generation for non-Ultra users and 10 for Ultra. Quality costs 100 credits for all users.
Can Google AI Plus users buy extra Flow credits?
Yes, in supported regions. Google’s current guidance lists Plus, Pro and Ultra subscribers as eligible to purchase additional AI credits. This differs from earlier rules that more heavily restricted purchases.
Does the Veo API have a free tier?
No. Google’s current Veo 3.1 developer pricing lists paid generation only. Lite with audio starts at $0.05 per second for 720p output.
How should I budget for Veo retries?
Choose an assumed number of attempts for every clip you expect to keep. Multiply that by the Flow credit charge or API generation cost. Do not present the assumption as Veo’s rejection rate. Once you have real project data, replace the assumption with your measured generations-per-accepted-clip figure.
Is Flow cheaper than the Veo API?
For manual creation, free or subscription Flow credits can make Flow the cheaper practical route. For software and automation, the API provides the correct programmatic access and a predictable per-second billing unit. Compare the routes based on the number of usable clips your project requires, rather than trying to invent a fixed dollar value for one Flow credit.
You Might Also Like:
Best AI Video Generators
Best Image To Video AI
Best Free AI Video Generators 2026
