OpenAI Killed Sora — Switch to Runway or Kling Now

Sora is dead. Not deprecated, not sunset-with-a-successor — dead. The API went offline September 24, 2026, OpenAI deleted all account data, and the recommended-replacement column on the deprecation page is empty. If you were building anything on Sora, there is nothing left to export and no fallback inside OpenAI’s ecosystem. You need to move today.

What Happened

OpenAI announced the deprecation on March 24, 2026 — six months notice. The Sora web and mobile app went dark first, on April 26. The API followed on September 24, removing every Sora 2 model alias: sora-2, sora-2-pro, sora-2-2025-10-06, sora-2-2025-12-08, and sora-2-pro-2025-10-06. Every Videos API endpoint now returns HTTP 410 Gone.

OpenAI offered a narrow export window at sora.chatgpt.com/sunset before shutdown. As of September 24, that window is closed and the data deletion is permanent — no recovery path, no customer support workaround, no grace period.

The official line from OpenAI is that the Sora research team is “refocusing on world simulation research to advance robotics.” The real story is in the unit economics: Sora cost approximately $1 million per day to operate while generating roughly $2.1 million in total revenue across its entire commercial run. Active users dropped from a peak near 1 million to under 500,000. OpenAI also terminated a $1 billion Disney licensing deal — a partnership that would have brought Marvel and Pixar characters into AI-generated clips — as part of the shutdown. When you’re burning compute at that rate before an IPO, you cut the product and free the GPUs for coding and enterprise AI where the margins actually work.

Why It Matters

The Sora shutdown isn’t just a product death — it’s a signal about where frontier AI labs are allocating scarce compute. Consumer creativity tools lost to enterprise software. Video generation, despite the hype, never found a repeatable use case that justified the infrastructure cost at OpenAI’s pricing tier.

For creators and developers, the practical implication is that building on any single AI video provider — especially one backed by a lab with a diversified product roadmap — carries platform risk that purpose-built video tools don’t. Runway and Kling have built their entire businesses around video generation. It’s not a product line they can kill to free compute for a more profitable segment.

The second-order effect: Sora’s user base — even the reduced 500,000 active users — now needs somewhere to go. Runway and Kling are the two tools with the infrastructure, pricing, and feature parity to absorb that migration. The duopoly just got stronger.

The Take

Runway is the professional pick, full stop. The Standard plan runs $15/month (or $12/month billed annually) for 625 credits and includes Gen-4.5 access with watermark-free exports. Before you pay anything, the free tier gives you 125 one-time credits — enough to test a handful of clips and verify Gen-4.5 output quality fits your workflow. A five-second Gen-4.5 clip costs 60 credits, which works out to roughly $0.60 at top-up rates on Standard. That’s higher per clip than Sora Standard was at scale (approximately $0.50 for a five-second clip), but Runway has a track record, an API that isn’t going anywhere, and a proven professional user base that Sora never built.

If cost is the constraint, use Kling. The Standard plan renews at $8.80/month for 660 credits. Kling 3.0 supports physics-accurate motion, multi-shot storytelling across up to six connected shots, and 4K 60fps output. A five-second 720p clip runs approximately $0.20-0.27 in credits — materially cheaper than Runway at the same output length. The first month is $6.99 if you want to test it at minimal cost before committing to renewal.

The persona split is straightforward: if you’re producing video for clients, managing multiple projects, or need reliable API access, go Runway. If you’re a solo creator generating content for your own channels and Sora’s cost was always a friction point, go Kling and keep more margin.

One thing not to do: wait. The community reaction to the Sora shutdown was telling — a former ML engineer on Hacker News noted that Sora “never got a technical report, just demos and a pricing page,” which is how you know a product wasn’t defensible long-term. Multiple Reddit users in r/artificial admitted they’d already migrated to Kling months ago for actual work and were barely using Sora. The migration is already happening. The creators who move now will have their workflows rebuilt before the inevitable traffic spike from everyone who waited.

Sora’s shutdown is also a reminder to audit your stack for any other tools where the core product is a side project for a larger company. If AI video generation matters to your output, it belongs on a platform where it’s the whole business — not a compute line item that gets cut when the IPO roadshow starts.