Time-sensitive product migration
Sora Is Shutting Down: Export Your Videos Before September 24, 2026
The Sora web and app experiences ended earlier. The Sora API shutdown is scheduled for September 24, 2026. Here is the evidence-backed export checklist and a provider-neutral migration plan.
Short answer
OpenAI says the Sora web and app experiences were discontinued on April 26, 2026, and the Sora API will be discontinued on September 24, 2026. Export your content from sora.chatgpt.com/sunset, wait for the email, download the files, open a sample, make a second backup and record a manifest. For an API migration, inventory every Sora call and replace it behind a provider-neutral adapter. Do not assume a replacement has the same inputs, duration, audio, rights or pricing.
Checked September 21, 2026 against OpenAI's Sora page and OpenAI's discontinuation notice.
01 · Do this first
Export before you redesign the workflow
A shutdown creates two different jobs that are easy to mix together. The first is preservation: make sure the work you already created remains available in a form you can open, identify and use under your retention and rights rules. The second is replacement: decide how future work will be generated, edited, stored and monitored. Preservation comes first because a migration experiment should not be your only copy of the original.
OpenAI's notice says the export path is at sora.chatgpt.com/sunset. Use a small export as a rehearsal. Confirm where the email arrives, how long the request takes, what the archive contains and whether the video files open in the tools your team actually uses. Then request the broader export and keep the request record. The practical failure mode is not only losing a file; it is losing the context that tells you which file was approved, which prompt created it or which project had permission to use it.
- List every Sora workspace, project, bucket or application that contains generated videos.
- Run a small export first and confirm that the email, download and file open correctly.
- Export the library from sora.chatgpt.com/sunset and keep the export request record.
- Save original files separately from edited derivatives and social-media encodes.
- Record prompt, model, creation date, owner, rights notes and intended use where available.
- Inventory API calls, webhooks, stored IDs, queues, scripts, secrets and downstream jobs.
- Freeze new Sora generation before the deadline if a job could finish after shutdown.
- Choose a replacement by workflow requirement, not by a generic quality claim.
02 · Preserve the evidence
Build a manifest you control
A downloaded video without a manifest becomes a mystery file. Create one row for every exported item, using an internal ID that does not depend on Sora's filename. Keep the original filename, exported filename, file extension, duration, dimensions, creation date, project or owner, prompt or brief if you have it, source references, rights notes and backup locations. Add a checksum if your storage process supports it. Most importantly, add an explicit status such as verified, incomplete, duplicate or needs review.
Treat metadata as something to check, not something to assume. Run a sample and inspect the archive itself. Does it contain only rendered files, or also project information? Are dates in the expected timezone? Are variations distinguishable? Can the file be opened in a normal player and imported into your editor? If the export does not include a field that matters, capture that field separately from your own records while you still have access. Do not invent missing prompts or dates from memory.
| Field | Why keep it |
|---|---|
| Internal ID | Lets your archive survive a provider change |
| Original and exported name | Connects the file to the export |
| Creation and export date | Preserves timing and audit context |
| Prompt or brief | Makes a later recreation possible |
| Rights and consent notes | Prevents a file from losing its usage context |
| Checksum and backup | Shows which copy was verified |
03 · If you run the API
Inventory the whole dependency, not just the model name
An API shutdown rarely lives in one line of code. Search for endpoint URLs, model identifiers, SDK calls, environment variables, secret names, queue labels, job-status polling, webhooks, download handlers, retry logic, storage prefixes, dashboards and user-facing error messages. Include scripts and documentation. A provider may be called indirectly by a worker or a shared adapter, so search by both the product name and the internal abstraction around it.
Write the internal contract before choosing the replacement. For example, your application might submit a brief and references, receive a job ID, poll status, download a video, store provenance and surface a review task. The replacement adapter should satisfy that contract, while provider-specific behavior stays at the boundary. This design makes a later provider change smaller and makes failure visible. A job that times out, returns an unexpected format or is rejected for policy reasons should fail into a reviewable state, not disappear into an automatic retry loop.
04 · Choose the next workflow
Compare documented capabilities, then inspect your own clips
The CSV proposal names Veo 3.1, Kling 3.0 and Seedance 2.0, but titles and notes are research leads. The primary-source picture is narrower and more useful. Google's official Veo 3.1 update describes availability in the Gemini app, YouTube, Flow, Google Vids, Gemini API and Vertex AI, as well as vertical output and 1080p or 4K options in that update. ByteDance's official Seedance 2.0 announcement describes text, image, audio and video inputs, reference-based creation, editing, extension and 15-second audio-video output. Those are documented capabilities, not a promise that either service is available to you or is the best fit.
Start with your clip contract: input types, duration, aspect ratio, resolution, audio, character or product continuity, editing, extension, API access, regional availability, rights, provenance, retention, pricing and review process. A replacement can be excellent at generation and still be wrong for a team that needs a stable API, a particular region, an audit trail or an approved data policy. Check the current vendor documentation on the day you choose and record the page date. Do not include a price unless you have verified the current official rate card.
- 1
Define the clip contract
Write down duration, aspect ratio, resolution, input types, audio needs, reference-image rules, editing needs, extension needs, watermark or provenance requirements, and acceptable licensing. A provider that matches one feature may fail another. This list becomes the acceptance test for a replacement.
- 2
Separate assets from the Sora call
Keep prompts, reference images, audio, output files and application metadata in a provider-neutral structure. Do not bury the only copy of a prompt inside a vendor dashboard. Use stable internal IDs so changing providers does not change the identity of the project.
- 3
Create a small representative set
Choose a few clips that cover ordinary text-to-video, image-to-video, motion, dialogue or sound, continuity and an edge case. Include clips your team is allowed to use for migration testing. Do not call the set a benchmark unless you define the method and actually run it.
- 4
Translate the brief, not just the prompt
Different video systems interpret camera language, references, duration and audio differently. Rewrite the scene brief for the target provider's documented inputs. Preserve the creative intent, but mark every change in duration, framing, reference handling or output format.
- 5
Run a human review
Compare candidates on the dimensions that matter to your project: subject identity, motion, timing, text, audio, continuity, artifacts, downloadability and rights. Keep observations tied to the sample clip and provider documentation. Avoid publishing unsupported claims such as 'best' or 'always consistent'.
- 6
Move the least risky workflow first
Start with a new or low-consequence project. Keep Sora exports as the reference archive and make the replacement pipeline produce reviewable files before it touches a production queue. A migration is safer when rollback means selecting the archived original, not recreating an entire library.
- 7
Update the application boundary
Change the provider adapter, configuration, queue labels, error handling, retry rules and monitoring separately from creative logic. Remove Sora-specific assumptions only after searching for them in code, environment files, documentation and dashboards. Revoke unused credentials after the final Sora call.
- 8
Document the new runbook
Record how a person submits a job, checks status, downloads the result, handles failure, records rights and stops the queue. Include the provider's official limits and current links. Assign ownership for future refreshes because video products and pricing change quickly.
05 · Migration brief
Copy-paste prompt for a safe replacement plan
06 · Questions
Frequently asked questions
When is Sora shutting down?
OpenAI says the Sora web and app experiences were discontinued on April 26, 2026, and the Sora API will be discontinued on September 24, 2026. The API date is the urgent deadline for applications that still call the service. Confirm the current Help Center notice before scheduling a final migration because shutdown instructions can change.
Can I still export my Sora videos?
OpenAI's discontinuation notice says you can export content through sora.chatgpt.com/sunset by choosing Export, after which you receive an email when the export is ready. Start early, check that the downloaded files open, and preserve the export email or request record. Do not assume that a request submitted near the deadline will complete instantly.
What happens to Sora data after discontinuation?
OpenAI says that after discontinuation and any final export window, data associated with Sora use will be permanently deleted. That is why an export is not complete until you have downloaded it, opened representative files, made a second backup and recorded what is missing. Keep only data you are allowed to retain.
Does the shutdown affect Sora web and app users?
The web and app experiences were already discontinued on April 26, 2026 according to OpenAI's notice. The September 24 date is for the Sora API. The practical response differs: consumer users should focus on export and retention, while API users also need to inventory calls, credentials, queues, webhooks and downstream processing.
Should I export every file or only final videos?
Export the complete library if it contains work you may need to revisit, prove ownership of, or use as a reference. At minimum, preserve final deliverables, project-relevant source material, versions with different rights or approvals, and metadata you need to identify the creation. Do not discard intermediates until you know they are unnecessary and legally safe to remove.
Will the export preserve prompts and metadata?
Do not assume it will preserve every field in the form you need. Run a sample export and inspect the files, filenames, sidecar data, timestamps and any available project information. Build your own manifest from what you can verify. If a field matters, capture it separately before access ends rather than trusting a future export screen.
What should an export manifest contain?
Use an internal ID, original filename, exported filename, file type, duration, dimensions, creation date, owner or project, prompt or brief if available, source references, rights notes, destination backups, checksum and review status. Add a field for missing or uncertain metadata. The manifest is an audit trail, not a claim that every field came from OpenAI.
Which tool should replace Sora?
There is no universal replacement. Google's official Veo 3.1 material documents availability in the Gemini app, YouTube, Flow, Google Vids, Gemini API and Vertex AI, including vertical output and 1080p or 4K options in the cited update. ByteDance's official Seedance material documents multimodal inputs, editing and extension. Choose based on your access, region, rights, API terms, inputs and output requirements, then run your own small review.
Is Veo 3.1 available through an API?
Google's official January 2026 developer announcement says the updated Veo 3.1 capabilities are available in the Gemini API and Vertex AI for enterprises, and describes features such as ingredients-to-video, vertical output and 4K or improved 1080p. Availability, model IDs, quotas and pricing are separate questions. Verify them in Google's current documentation before building an integration.
What does Seedance 2.0 support?
ByteDance's official launch material describes text, image, audio and video inputs, reference-based creation, editing, extension and 15-second audio-video output. It also notes that the model is not perfect. Treat those statements as documented capabilities, not a guarantee that your clips will match Sora or that the service is available in your region or preferred API.
Should I migrate old Sora prompts word for word?
Keep the original prompt as an archive, but translate the creative brief for the new system. Model interfaces differ in duration, camera controls, reference inputs, audio, safety rules, output sizes and editing semantics. Record what you changed and why. A literal prompt transfer can preserve words while losing the intended shot.
How do I migrate an application that calls the Sora API?
Inventory every call site, model or endpoint identifier, authentication path, job status loop, retry rule, webhook, storage location and user-facing error. Add a provider adapter with the same internal job contract, then test submission, polling, download, timeout, cancellation and failure. Cut over a small queue first. Revoke Sora credentials only after the final required export and API work is complete.
Can I keep using Sora until the deadline?
OpenAI's notice gives September 24, 2026 as the API shutdown date, but deadline behavior can include disabled requests, delayed jobs or a final export window. Treat the date as a hard migration boundary. Do not schedule a production job that depends on a response arriving at the last minute, and check the official notice for changes.
Do I need to save a local copy of the videos?
Yes, if you are allowed to retain them and they matter to your work. Keep at least two independent copies, verify that representative files open and record checksums or another integrity check. Separate the archive from the working folder so an editor or migration script cannot silently replace the only original.
What if my export email never arrives?
Check the official export page again, the account email and spam or quarantine folders, then document the time and result. Avoid repeated destructive actions or assuming the absence of an email means deletion. If the official notice provides support guidance, follow it and keep the evidence needed to explain which content you requested.
Can I upload Sora exports to another video provider?
Only after checking the provider's terms, your rights in the source material, consent for identifiable people, music and voice permissions, confidential information and any restrictions attached to the original work. An export gives you a file; it does not automatically transfer every right needed for a new service or a new public use.
How should I compare replacement outputs?
Use the same brief and a declared review rubric for each provider. Score or describe only dimensions you actually inspect: framing, motion, identity, timing, audio, text, artifacts, continuity, rights signals and workflow reliability. Keep the sample, date, settings and failure cases. Do not present a small private comparison as a general benchmark.
What if none of the replacements meets my needs?
Preserve the Sora archive, identify which requirement fails, and choose a temporary workflow rather than hiding the gap. That might mean a conventional editor, stock or licensed footage, a hybrid of image animation and editing, or waiting for a provider that documents the missing capability. A clear limitation is better than a migration that breaks the deliverable or rights chain.
Are prices included in this migration guide?
No fixed price is included because video pricing, quotas, plans and access change. Check each vendor's current official pricing and API documentation on the day you choose. Separate subscription access from per-generation or per-second charges, storage, upscaling, retries and failed generations. Put the source date in your migration record.
What should I do after the shutdown?
Confirm that your application no longer sends Sora requests, remove unused credentials, close or redirect queue paths, update documentation and monitor error logs for old identifiers. Keep the archive and manifest under your retention policy. Schedule a later review of the replacement because a migration is a new dependency, not a finished investigation.
Primary sources
- OpenAI Help: What to know about the Sora discontinuation
- OpenAI: Sora 2
- Google: Veo 3.1 Ingredients to Video
- Google: Veo 3.1 in the Gemini API
- ByteDance Seed: Seedance 2.0 official launch
Product access, limits, prices and terms change. The linked vendor documentation is the authority when your account or console differs.