Veo 3.1 direct from the Gemini API
Prices read from Google's published Gemini API pricing on 2026-07-30 and re-checked quarterly. Audio is included in every rate below.
| Tier | 720p | 1080p | 4K |
|---|---|---|---|
| Veo 3.1 Lite | $0.05 / sec | $0.08 / sec | Not supported |
| Veo 3.1 Fast | $0.10 / sec | $0.12 / sec | $0.30 / sec |
| Veo 3.1 Standard | $0.40 / sec | $0.40 / sec | $0.60 / sec |
You pay per second of output whether or not the result is usable, which matters more than the headline rate. A tier is a compute budget: higher tiers cost more per second and return more fidelity. Consumer subscriptions to Google's own apps are priced separately and are not the same as API access.
Veo 3.1 inside GATA
| Line | Credits / second | ≈ £ / second |
|---|---|---|
| Base | 45 | £0.45 – £0.54 |
| + 4K | 75 | £0.75 – £0.90 |
| + lip-sync | 60 | £0.60 – £0.72 |
| + 4K and lip-sync | 90 | £0.90 – £1.08 |
The £ range comes from GATA's overage rates, which tier down by plan: £0.012 per credit on Starter, £0.011 on Studio, £0.010 on Pro. A background-noise toggle adds 5 credits per second on any of the rows above. Rates verified against application code on 2026-07-30; the full per-model table is on the models comparison.
Worked example: a 6-second hero shot in 4K with dialogue is 90 × 6 = 540 credits, roughly £5.40 to £6.50. The same 6 seconds with no uplifts is 270 credits.
The duration rule that changes your bill
Veo 3.1 only renders 4, 6, or 8 seconds. Requested durations round up to the next supported value, and anything longer than 8 seconds is clamped to 8. Ask for 5 seconds and you are billed for 6 — 270 credits instead of 225.
Budget from the rounded duration, not the one you typed. GATA shows a confirmation before generating whenever the model would adjust a shot's duration, so the change is visible before you spend. For anything past 8 seconds the shot has to be split, or rendered on a model without the bucket restriction — see the comparison for which.
Which route is cheaper?
The API is cheaper for raw clips, and by a wide margin on the Lite and Fast tiers. At $0.05 per second, Lite is a fraction of GATA's 45-credit rate. If your requirement is "generate Veo clips", use the API directly and keep the difference.
The comparison shifts at Standard. At $0.40 per second, direct Veo Standard and GATA's ~£0.45–£0.54 land close enough that the per-second number stops being the deciding factor.
And it is worth being precise about what the API does not include. It returns a clip. It does not hold an approved look between shots, keep locations consistent, bind a cast reference, track which shot belongs to which scene, or hand back a scored and mixed cut. Every one of those is something a team otherwise builds and maintains itself — see prompt drift for what happens when that structure lives in a prompt box instead of project state.
The Veo limitation that decides most campaigns
Veo 3.1 does not accept locked-cast composites as references. Only Kling o3 and Kling v3 do. For a campaign with a recurring protagonist, that single fact usually settles the model choice regardless of price: Veo renders a superb stranger.
The standard pattern is Kling o3 at 20 credits per second for every recurring-character shot, with Veo 3.1 reserved for the one or two hero beats where fidelity and native audio earn the 45. Because the model is a per-shot choice, mixing them costs nothing in rework — the shot inherits the same project context either way. See shot inheritance and Kling AI pricing.
Frequently asked
How much does Veo 3.1 cost per second?
On the Gemini API, Veo 3.1 Lite is $0.05 per second at 720p and $0.08 at 1080p; Fast is $0.10 at 720p, $0.12 at 1080p, and $0.30 at 4K; Standard is $0.40 at 720p and 1080p, and $0.60 at 4K. Audio is included in those rates. Verified 2026-07-30. Inside GATA, Veo 3.1 is 45 credits per second, roughly £0.45 to £0.54.
Why does a 5-second Veo shot get billed as 6 seconds?
Veo 3.1 only renders 4, 6, or 8 seconds. A requested duration rounds up to the next supported value and anything over 8 seconds is clamped to 8. A 5-second shot is rendered and billed as 6. GATA shows a confirmation before generating whenever the model would adjust your duration, so it is never silent.
Is Veo 3 or Veo 3.1 the current version?
Veo 3.1 is current and is what GATA renders with. Searches for 'Veo 3 pricing' generally land on 3.1 rates now, which is what this page lists.
Is the Veo API cheaper than using GATA?
For raw clips, yes — especially on the Lite and Fast tiers. The API charges for inference and nothing else. GATA's 45 credits per second is a blended workspace rate covering the production around the model: persistent look and locations, script and shot state, retry handling, and a scored, mixed cut. If you need clips, use the API. If you need a film, the difference is what you are buying.
Can Veo 3.1 keep a character consistent across shots?
Not reliably. Veo 3.1 does not accept locked-cast composite references — only Kling o3 and Kling v3 do. Veo will render an excellent shot of a person, but not dependably the same person across a dozen shots. The usual pattern in GATA is Kling o3 for recurring-character shots at 20 credits per second, with Veo reserved for one or two hero beats.
What does 4K cost on Veo in GATA?
The 4K uplift is +30 credits per second on top of Veo's 45, so 75 credits per second. An 8-second 4K hero shot is 600 credits. Alternatively, render at standard resolution and upscale the finished scene clip at the master stage for 10 credits per second.
Veo and Gemini are trademarks of Google LLC; referenced here for comparison under nominative fair use. Third-party prices are indicative, shown in their native currency, and exclude local taxes. GATA prices are GBP excluding VAT.