LLMSwaps

Announced end dates for video models, and which apps still carry them

A table of dated rows against a single notice

Two makers, two formats. One keeps a standing deprecations table where identifiers acquire dates as they are scheduled. The other published a single notice with two dates and a deletion policy. Neither names a successor for the lines it is ending. From 2 source pages, read 2026-09-12 to 2026-09-22; no maker pays to be listed.

What each page says, point by pointFilled where the entry's own page addresses that point, hollow where the page is silent on it.What each page says, point by pointGemini APISoraFormatFormat — Gemini API: A standing table, updated over timeFormat — Sora: One notice, published onceWhat a reader watchesWhat a reader watches — Gemini API: The table, for new rowsWhat a reader watches — Sora: Nothing; the notice was the eventWhat the date meansWhat the date means — Gemini API: The earliest a model might goWhat the date means — Sora: A fixed discontinuation dateSuccessor namedSuccessor named — Gemini API: No replacement column existsSuccessor named — Sora: No replacement in the noticeMaterial addressedMaterial addressed — Gemini API: Not addressed; output is returnedMaterial addressed — Sora: Deleted after a final export window
Fig. 1 Filled where the entry's own page addresses that point, hollow where the page is silent on it.
How each maker publishes the end of a video line. Recorded 2026-09-22.
On this pointGemini APISora
FormatA standing table, updated over timeOne notice, published once
What a reader watchesThe table, for new rowsNothing; the notice was the event
What the date meansThe earliest a model might goA fixed discontinuation date
Successor namedNo replacement column existsNo replacement in the notice
Material addressedNot addressed; output is returnedDeleted after a final export window

Inclusion rule. Both cells on a row come from the maker's own published pages. Coverage of either announcement is not used. Order. Format first, then what each one settles.

1A standing table is a better instrument than a notice

A table can be checked on a schedule, and a new row appearing is a detectable event. A notice has to be noticed when it is published, which for most teams means reading about it later.

What the table gives up is certainty. Its dates are described as the earliest a model might go, while the one-off notice gave two fixed dates that both arrived.

A standing table against a notice published onceA table can be checked on a schedule, and a new row appearing is a detectable event. A notice has to be noticed when it is published, which for most teams means reading about it afterwards.A standing tableA single noticeCheckableOn a scheduleOnly when publishedA new ending shows asA new rowAn announcement to catchDate meansThe earliest it might goThe day it happensSuccessor namedNo column for oneNo sentence for oneOnly one of the two also said what happens to the files
Fig. 2 What the table gives up is certainty: its dates are the earliest a model might go, while the one-off notice gave two dates that both arrived.

2Neither format made room for a successor

One page has no replacement column and the other has no replacement sentence. So on both, a reader learns that something ends and has to choose where to go themselves.

That is the shared finding across the two most date-rich makers in this register. The succession column records one named successor in total, and it belongs to a hosting platform rather than to a maker.

3Only one of them addressed the files

The one-off notice ended storage as well as service, with deletion after a final export window. The standing table says nothing about material, because output is returned per call and never held.

Those are different products rather than different policies. The stored work column keeps both readings and explains why one cell is filled and the other is structurally empty.

4The same question, put to a third entry

What SceneMixer publishes on this column, beside Gemini API and Sora. Recorded 2026-10-13.
On this pointSceneMixerSource
When a tier is withdrawnWhen a tier is withdrawn, text and image work falls back to the default tier and video to the tier the episode last used if it is still listed, otherwise the default; the price shown is the tier that will runSceneMixer, withdrawn tier guide

Inclusion rule. SceneMixer's own statements that bear on the column this pair was chosen for. Order. The statement closest to the column first.

All of its readings are on the SceneMixer entry.

  • 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
  • Named replacement model
    No replacement named (as of 2026-09-12)none in the announcementOpenAI Help Center / recorded 2026-09-12

5Sources

Both readings come from the pages the entries publish themselves: Gemini API and Sora, read 2026-09-22. The column being compared is Named replacement. Other pairs: invideo AI and Luma, PixVerse and Vidu.