Announced end dates for generative video models
Three companies in this register have announced end dates for a video model: OpenAI for Sora, Google for five Veo identifiers, and Microsoft for the two sora-2 versions it hosts. Everything else tracked here has no announced date, which is not the same as having a future. As of 2026-09-12.
| Date | What ends | Vendor | Status | Detail |
|---|---|---|---|---|
| 2025-11-12 | veo-3.0-generate-preview and the fast preview | Shutdown | Gemini API | |
| 2026-04-26 | Sora web and app | OpenAI | Discontinued | Sora |
| 2026-06-30 | veo-3.0-generate-001, veo-3.0-fast-generate-001, veo-2.0-generate-001 | Shutdown, stated as the earliest possible date | Gemini API | |
| 2026-07-15 | sora-2 version 2025-10-06, as hosted by Microsoft | Microsoft | Retired | Microsoft Foundry |
| 2026-09-24 | Sora API | OpenAI | Discontinued | Sora |
| 2026-10-15 | sora-2 version 2025-12-08, as hosted by Microsoft | Microsoft | Retirement scheduled | Microsoft Foundry |
Inclusion rule. Dates announced in public by the vendor that makes the model. A date reported only by press coverage, or inferred from a model disappearing from a menu, is not listed. Order. Chronological.
1Where the dates come from is the finding
The calendar grew when this register started reading cloud platform documentation instead of only application pages, and the shape of what it found is the point. Every dated line above was published either by the company that built the model or by a platform that hosts it for other people. Not one of them came from an application that sells video generation to a production, and applications are what most buyers are actually paying.
The temptation is to read a blank column as safety. It is the opposite: a model with no announced date is not one with a guaranteed future, it is one whose vendor has not said anything. And a date is not automatically a commitment either. Google labels its shutdown column as the earliest a model might be retired, which makes those rows a floor rather than an appointment.
2What gets a row
A date published by the company that makes the model, or by a platform stating when it will stop serving a model it hosts. Not a date from press coverage, not a date inferred from a model vanishing from a reseller's menu, and not a deprecation notice without an end date attached. Those may all be true and none of them is a commitment a production can plan against.
When a model does leave a menu without an announcement, that shows up on the app page rather than here, because the fact is about the app's list and not about the model's life.
3Entries tracked
- SceneMixer — five named tiers, model named per tier.
- LTX Studio — two house generations plus licensed models.
- invideo AI — six makers aggregated, Sora 2 still listed.
- Kling AI — two generations sold on one plan.
- Pika — a single house model across every plan.
- Runway — a credit conversion table that names each model.
- Luma — two Ray generations and a long licensed half.
- Adobe Firefly — partner models named against particular tiers.
- Hailuo AI — one model promoted, no predecessor mentioned.
- PixVerse — a house line numbered six, with five unaccounted for.
- Vidu — a current generation plus a real-time model.
- fal — other makers models priced one at a time.
- Microsoft Foundry — dated sora-2 rows and a notice period in days.
- Amazon Bedrock — three lifecycle states and months of notice.
- Gemini API — five Veo identifiers with shutdown dates.
- Wan-AI — weights published under a permissive licence.
Each of those pages lists the models the entry names and, beside each one, any end date announced by whoever makes it. The register holds sixteen entries and around seventy named model rows, and the six lines above are every published date between them.