

Sora 2 is approaching a product cutoff, so historical generation rates are not enough for a buying decision. OpenAI ended the Sora app and web experience on April 26, 2026, and schedules the API shutdown for September 24, 2026. This guide now focuses on existing-project costs and migration. Status checked September 9, 2026 against OpenAI’s shutdown notice.
A ChatGPT subscription, an OpenAI API account, and a third-party platform are different billing relationships. Do not assume that credits or entitlements transfer between them. For remaining API usage, inspect the exact model, resolution, duration, and charge in the current provider account.
List the jobs that depend on Sora, their inputs, output requirements, and where they enter your application. Save any existing media and prompts. Test a replacement on representative scenes before switching a production workflow.
Include engineering changes, new provider charges, retries, and output review in the migration cost. There is no reliable universal multiplier for moving from Sora to another model.
Magic Hour’s API documentation is one integration reference to evaluate. Select a currently supported model and verify its parameters; another provider’s API is not a drop-in replacement merely because it also generates video.
OpenAI provides an export page and emails when the archive is ready. It recommends saving content promptly. Refer to the official discontinuation guidance for credits, refunds, and data deletion rather than relying on historical subscription claims.
Use a fixed brief, duration, resolution, and acceptance standard. Record the cost of all attempts needed for a usable output. Keep measured results separate from a hypothetical budget and do not infer long-term availability from a single successful generation.
