Which models Gemini API carries

The Gemini API (ai.google.dev) lists five Veo model identifiers with shutdown dates: three generally available ones dated 30 June 2026 and two previews dated 12 November 2025. The page calls those the earliest possible dates rather than the actual ones. As of 2026-09-12.

Inclusion rule. Models the app names on its own public pages. A model the app does not name is not listed, and an end date is recorded only when the vendor that makes the model has announced one. Order. As the app orders them on its own page.

1How many models each application names

Inclusion rule. Entries whose own pages name a model, a version identifier or a lifecycle state. House tier names with no model behind them are not counted. Order. Alphabetical by entry name.

Inclusion rule. Counted only where the vendor that makes the model has announced a date in public. A date reported by press coverage alone is not counted. Order. Alphabetical by entry name.

2A date that means not before rather than on

The table states that the dates it lists are the earliest a model might be retired, and that the exact date will be communicated with advance notice. That single sentence changes what every row means. These are not the two dates a production needs; they are one of them, a floor, with the ceiling left open and the notice promised but never counted in days.

This register records the floor because it is published and the notice as unstated because it is not quantified, which is a distinction worth holding on to. A promise of advance notice with no number is closer to the blanks elsewhere in this register than it is to the sixty and thirty days committed by Microsoft Foundry.

3Retiring a version by identifier, not by name

These rows are identifiers rather than product names, which is the form retirement notices almost always take, and it is why this register copies version strings wherever it can find them. A customer of an application that advertises Veo cannot tell from that word which of these five identifiers is being called, and therefore cannot tell whether a dated shutdown touches their work at all.

Several entries here resell this family. Two of them name a version number on the page a buyer reads, which at least narrows the question; one names the maker with no version. The register keeps those rows as the pages state them and links the makers' dates back here, which is the whole reason application menus and maker dates live on separate pages: see how the same family reads from the reseller side at fal.

4Read column by column

This register reads Gemini API along notice period, named replacement, stored work, default tier, lifecycle states and ending early. One page each.

• Notice period — notice promised in words and never converted into a number of days
• Named replacement — three video identifiers shut down on one date, with no successor named beside any of them
• Stored work — output is returned per call, so a shutdown removes the capability and reaches no files
• Default tier — an alias moves and a pinned identifier does not, and the choice is the caller's
• Lifecycle states — being listed on the deprecations table is itself the state, and the date is separate
• Ending early — a date described as the earliest, so it is a floor that can quietly become later

5Sources

Menu taken from the deprecations page on ai.google.dev, 2026-09-22. Any end date beside a model comes from whoever makes it, and is listed on the calendar.

• 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
• 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
• How many days of advance notice
  No date announced (as of 2026-09-12)promised but never countedGoogle, Gemini deprecations / recorded 2026-09-22