LLMSwaps

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

Stored work: what a shutdown does to the files

The one shutdown documented in this register ended storage as well as service: data associated with the product is deleted after a final export window passes. One application publishes the opposite policy for a withdrawn tier: renders already made are kept, with the tier that made them recorded. From 2 source pages, read 2026-09-12 to 2026-10-13; no maker pays to be listed.

The two deadlines inside one noticeA shutdown notice carries a date for the service and, usually further down and in one line, a shorter one for the material kept inside it. The second is the deadline a team with an archive is actually working to.Shutdown announcedThe notice ends theservice and, in oneline, the storagewith it.A window opensExport windowMaterial can bedownloaded, on aperiod shared witheveryone elseleaving.Window closesDeletionData associated withthe product isdeleted. Nothingfurther is offered.
Fig. 1 One retirement here has run this course end to end, and the material was deleted at the end of it.
Which entries fill the stored work columnFilled where the entry has published something in this column, hollow where it has published nothing; the count in the margin uses the same rule.Which entries fill the stored work columnStored workSoraSora — Stored work: Deleted after any final export windowSceneMixerSceneMixer — Stored work: Kept, with the tier that made each render recordedLTX StudioLTX Studio — Stored work: Nothing publishedEvery other entryEvery other entry — Stored work: Nothing published
Fig. 2 Filled where the entry has published something in this column, hollow where it has published nothing; the count in the margin uses the same rule.
What each entry has published about material stored inside the product. Recorded 2026-09-12.
EntryStored workWhat that leaves a production with
SoraDeleted after any final export windowA download period comes first, then nothing
SceneMixerKept, with the tier that made each render recordedNothing regenerated or charged by a fallback
LTX StudioNothing publishedThe published clause covers models, not material
Every other entryNothing publishedNo ending announced, so no disposal stated

Inclusion rule. A cell is filled from a shutdown notice, or a published policy for a withdrawn model, that says what becomes of stored material. Ordinary account-closure terms do not fill one. Order. The announced shutdown first, then the published policy, then the apps whose pages say nothing.

1A shutdown ends the library as well as the tool

The announcement that ended a model here also ended the place its output lived. Data associated with the product is deleted once a final export window passes, which makes the storage deadline a second date, earlier in practice than the one everybody quoted and carried in a single line near the end of the notice.

A team that treated the product as a tool lost a tool. A team that treated it as an archive lost the archive. Those are different sizes of problem, the notice does not distinguish between them, and so this column does.

2Two answers, and a run of blanks

No other entry has announced an ending, but one application has published what it does when a tier is withdrawn: sheets and segments already made keep their pixels and their record of which tier made them, versions are kept, and nothing is regenerated on the customer's behalf. That is the kinder outcome, written down before any ending rather than in the notice of one.

The blanks are still not a promise that files stay where they are. They record that the question has not been answered in public, and the one documented shutdown resolved as deletion after a window, which remains the outcome worth assuming where nothing is published.

3Getting the files out is the part a register cannot do

Recording what a vendor published is the whole job here. Moving delivered files off a vendor's account and onto storage somebody else controls is work that has to happen before an announcement, because the export window in the documented case was measured in weeks and shared with everyone else in the same position.

So the column is better read as a prompt than as an inventory. If the cell for a product you depend on is blank, that is not a finding about the product. It is a question still open while there is time to act on the answer.

4This column, entry by entry

The stored work column read one entry at a time, wherever that entry has published something here or falls silent in a way the others do not. Ordinary blanks stay on the table above.

  • Sora — the register's one filled cell: deletion once a final export window passes
  • Microsoft Foundry — requests return 410 Gone after the date, and nothing is said about material
  • Amazon Bedrock — the model leaves every region and requests fail; material is the customer's own problem
  • Gemini API — output is returned per call, so a shutdown removes the capability and reaches no files
  • Wan-AI — the files were never on the publisher's disk, so a withdrawal cannot reach them
  • fal — a meter per output unit rather than a library, so delivery is the whole relationship
  • LTX Studio — the published clause covers models, not the material made with them
  • SceneMixer — renders already made are kept, with the tier that made them recorded
  • What happens to the work
    Data associated with Sora is deleted after any final export window passesOpenAI Help Center / recorded 2026-09-12
  • Sora web and app
    26 April 2026discontinuedOpenAI Help Center / recorded 2026-09-12
  • Sora API
    24 September 2026discontinuedOpenAI Help Center / recorded 2026-09-12
  • Finished work when a tier goes
    Sheets and segments already made keep their pixels and their record of which tier made them; versions are kept, and nothing is regenerated or charged by a fallbackSceneMixer, withdrawn tier guide / recorded 2026-10-13

5Sources

Values come from the page the entry is read on: vendor announcements for endings, app pages for menus, both linked from the calendar. What counts as a value is on sourcing. Read 2026-09-12. Other fields: Notice period, Default tier. All of them: the field list.