LLMSwaps

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

What happens to work stored inside a model that ends

The one published retirement in this register also published what happens to the material inside it: data associated with Sora is deleted after a final download window. No replacement model was named with a date. As of 2026-09-12.

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 is publishedStored workStored work — What is published: Deleted after a final windowNamed replacementNamed replacement — What is published: No date announcedEvery other modelEvery other model — What is published: Nothing published
Fig. 1 Filled where the vendor has announced something in that column, hollow where it has not.
What a vendor said would happen to work held inside a model being retired. Recorded 2026-09-12.
EntryWhat is publishedDetail
Stored workDeleted after a final windowA download period is offered first
Named replacementNo date announcedNothing published for continuity
Every other modelNothing publishedNo statement on either point

Inclusion rule. Statements published by the vendor retiring the model. What a reseller does with its own copy of the work is outside this register. Order. From what was published to what was not.

1A download window is the part that has a deadline attached

Deletion after a final window means the clock a production actually has to act on is not the end date of the model but the end of the window. Those are different dates and coverage reliably reports the first one.

For anything with material sitting inside a vendor's product rather than exported to storage, the second date is the one that decides whether the work survives. This register records it for that reason and would record it for every future retirement.

2No named replacement is a separate problem from no date

A retirement with a successor named lets a production plan a migration, even badly. A retirement with no named replacement means the question is not when to move but what to move to, and no amount of notice answers that.

Both were true here: dates were published and a replacement was not. That combination is worth noting because it is the one that leaves the most work to the customer.

3What this implies for anything held only inside a product

Material that exists only inside a vendor's account is subject to whatever that vendor publishes at retirement time, which in the one observed case was a window and then deletion. Material exported to storage is not.

That is a workflow conclusion rather than a finding about any product, and it is the only generalisable thing on this page. Everything else here is one vendor's announcement.

  • What happens to the work
    Data associated with Sora is deleted after any final export window passesOpenAI Help Center / recorded 2026-09-12
  • Named replacement model
    No date announced (as of 2026-09-12)none in the announcementOpenAI Help Center / recorded 2026-09-12

4Sources

Dates come from the vendor that makes the model; menus come from the app, and both are linked on the calendar. Read 2026-09-12. What counts as a date is on sourcing. Nearby: Notice clauses, Aggregators, One or many.