You can no longer use Sora Remix as a current OpenAI workflow. Learn when Sora ended, how Remix gave way to video edits, and how to request an export of content created in Sora.
Can You Still Use Sora Remix?
You can no longer use Sora Remix as a current OpenAI workflow. OpenAI discontinued the Sora web and app experiences on April 26, 2026. Its deprecation schedule says the Videos API and the listed Sora 2 models were removed from the API on September 24, 2026.
OpenAI’s schedule lists no recommended replacement for the Videos API or the affected Sora 2 models. Consequently, the former Remix and video-editing instructions should be read as historical documentation, not as steps that can be completed in a currently available Sora product.
OpenAI still documents a way to request an export of content created in Sora. That export process—not remixing—is the practical action remaining for former users who want to recover their work.

What “Sora Remix” Meant
In the former video API, Remix referred to changing an existing video generation. OpenAI’s video-generation guide says video generations could previously be changed through the remix endpoint and directed new integrations to the edits endpoint instead.
The documented edits workflow accepted either a video ID or an uploaded video. When a video ID was provided, the API determined the model from the source video. Editing an uploaded video was restricted to eligible customers, who were directed to contact an account manager or OpenAI’s sales team.
This was a change of endpoint before the broader shutdown, not evidence that Sora Remix remains available under a new name. The later deprecation notice records the removal of the Videos API and Sora 2 models.

How the Former Video-Editing Workflow Operated
Before the shutdown, OpenAI documented sending a request to POST /v1/videos/edits with a source video and a prompt describing the requested modification. An existing generation could be identified by video ID. For an uploaded video, the request had to specify a model explicitly, and upload-based editing was limited to eligible customers.
OpenAI advised making one well-defined change per edit. Its examples included changing a subject’s color, adding a second subject, and shifting a color palette. The guide explained that a focused adjustment was more likely to retain the source video’s structure, continuity, composition, style, subject consistency, and framing while lowering the risk of artifacts.
These details explain what replaced the remix endpoint while the API existed. They are not a usable API tutorial today because the Videos API was removed on September 24, 2026.
How to Request Your Sora Export
OpenAI directs former users to the Sora sunset page. Select Export there to request an archive; OpenAI says it will send an email when the export is ready.
OpenAI recommends exporting Sora content promptly. It says users will receive an email if it can offer a final export window, so an additional window should not be treated as guaranteed. The company also states that Sora-associated data will be permanently deleted after discontinuation and after any final export period it is able to provide.
Editorial suggestion: If the sunset page remains accessible to you, request the export now. After receiving it, check that the archive contains the material important to your project and keep a separate local copy. These are precautionary recommendations, not guarantees about archive contents or future access.
Planning Revisions Outside the Former Sora Workflow
The old OpenAI guidance can still serve as a creative planning principle: define one clear modification when trying to preserve useful parts of a clip. That principle came from OpenAI’s explanation that focused edits retained more of the source while reducing the chance of unwanted artifacts.
Editorial suggestion: Write down the subject, composition, framing, and visual style you want to retain, followed by one specific change. If most foundational elements—including the subject, action, setting, and composition—need to change, consider planning a new generation instead. This is an editorial framework, not an OpenAI rule or a promise about results.
Editorial suggestion: Before selecting another service, verify in that provider’s current official documentation that it supports the editing or generation workflow you need. Do not assume that another product reproduces the former Sora endpoints or behavior.
Conclusion
Sora Remix is not a current OpenAI workflow. The remix endpoint was superseded by video edits before OpenAI removed the Videos API and Sora 2 models, while the Sora web and app experiences had already ended.
The practical recommendation is to request an export through the Sora sunset page as soon as possible if you still need content created in Sora. For later creative work, use the former one-change-at-a-time guidance only as a planning suggestion, then confirm the chosen provider’s current capabilities and access conditions in its official documentation.
Sources
- What to know about the Sora discontinuation | OpenAI Help Center
- Deprecations | OpenAI API
- Video generation with Sora | OpenAI API
Disclosure
This article was prepared with AI assistance.
Improve this guide
Report a problem or suggest the next question
Submissions enter a private editorial queue. They are reviewed and deduplicated before any public update or new page is created.
