LLMSwaps

Which model each app runs today, and when it last changed

What the Gemini API promises before a Veo model stops

Google publishes shutdown dates for five Veo identifiers and describes them as the earliest possible dates on which a model might be retired. Advance notice is promised in words. No number of days is attached to that promise, so this register records the period as unfilled rather than as generous. As of 2026-09-22.

What has been announced, entry by entryFilled where the vendor has announced something in that column, hollow where it has not.What has been announced, entry by entryWhat Gemini API publishesWhat Gemini APIpublishesWhat that leaves openWhat that leavesopenAre dates publishedAre dates published — What Gemini API publishes: Yes, five Veo identifiers carry oneAre dates published — What that leaves open: Two are preview lines already past their dateHow much notice before one arrivesHow much notice before one arrives — What Gemini API publishes: Not stated in daysHow much notice before one arrives — What that leaves open: Advance notice is promised without a figureWhat the published date meansWhat the published date means — What Gemini API publishes: The earliest a model might be retiredWhat the published date means — What that leaves open: So a date can move later without a correctionIs a successor named beside the da…Is a successor named beside the dateIs a successor named beside the date — What Gemini API publishes: No replacement is named for the video linesIs a successor named beside the date — What that leaves open: The newer generation is not stated as the route
Fig. 1 Filled where the vendor has announced something in that column, hollow where it has not.
What the deprecations page commits to, and where the commitment stops. Recorded 2026-09-22.
What the page is askedWhat Gemini API publishesWhat that leaves open
Are dates publishedYes, five Veo identifiers carry oneTwo are preview lines already past their date
How much notice before one arrivesNot stated in daysAdvance notice is promised without a figure
What the published date meansThe earliest a model might be retiredSo a date can move later without a correction
Is a successor named beside the dateNo replacement is named for the video linesThe newer generation is not stated as the route

Inclusion rule. Read from the deprecations page for the interface, restricted to the video identifiers. Dates for text and image models on the same table are not counted in this column. Order. What is published first, then what the publication does not settle.

1A table full of dates and no period

This entry is the odd one in the column: it publishes more dates than anybody else and no notice period at all. The two are not the same commitment, and having the first makes the absence of the second easier to miss rather than harder.

A reader who finds a dated row will feel informed and stop looking. The question that decides a migration plan is how much warning arrives before a row appears, and that question has no answer on this page.

2Earliest possible is the opposite of a deadline

The page describes its dates as the earliest on which a model might be retired. That makes each one a floor rather than a ceiling: work can safely be scheduled up to the date, and nothing says the model stops there.

Read carelessly it looks like reassurance. In planning terms it is a date that cannot be relied on in either direction, which is why the register keeps the wording verbatim instead of summarising it as a shutdown date.

A published date that is a floor, not a deadlineThe page describes its shutdown dates as the earliest possible dates on which a model might be retired. A floor can move later without any correction being published, so the date cannot be relied on in either direction.Read as a deadlineRead as publishedWhat the date meansAccess ends on this dayAccess ends no earlier than this dayCan it moveNoLater, with nothing to announceWhat you planA migration finished by thenA migration ready by then, heldIf it movesWasted urgencyExpected, and already budgetedSame row in the table, two different commitments
Fig. 2 Recorded verbatim rather than summarised as a shutdown date, because the two readings produce different migration plans.

3Where that leaves a production two layers down

Several applications in this register resell these video lines. None of them repeats the dates, and none inherits the promise of advance notice, so the information exists at the layer that publishes it and travels no further.

That is the structural finding rather than a criticism of anyone. A customer of an app is not a customer of this interface, and a promise made to developers is not a promise made to the people whose series depends on the same weights.

  • How many days of advance notice
    No date announced (as of 2026-09-12)promised but never countedGoogle, Gemini deprecations / recorded 2026-09-22
  • What a date in that table commits to
    The shutdown dates listed indicate the earliest possible dates on which a model might be retiredGoogle, Gemini deprecations / recorded 2026-09-22
  • veo-3.0-generate-001
    30 June 2026veo-3.0-fast-generate-001 and veo-2.0-generate-001, shutdown dateGoogle, Gemini deprecations / recorded 2026-09-22
  • veo-3.0-generate-preview and veo-3.0-fast-generate-preview
    12 November 2025shutdown dateGoogle, Gemini deprecations / recorded 2026-09-22

4Sources

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 Notice period. Same column, other entries: LTX Studio, SceneMixer.