Licences and law / Generative AI
Sora API shutdown: how to prepare a replacement workflow
An API retirement affects generation, downloads, review and delivery. Before replacing Sora, preserve the work and define what the next tool must support.
When is the shutdown scheduled?
OpenAI’s documentation sets 24 September 2026 as the removal date for the Videos API and the Sora 2 models listed in its notice. At this review date, the shutdown is scheduled; it has not yet occurred.
If your application uses that API, identify affected calls and pending tasks. Changing a model name does not guarantee a compatible migration.
Preserve the work first
Check that you have accessible copies of required outputs, authorised references and generation settings. Keep each file linked to its project.
Do not rely on a temporary provider URL as your master archive. Verify that videos open, audio is complete and editing can continue without the retired API.
Then identify the replacement functions you need: text-to-video, image references, editing, shot extension or audio generation.
Which alternatives can you assess?
Options include hosted services and downloadable models. Choose according to the workflow and the applicable terms.
Wan 2.2 publishes code and models under Apache 2.0 through its official project. LTX-2.5 offers weights under a community licence with commercial and redistribution conditions. These are examples to assess, not an exhaustive list or automatic equivalents to Sora.
Downloadable models can support production when licensing and quality permit. A paid service does not guarantee every commercial use or exclusive rights to the output.
Compare using a representative shot
| Criterion | What to check |
|---|---|
| Visual control | Reference fidelity and continuity |
| Integration | Task states, errors, downloads and retries |
| Delivery | Resolution, duration, colour, audio and format |
| Terms | Territory, permissions, privacy and rights |
| Operation | Time per accepted shot and correction effort |
Use a realistic assignment and retain rejected attempts. The best clip in a gallery does not reveal how many attempts your shot will need.
For compositing, review what EXR delivery can provide and inspect what the actual file preserves.
Test the complete replacement
Run the workflow from the initial request to the approved file. Ensure failures are visible and retries do not duplicate tasks.
Document the replacement and a continuity procedure. Our review of the Fable 5 suspension explains how to prepare a proportionate response to another interruption.
To plan the migration without stopping production, tell us which workflow depends on that API today.
Sources
Checked on September 20, 2026