Veo 2 API Costs, End of Life & Migration: 2026 Guide

Veo 2 was billed two ways, and both are now historical. Through the Vertex API it charged $0.50 per second of generated video. So a single 30-second clip cost $15, and a batch of ten test clips ran $150 before you kept one. The advanced controls, frame interpolation and camera moves, billed at the same $0.50 rate. Consumer access came bundled inside Google's subscriptions, at $19.99 a month for AI Pro and $249.99 for AI Ultra, with a free tier that reached Veo 2 through Gemini. The API was a flat per-second meter, so the bill scaled with every second you rendered, retries included.

The trap that emptied budgets fastest was the default. Vertex generates several videos per prompt unless you tell it otherwise, which quietly multiplies the bill. If the default returned four clips and you only wanted one, that 30-second prompt cost $60 instead of $15. The fix was a single setting, capping the sample count at one before you ran anything, but the default cost you four times over until you found it. The old Veo 2 rate detail is worth reading if you are reconciling a Vertex bill.

The decisive cost now is that Veo 2 is over. It was API-only through Vertex, carried no audio track, and shut down on June 30, 2026. Anything built on it has already hit its expiry, and every clip was silent, so sound had to be added separately. For any live project you are re-platforming to Veo 3 or 3.1 regardless, where video with audio starts at $0.40 per second. So the honest cost of Veo 2 today is the migration you are already doing.

Veo 2 had no standalone free plan. It reached free users through Google's Free Access tier, which bundled Gemini Advanced, the Veo 2 model, the Flow video editor and 2TB of cloud storage. So the free route to Veo 2 was really a slice of Google's consumer stack, not a Veo product you signed up for on its own. In practice the access was often invite-gated too.

That free path is now a dead end for Veo 2 specifically. The model reached end of life in June 2026, and Google's free and paid tiers steer generation toward the Veo 3 family instead. If you are evaluating today, treat any Veo 2 access as legacy and test on a current model. For live alternatives with real free tiers, the Veo 2 alternatives page lists what the standalone tools include.

There was never a Veo 2 discount program to apply for. It carried no student, nonprofit or promo rate, because it was not sold as a standalone product. Consumer use was simply part of Google AI Pro at $19.99 or Ultra at $249.99, and API use was the flat Vertex per-second rate. The one genuine lever on the API was operational, not commercial: capping the sample count so you paid for one clip, not four.

At real volume, the usual Google Cloud commercial routes applied. A committed-use arrangement on Vertex could shave the effective rate for a team rendering steadily, and enterprise agreements bundled Vertex spend with the rest of a cloud contract. With Veo 2 now retired, those conversations only make sense pointed at Veo 3 or 3.1, which is where the migration steps below aim. Nothing about the dead model is worth negotiating.

One practical note for anyone closing out a Veo 2 project. Reconcile the Vertex bill against your intended sample count, because the multi-generation default may have quietly charged you several times over. If your invoice looks high, that setting is the first place to look before you assume the per-second math was wrong.

For a dead model, the only tactics worth listing are the ones that saved money while it ran and the one that matters now, which is leaving. There is no rep to lean on for a retired product, so these are settings and decisions rather than negotiations.

Three moves cover it, and the third is the real one.

With Veo 2 retired, there is no subscription cycle or promotion window to time. The only date that mattered was June 30, 2026, and it has passed. The single timing decision left is how quickly you migrate any workflow that still assumed Veo 2. The answer is immediately, because the model no longer generates and a new pipeline on it would be dead on arrival.

Veo 2 was one of the least flexible tools in the category even before it retired, because the price was a fixed public Vertex rate. What you could influence was operational, mainly the sample count, plus a committed-use rate at real scale. None of that survives the shutdown, so today the only live lever is what you negotiate on the model you move to.

Veo 2 is retired, so this draft is a planning note, not a haggle over a dead rate. It covers two realistic asks. One is a Google Cloud committed-use rate for the Veo 3 volume you are moving to. The second is a migration question to a standalone tool, with real prices from our catalog for context. Complete the fields, copy the draft, and send it to your Google Cloud contact or the alternative's team. A rival number gives either ask something firm to sit beside.

Each of these comes from how Vertex metered Veo 2, and every one still applies to reading an old invoice.

The useful comparison for a retired model is not a threat; it is your exit. Beyond Google's own Veo 3, the three standalone tools below still run, quoted from our catalog, and cover what most people used Veo 2 for. Trial one on your real prompts so the move is deliberate rather than forced. The wider set of live options is on the Veo 2 alternatives page.