Sora's back catalogue, read on the pages that remain
Sora's help page dates the app's discontinuation to 26 April 2026 and the API's to 24 September 2026, with an export offered before the data is deleted. Work made with the model still hangs on other makers' pages: StoryShort names Sora 2 on ten of the videos on its community page, each kept with its full prompt. From 3 source pages, read 2026-09-25 to 2026-10-25; no maker pays to be listed.
1What this index already records
The readings this index already holds for pages where a model name survives beside an old work, or where a date keeps a catalogue countable, each with the day its page was read.
- Community pageA community page of 24 videos
- Video cardModel named on each video: 10 Sora 2, 5 Veo 3 and 9 Wan 2.5
- FiltersFilters by model, Sora 2, Veo 3 and Wan 2.5, and a Faceless Videos filter that opens a second gallery
- Video cardThe full prompt printed with each video
- Channels tabModel named on the channel list: 16 of the 48 channels marked Veo 3 with audio
- Showcase pageA showcase page of four entries
- Showcase listMarey, Moonvalley's own model, named in the v1.0 and v1.5 titles
- Showcase listA date on each entry, the latest July 8, 2025
2What the ending notice fixes, and what it deletes
The help centre article is short and dated. It gives 26 April 2026 as the day the app closed, 24 September 2026 for the API, points to sora.chatgpt.com/sunset for exports, and says the data goes once that final window passes. The notice names no successor, which is the part a schedule has to work around: a page that named one would be a different fact from a page that does not.
Read as a whole the article is about the work as much as about the tool. Everything a production wants to keep has to leave before the window closes, and nothing in the notice extends it. This register's own rule for such a page is narrow: the dates are recorded in the company's wording and dated to the day they were read, and no coverage elsewhere is allowed to supply a date the page does not carry.
3The work that outlives the tool
A back catalogue survives wherever another page keeps showing it. StoryShort's community page is one such place: twenty-four videos, each kept with its full prompt and the name of its model, with filters by model. Ten of them name Sora 2. Nothing on that page calls itself an archive; the videos are simply there, and the model name is printed beside each one in the maker's own format.
That is what the index can offer a reader asking where everyone went. The clips made before the ending are still readable on the pages that host them, and the reading is dated, so a page that drops a model filter or reshuffles its feed will be visible as a change rather than as a fact that quietly stopped being true.
4Where a model name keeps an old clip checkable
A name beside a work is the handle that outlives the tool. Google Flow marks its channels rather than its clips: sixteen of the forty-eight are marked Veo 3 with audio, and the prompt sits beside the clip so the request can be read with it. Moonvalley goes the other way and puts the model into the title — Marey in the v1.0 and v1.5 entries — with a date on each entry, the latest July 8, 2025, so a catalogue can be counted by year.
For work made with a retired model these three habits are what remains. A card naming Sora 2, a channel marked with a model family, a title carrying its engine: each tells a reader what made the clip without asking them to trust the page's presentation. Where none of them is printed, the index records the absence, and an old work becomes anonymous on the page that kept it.
5What the threads ask now that it is gone
The material counts the name heavily even after the ending: 11,729 posts and 4,662 comment mentions over the window read, with 1,112 posts positive and 452 negative. The two posts quoted below are the shape of it — one asking what creators do now, the other asking whether anyone will miss it. Both are questions about the catalogue rather than about a replacement.
The contribution this index can make to that is not a list of successors. It is the set of pages that still show work made with the retired tool, with the day each page was read, so a reader can check the claim rather than take it. What the threads moved on to is a question the pages answer one credit at a time.
6What each maker's own pages state
| Maker | What its own pages state | Read on |
|---|---|---|
| Google Flow | Google's models: Veo 3.1 (native audio), Nano Banana, Gemini Omni; an agent and Scenebuilder | 2026-10-13 |
| SceneMixer | “Reading a clip produces a scene-by-scene script: who is there, what happens, every line of dialogue, in order.” | 2026-10-13 |
| Sora | App discontinued April 26, 2026; API discontinued September 24, 2026 | 2026-10-13 |
Inclusion rule. Rows are the makers this page reads, each on its own pages, plus one pipeline this index follows. A cell carries that maker's own wording for the point; a page that does not address the point is written as unstated rather than read as a denial. Order. Alphabetical by maker name.
| Read for each of the three | Sora, per its help page | StoryShort, in this index | Moonvalley, in this index |
|---|---|---|---|
| What is dated on the page | The app to 26 April 2026 and the API to 24 September 2026 | No date on the videos, as the register read them | A date on each entry, the latest July 8, 2025 |
| How the model name is kept | On the notice itself, naming the product that ends | Printed on each video: ten of the twenty-four name Sora 2 | Written into the titles: Marey in the v1.0 and v1.5 entries |
| What the page says happens to the work | An export is offered before the data is deleted | Kept on the community page, each with its full prompt | Listed by title on a showcase page |
| Where this reading was taken from | The help centre article | The community page | The showcase page |
Inclusion rule. Cells are what each page prints, taken from the readings this index holds and dated in the rail. A point a page does not carry is written as unstated rather than filled in from a maker's other pages. Order. As the points are listed above.
7What the threads counted
One name from the material behind this column, counted after the ending rather than before it. The posts below are what a retired tool leaves behind in the threads: questions about the work that still exists, not about what will replace the tool.
| Name | Posts | Comment mentions | Positive | Negative |
|---|---|---|---|---|
| Sora | 11729 | 4662 | 1112 | 452 |
Inclusion rule. Names the collection counted and that this page is about. The tallies come from the same posts, and a post arguing with itself can land in both. Order. Descending by posts.
Sora is dead — what do creators do now?
r/SoraAi, collected 2026-10-14
Will you miss making Sora videos?
r/SoraAi, collected 2026-10-14
8When the other one is the better fit
- The record of what was made matters more than the tool — A clip named Sora 2 on a community page is a reading of the model as much as of the maker, and the index keeps it while the page keeps the clip.
- The export has already been taken — Work that left before the final window keeps its pixels; the help page's own line is that the data is deleted afterwards, which is a deadline rather than a change of product.
- An older series has to sit beside a newer one — Readings that print a model name — a filter by model, a title that names its own engine — let a work from the retired line be compared with a current one on the same page.
Written for the question counted in the material as "What did everyone move to after Sora disappeared?" Beside it: Kling against what users post and DramaSo's output.