Three identifiers ending together, none replaced
Three Veo identifiers share one shutdown date on the deprecations table, and two preview identifiers share an earlier one. No row names a successor. The newer generation exists and is not presented anywhere on that page as where the retired identifiers go. From 1 source page, read 2026-09-22; no maker pays to be listed.
| What the page is asked | What Gemini API publishes | What that leaves open |
|---|---|---|
| Is a successor named per row | No replacement column appears on the table | The table carries identifiers and dates only |
| How many video lines share a date | Three on one date, two on an earlier one | So the move is not staggered by version |
| Is the newer generation offered as the route | Not stated on the deprecations page | It is documented elsewhere, as a product |
| What the date itself commits to | The earliest a model might be retired | A floor, so the runway is not fixed either |
Inclusion rule. Read from the deprecations page for this interface, restricted to video identifiers. Product documentation for newer models is not read into this column. Order. What the table publishes first, then what it does not.
1Retiring three lines on one date is a decision about people
Staggering retirements spreads the work of migrating; collapsing them into one date concentrates it. Three identifiers going at once means every caller of any of them has the same deadline and the same week to test.
That is defensible for a platform with many customers and no successor to offer per line. It also means the register cannot describe a gradual path off this generation, because the page does not describe one.
2A table with no successor column
The shape of the page decides what can be published. This one has identifiers and dates and no place to put a destination, so the absence is structural rather than an omission in a particular row.
Compare the platform in this column that does name one: it publishes a schedule with a replacement written into the row itself. Same kind of document, one extra column, and the difference in planning value is large.
3Where the successor information actually lives
Newer identifiers are documented as products, on pages written to sell capability rather than to manage an ending. A reader can find them, and nothing connects them to the rows that are going away.
For anyone reaching these weights through an application the gap is wider still. The reseller repeats neither the dates nor the newer identifiers, so the entire migration question exists two layers above the person whose series depends on it.
- veo-3.0-generate-00130 June 2026veo-3.0-fast-generate-001 and veo-2.0-generate-001, shutdown date
- veo-3.0-generate-preview and veo-3.0-fast-generate-preview12 November 2025shutdown date
- What a date in that table commits toThe shutdown dates listed indicate the earliest possible dates on which a model might be retired
4Production that outlasts a model
Model end dates touch “Gemini API”; SceneMixer's guides describe how its pipeline treats the models it runs:
Dubbing replaces the audio of a finished clip; the picture was generated for a different line, so mouth shapes, pauses and shot length all belong to the original language. Native-language generation gives the video model the line in the target language before it renders the shot, so the performance, the pacing and the cut points are built for that language.
SceneMixer, Native-Language Dialogue vs. Dubbing in AI Video (2026): Why the Cast Should Speak the Line (read 2026-10-13)
SceneMixer writes dialogue into the script analysis, assigns each line to a shot with a speaker and a short delivery note, and the video model performs it — picture and audio generated together, so the mouth forms that sentence in the language you chose.
SceneMixer, AI Dialogue Generator (read 2026-10-13)
5Sources
Read from the deprecations page on ai.google.dev, 2026-09-22. The whole entry is on Gemini API, and the column it sits in is on Named replacement. Same column, other entries: Amazon Bedrock, LTX Studio.