Sora 2 service will stop content generation in web and app interfaces on 26.04.2026, while API access remains until 24.09.2026.

Organizations using Sora 2 in production should verify dependencies and export needed data before the web shutdown.

Key dates

The decommissioning follows a two-step timetable affecting the user-facing app and programmatic integrations separately.

• Web and mobile generation via the Sora site and application ends on 26.04.2026.
• API endpoints and programmatic access will be turned off on 24.09.2026.

What to check

Audit pipelines, scheduled jobs and internal tooling to locate any calls, wrappers or SDKs that depend on Sora 2 endpoints or tokens.

Confirm that backups include generated assets, configuration files and any metadata required for future processing or compliance audits.

Migration recommendations

Begin exporting critical content immediately from the web interface, since that channel is the first to stop functioning on the announced date.

• Identify all systems relying on the Sora 2 API and prepare replacement integrations before the API cutoff.
• Rotate or revoke credentials tied to the service after migrations complete to reduce exposure.
• Validate that archived outputs are accessible and usable by downstream processes after transfer.
• Schedule migration tasks with buffer time to allow for unexpected compatibility or performance issues.

Operational notes

Teams should prioritise exports from the app and web console ahead of 26.04.2026 and plan API migrations well before 24.09.2026.

Review service-level dependencies, including third-party integrations and internal automation, to minimise disruption during the decommissioning windows.