LLMSwaps

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

A shutdown that ended the library as well

This is the filled cell in the column. The discontinuation notice states that data associated with the product is deleted once a final export window passes, so the storage deadline is separate from the interface date and arrives first. A team that treated the product as an archive lost the archive. As of 2026-09-22.

What the notice settles about material kept inside the product. Recorded 2026-09-22.
What the page is askedWhat Sora publishesWhat that leaves open
Is disposal addressedYes, deletion after a final export windowThe clearest sentence in this column
Is there a route out firstAn export window is named in the noticeIts length is the practical deadline
Which date does it attach toThe window, not the interface closureSo the earlier date is the one that bites
Where is the route publishedOn the product's own sunset pageNot repeated by anyone reselling the model

Inclusion rule. Filled from the shutdown notice itself, which is the only kind of document that has to say what becomes of stored material. Ordinary account-closure terms do not fill a cell. Order. What is stated first, then which date it attaches to.

1A tool and an archive are different sizes of loss

A team that used the product to make clips and kept the clips elsewhere lost a tool. A team that left masters inside it lost the masters. The notice does not distinguish between those two positions, and the column exists because the difference is enormous.

Read that way, the sentence about deletion is the most consequential line in the register. Every date here is about capability; this one is about material that already exists.

2The export window is the real deadline

Everybody quoted the interface closure because it is the headline date. The window for getting files out closes earlier and was carried in a single line near the end of a notice most readers skimmed.

It is also shared. Every customer in the same position exports at the same time, which is not a reason to expect failure and is a reason not to start on the last day.

Two deadlines, and the quieter one comes firstCoverage quoted the interface closure because it was the headline. The window for getting files out closes earlier and was carried in a single line near the end of the notice, which makes it the deadline that actually binds.One notice, two clocksBoth datesappearNoticepublishedOne of them isquotedeverywhere;the other isone line.MaterialdeletedExport windowclosesThe bindingdeadline foranyone whokept mastersinside.Interfacecloses24 September2026The headlinedate, and thelater of thetwo.Which one a team is on depends on where its files live
Fig. 1 Every customer in the same position exports in the same weeks, which is a reason not to start on the last day.

3Why the blanks elsewhere are not reassurance

No other entry has announced an ending, so no other entry has been forced to say what happens to the material inside it. The blanks record an unasked question, not a promise that files stay put.

One documented case resolved as deletion after a window, which is the harshest outcome a reader would have guessed. Until some entry publishes something kinder, that is the assumption the planning page is built on.

  • 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

4Sources

Read from the discontinuation article on help.openai.com, 2026-09-22. The whole entry is on Sora, and the column it sits in is on Stored work. Same column, other entries: Microsoft Foundry, Amazon Bedrock.