Sora API Shutdown: A Video Portability Checklist for Studios

OpenAI shut down the Sora API on September 24, 2026, four days before this was published, following the app and website's closure back in April. If your studio has ever generated a project film with Sora, or any AI video tool, the Sora API shutdown is a concrete reason to stop treating a vendor's library as storage. Below is what happened, why it matters even if you never touched Sora, and a short checklist for keeping every project film portable.

Key takeaways

• OpenAI closed the Sora app and website on April 26, 2026, then shut down the API on September 24, 2026; unexported content is deleted once the deadlines pass.
• The shutdown shows that any AI video tool's library, no matter which company runs it, is not a permanent archive.
• A short routine — saving your source images, any prompts and seeds, and the finished exported file — is enough to keep a project film portable.
• Read a vendor's terms for language about discontinuation, sunset dates or data deletion before relying on its library as your only copy.
• Favor tools that hand you a finished file you own outright, so a policy change at the vendor can't strand a client's video.

What happened with the Sora API shutdown, and when

OpenAI carried out the Sora shutdown in two stages. The consumer app and website closed first, on April 26, 2026; the developer-facing API followed on September 24, 2026, five months later, ending programmatic access entirely, according to the-decoder.com's reporting on the announcement. A thread on OpenAI's own developer forum confirms the same date from the other side of the cutoff: a post in the deprecations section states plainly that "the Sora API will be discontinued on September 24, 2026".

OpenAI's guidance to users was direct: download your content before the cutoff dates, since videos and images could be exported straight from the Sora library, and "once all deadlines pass, user data gets permanently deleted," per the-decoder.com. That is the detail worth sitting with. This was not a quiet retirement with no notice — OpenAI announced both dates and told people how to export — and unexported work was still deleted on schedule.

OpenAI's shutdown notice did not spell out a reason, according to Wikipedia's article on the Sora model, which describes the company redirecting resources toward coding tools and enterprise products while keeping Sora alive internally as a research effort into world models. The same article cites reporting that points to roughly one million dollars a day in compute costs and a user base that peaked near a million before falling under 500,000. Whatever combination of those factors drove the decision, the pattern is the one to remember: a product can be popular enough to cover a major AI lab's homepage and still be gone within a year of its most-discussed release.

Why this matters even if your studio never used Sora

Treat the Sora API shutdown as a preview, not a one-off. It is a reminder that even a well-funded, high-profile vendor can retire a product outright, on a schedule it sets, with real users depending on it.

Access terms shift in smaller ways too, on a shorter timeline, from vendors that aren't shutting down anything. Wan 3.0's August 24, 2026 launch moved the model to closed weights, a change from the open releases Alibaba had shipped before it — proof that a tool's terms of access can move even when the product itself is thriving. Between an outright shutdown and a licensing change, the lesson for a studio is the same: don't build your archive strategy around any one vendor's continuity.

For a design studio, a project film is often the only moving record of a space — a hillside house before a renovation, a clinic interior mid-fit-out, a coastal retreat concept that never got built. If the only copy sits inside a discontinued tool's library, replacing it does not mean switching vendors. It means starting the project over from the source images, if you still have them, and generating an entirely new film that will look and move differently from the one that shipped on your website, on a proposal deck, or in a client's inbox.

A short archive routine for every AI project video

Build this into the same step where you download a finished film, not as a separate task for later:

1. Create one folder per project film, named for the project and the date the film was generated, in storage you control — cloud drive or local, either works, as long as it doesn't live only inside the vendor's account.
2. Save the source images you uploaded — renderings, drawings or photographs — even though the vendor also stores them, since your own copy doesn't depend on that account staying open. Choosing the six best images for a project video covers how those get selected in the first place.
3. Download the finished file the moment it's ready, not "when there's time." A shutdown or sunset notice turns "when there's time" into "too late," and Sora's own export window shows how narrow that gap can be.
4. Record the prompt and seed, if the tool uses one. Most general-purpose and architecture-specific tools work from a prompt box you can copy and save. A done-for-you finished-film service like Arch2Video has no prompt box to record, since its AI director plans and sequences scenes automatically from your six images; for that kind of tool, the source images and the exported file are the two things worth keeping.
5. Log the tool name, plan and generation date somewhere outside the vendor's dashboard — a single spreadsheet row is enough — so you can find the film again even if that dashboard changes or disappears.
6. Keep two copies of the finished file, one local and one cloud-synced, so a single lost drive or expired login isn't the only thing standing between you and a client's video.

Reading a vendor's terms for a sunset clause

Before you commit a real project to any AI video tool, read its terms page for three things: whether it commits to any notice period before discontinuing a product or feature, whether you can export a finished file at any time rather than only within a special window, and what happens to your data after an account closes or a service ends.

This is not legal advice, and a terms page can be dense; if a project represents significant budget or a client relationship you want to protect, it is worth having someone who reads SaaS agreements for a living look at the deletion and ownership language before you rely on it. Choosing an AI video generator for architecture has a fuller checklist for commercial terms, training-data use and ownership questions to ask before you subscribe to anything.

Choosing tools that hand you a file you own

Sora's API was built for developers integrating video generation into their own products, which put the responsibility for storage on whoever built on top of it. Tools aimed at studios directly work differently: the normal workflow already includes downloading a finished file, so portability is less about remembering to export and more about what happens to that file once you have it.

Arch2Video's own terms are a useful example of what to check for in any tool: you keep ownership of the images and logos you upload, files are used only to create and deliver your video, and — subject to payment and the terms — you can use and distribute your generated videos for lawful personal or commercial purposes. Videos and project files can also be deleted from your account whenever you choose, which is a different thing entirely from data being deleted on a vendor's schedule whether you're ready or not. How Arch2Video turns six images into one film walks through the process end to end, from upload to the finished 1080×1920 MP4 delivered by email.

Whichever tool you use, treat "can I get a file I own out of this, on my own timeline" as a real evaluation question, not an afterthought you'll deal with if the vendor ever announces a shutdown.

If a project is already stuck behind the Sora shutdown

If your studio generated a film through Sora and didn't export it before September 24, 2026, OpenAI's stated policy is that the content is permanently deleted once the deadlines pass, with no recovery path described in the shutdown notice. Check your account email now for any mention of a final export window, since OpenAI indicated one might still be offered with advance notice even after the main deadline. If the project still needs a film for an active marketing push, the practical move is to go back to the original source images — renderings, drawings or photographs — and generate a fresh film in a tool that is still available, budgeting for the fact that a new generation will not look identical to the one you lost.

Frequently asked questions

What exactly happened with the Sora API shutdown?

OpenAI closed Sora's app and website on April 26, 2026, then shut down the API on September 24, 2026, ending both consumer and developer access. OpenAI told users to export videos and images directly from the Sora library before the cutoff dates, and said that once all deadlines passed, remaining user data was permanently deleted.

Why did OpenAI shut down Sora?

OpenAI's own shutdown notice did not give a specific reason, according to Wikipedia's account of the discontinuation. Later reporting pointed to resources shifting toward coding tools and enterprise products, plus a reported cost of roughly one million dollars a day to run Sora and a user base that fell from about a million to under 500,000.

Does this mean my studio should stop using AI video tools for project films?

No. It means treating any vendor's library as temporary rather than as a backup, and keeping your own copies of the source images and finished file, the same way you wouldn't trust a single hard drive with a project's drawings. Well-funded tools can still shut down or change terms; the practical response is keeping your own archive, not avoiding the category.

How can I tell if a tool I already use might shut down like this?

You can't predict a shutdown, but you can read its terms page for language on data retention, deletion rights and advance notice, and watch for changes to its roadmap, pricing or licensing. Wan 3.0's shift to closed model weights at its August 2026 launch shows terms can change without any shutdown at all, which is why an archive routine matters regardless of which tool you're using.

What should I save from a finished-film service that has no prompt box, like Arch2Video?

Save the source images you uploaded and the exported film once it arrives by email; those are the two things worth keeping, since a done-for-you service plans and directs the scenes automatically rather than working from a prompt you'd otherwise record. Arch2Video also lets you keep ownership of your uploaded images and delete a project from your account on your own schedule, rather than a vendor's.