Sora 2

What happened

The Sora 2 shutdown is the cautionary tale of the current video generation market, and it is worth studying precisely because Sora was once the most famous name in the field. OpenAI has now wound the product down: the web and app experiences were discontinued on 26 April 2026, and the API is scheduled to follow on 24 September 2026. The plain instruction for anyone reading this is not to build new pipelines on it. Whatever Sora 2 represented at launch, it is now a system on a published path to retirement, and treating it as a foundation would be a mistake.

The economics

The economics go a long way towards explaining the Sora 2 shutdown. API pricing had been $0.75 per second, which is roughly five times the cost of Veo 3.1 in fast mode for comparable quality. In practical terms a 30-second clip cost about $22.50, a figure that becomes hard to defend the moment a buyer lines it up against the alternatives. When a rival delivers similar output at a fifth of the price, fame is not enough to hold a customer, and the market moved accordingly. Price discipline, more than any single technical failing, is the thread that runs through this story.

Where to migrate

For the teams affected, this page is best read as a migration guide. A good many organisations prototyped on Sora simply because it was the name everyone had heard of, and those teams now need a clear exit before the API date arrives. The honest recommendation depends on what the team was using Sora for. For Western compliance, where a familiar corporate supplier and built-in provenance are the priority, Veo 3.1 is the sensible destination. For cost-sensitive work, Kling 3.0 offers the best price-to-quality ratio on the board. For sheer output quality, particularly image-to-video, Seedance 2.5 leads the field. Most teams will find one of those three fits the use case they originally brought to Sora.

Timing the exit

Timing is the practical concern. The web and app closures on 26 April 2026 have already happened, so any workflow that relied on them has stopped, but the API remains live until 24 September 2026, which gives engineering teams a finite and now short window to port their work. Planning around the Sora 2 shutdown means testing a replacement, rebuilding the integration and validating output well before that date, rather than waiting for the endpoint to go dark. A deprecation notice is a deadline, and treating it as anything softer risks an outage that could have been avoided.

The wider lesson

There is a broader lesson in all of this, which is why the page carries the weight it does. Sora demonstrated that being early and being famous count for very little once the underlying economics stop working. OpenAI arrived with enormous attention and a genuinely striking early model, yet within a short span it was undercut on price and overtaken on quality, and the product could not sustain the position that publicity alone had won it. For anyone choosing a video vendor today, the Sora 2 shutdown is a reminder to weigh price, quality and longevity together, and to be wary of standardising on a tool for its brand rather than its numbers.

Where this leaves the field is instructive. The exit of a marquee name does not shrink the market; it consolidates it around the vendors that got the fundamentals right, and it hands their share to the Chinese leaders and to Google’s compliant Western default. For teams still on Sora, the task is immediate and unambiguous: pick a successor, migrate before September, and treat the episode as a lesson in choosing on substance. For a side-by-side view of the alternatives, our AI video models hub tracks all of them, and the wider AI section follows the labs involved.