The Sora 2 API Shut Down September 24: A Working Migration Map for Video Pipelines

On September 24, 2026, OpenAI removed the Videos API and with it the sora-2 and sora-2-pro model aliases. Developers were notified on March 24, so the runway was six months, and it has now run out. The consumer Sora app had closed before that.

The unusual part is one cell on OpenAI's deprecations page. Where every other retired model lists a recommended replacement, the Videos API row shows a dash. No successor, no migration guide, nothing. If you built an ad-creative or UGC pipeline on Sora 2, the vendor's official answer to "what now?" is blank space, and the top of the search results is already filling with aggregators racing to sell you their own proxy.

We run three of the surviving production video APIs (Seedance 2.0, Seedance 2.5, and MiniMax H3) behind one product, and we have already published working guides for two of them. This is the migration map we would have wanted: not a listicle of alternatives, but which engine matches which property of the pipeline you actually built.

First, do not plan around Azure

The obvious dodge is "keep calling Sora through Azure AI Foundry." Two things argue against it. The Azure portal listed a retirement date of June 2, 2026 for its sora-2 model version, earlier than OpenAI's own shutdown, not later. And developer threads through the summer show the deployment gateway rejecting sora-2 by name, including a documented catch-22 where the validator refuses the deprecated model while the docs still describe it as preview. An escape hatch that is closing from both ends is not a migration plan.

Inventory what your pipeline actually uses

Sora 2, as the API stood at the shutdown notice, had a specific shape: clips up to 20 seconds (OpenAI's March 12 update added 16- and 20-second generations, and extensions that grow a video to 120 seconds); portrait and landscape sizes, with 1080p on sora-2-pro; one reference image in as the first frame, plus up to two reusable characters; an edits endpoint for existing videos, with uploaded videos limited to eligible customers; synchronized speech and sound generated with the video; strict input moderation, especially around real people; credentialed, watermark-carrying output.

Your migration is about those properties, not the logo. Write down which ones your pipeline depends on, because no surviving engine matches all of them exactly, and the mismatches are where rebuilds go wrong.

The map

Prices are list rates for the vendor's cheapest qualifying tier, converted where billing is in RMB; token-metered engines vary with resolution and input. The fine print matters more than the table, and that is the next section.

Choose MiniMax H3 if Sora was your exploration engine: it is the cheapest per finished second by a wide margin, and 768P is fine for feed placements. Its ceilings are hard (15 seconds, no 1080p), and it has the sharpest edges (below).

Choose Seedance 2.0 if you need 4K (listed on BytePlus), explicit vertical ratios, or shots longer than one call via reference-video continuation. This is our workhorse, and in Riffkit you can pick up to 1080p on it.

Choose Seedance 2.5 when the thing you are replacing is Sora's coherence: a 30-second continuous take has no seam to hide, which below 15 seconds buys you nothing but past it changes the product.

The traps that are not in any rate card

These are the ones that cost us real renders, and every one applies to a Sora migrant.

Input video is metered. Hand Seedance a reference clip and the token formula counts the input duration at your output's dimensions. Hand H3 a reference clip and it bills the clip's own duration at the output rate, on top of the output. Sora never charged you for what you sent in; both of these do, and a budget model that ignores it understates every continuation.

Continuations cost more, not less. On our production traffic, a continuation segment consumes about 2.28× the tokens of an opening segment; even at the cheaper reference-video rate that nets out to roughly 1.39× the cost per second. If you are replacing 20-second Sora clips with 15-plus-continuation, price the second segment correctly.

H3 silently drops contradictory parameters. First/last frame and the reference family are documented as mutually exclusive, but the API does not enforce it: send both and the request is accepted, billed, and one group is discarded with no warning field. Validate the exclusivity yourself.

Ratio comes from the input frame. In image-to-video mode H3 ignores the ratio parameter entirely and follows your image. If your Sora pipeline requested portrait output from square product shots, crop upstream or you will ship square ads.

Moderation runs on inputs, and stills are judged harder than video. Both vendors screen what you send in; a rejection surfaces as a failed generation, not a validation error, and retrying the identical request will not clear it. Real-person images get the strictest read. If Sora's moderation was your baseline, re-run your actual asset library through the new engine before you commit traffic.

Deeper dives, from the same production data: our MiniMax H3 working guide and the three costs every Seedance-vs-H3 comparison misses.

A six-step migration checklist

1. Inventory properties, not vendors: durations, ratios, audio languages, reference inputs, moderation exposure.
2. Map your durations. Everything ≤12s fits any engine; 13–15s fits Seedance 2.0 and H3; longer, including Sora's 16- and 20-second clips, means segmentation and seams, or Seedance 2.5's single take.
3. Move ratio decisions upstream. Crop the input frame to the shape you want before the API call; do not trust the parameter.
4. Re-run moderation assumptions with your real assets, especially anything with a face.
5. Re-price with input metering and retries in the model, not just the per-second headline.
6. Keep the seams provider-neutral: segment planning, asset URLs, polling, and billing should treat the engine as a config value, because this is not the last shutdown you will migrate through.

The shortcut, if you would rather not rebuild

We did this the long way so the pipeline you rent can be boring: Riffkit runs Seedance 2.0, 2.5, and MiniMax H3 behind one form. You hand it a short video that already worked (the thing most Sora ad pipelines were built to imitate), and it rebuilds that video's formula around your product, handles the segmentation, the reference plumbing, the ratio rules, and the engine choice, and shows you the per-second rate before you render. The engines on the pricing page are the same ones in the table above, because they are the ones that survived.