Sora’s not working because Sora doesn’t exist anymore.
OpenAI shut down the Sora app on April 26, 2026. The standalone site is offline. The ChatGPT integration was pulled. If you’re hitting a blank page, a redirect to OpenAI’s homepage, or a message saying Sora is no longer available — that’s accurate, not a local issue.
I know that’s not the troubleshooting answer you were expecting. But it’s the correct one.
This guide covers what happened, the specific errors users hit during Sora’s run (useful if you’re still on the API before its September 2026 sunset, or just trying to make sense of what went wrong), what OpenAI did and didn’t replace it with, and which AI video tools are actually worth using right now.
What Happened to Sora
Quick timeline for context:
- December 2024: Sora opened to Plus and Pro subscribers after a long research preview period
- September 2025: Sora 2 released, with improved motion quality and audio features
- March 24, 2026: OpenAI announced the shutdown
- April 26, 2026: Sora app goes offline. Consumer access ends.
- September 24, 2026: Sora 2 API deprecated. Developer access ends.
The reported reasons: infrastructure costs that didn’t pencil out, user retention that dropped sharply after the initial launch wave, and a sustained backlash over deepfakes and nonconsensual imagery of public figures that OpenAI kept patching after the fact. A $1 billion Disney partnership built around Sora collapsed with it, before any money changed hands. OpenAI redirected resources toward its coding and enterprise products. The video experiment — in its Sora form — is over.
Video generation did not move somewhere else inside OpenAI. Sam Altman told staff that both the app and the developer API were being discontinued, with no plans to integrate the video generator into ChatGPT — the ChatGPT integration OpenAI had previously signaled was scrapped along with the app. What’s left is internal research on world models, not a product you can use. The Sora brand, the standalone app, and the dedicated tooling are gone.
The Errors Users Hit Before the Shutdown
If you’re on the Sora API before the September 24 deprecation, or you’re trying to understand a project failure from earlier this year, here’s a record of what users were reporting. All of these come from OpenAI’s developer community, Adobe’s community forums (which integrated Sora 2 via API), and user complaint threads from 2025 through early 2026.
“Something Went Wrong. Please Try Again Later.”
The most consistently reported error across Sora’s entire lifespan. It showed up in November 2025, peaked in February and March 2026, and became near-constant in the weeks before the shutdown.
Users described it in Adobe’s community forums as: every generation attempt failing with a generic message, no error code, no useful debugging information, no content produced. Multiple threads in a single week. The error was masking everything from content policy blocks to capacity failures — the UI just surfaced one unhelpful message regardless of the underlying cause.
Workarounds people found, with varying success:
- Wait 15-30 minutes and retry
- Simplify the prompt significantly
- Switch to a different aspect ratio or lower resolution setting
- Clear browser cache and reload
None were reliable. During March 2026 especially, this error appeared to be a sign that the service was being wound down — not a fixable bug on the user’s end.
Waitlist and Queue Errors (Late 2024–Early 2025)
When Sora first launched to paying subscribers in December 2024, demand blew past capacity almost immediately. OpenAI had to pause new Sora account creation within days of the launch. Users in some regions found video generation unavailable even with active Plus or Pro subscriptions — a frustrating situation for people who’d specifically upgraded to get Sora access.
Practically, there wasn’t a fix. Regional and capacity-based lockouts were OpenAI’s call. Demand cooled over the following months and access expanded, but the initial rollout was rough.
Content Policy Refusals
Sora’s content filter was strict. A user on OpenAI’s developer community described the experience well: prompts they’d used to create 60+ videos were suddenly flagged for violations, with no explanation of what changed.
The filter’s known trigger categories, based on user reports:
Real people’s names and likenesses. Any celebrity, public figure, or identifiable person in a prompt would get blocked. This wasn’t always explicit — users discovered it through trial and error.
Realistic misleading scenarios. Anything that looked like it could produce fake news, deepfake material, or realistic false representations of events. The filter was sensitive here, sometimes catching vague prompts that weren’t intended that way.
Graphic violence. Even relatively mild action sequences triggered it in some cases. The threshold wasn’t clearly defined or consistently applied.
Brand references. Some brand names in prompts produced blocks — inconsistently and unpredictably.
The usual workaround was rephrasing toward abstraction and fiction. “A person speaking at a podium” instead of a specific name. “A car collision in a stylized action film” instead of a realistic accident. Users who figured out the filter’s logic got through it. Users who didn’t kept hitting walls without understanding why.
What made this especially frustrating: the same prompt would sometimes pass on the second or third try with minimal changes. Inconsistency was one of the top complaints in user threads.
Video Generation Stuck or Spinning
Generation would start, the spinner would run, and then nothing would deliver. Could be 5 minutes. Could be 30.
The stuck-at-99% variant was reported multiple times: generation completed server-side, the progress bar hit 99%, and then stalled indefinitely. Hard-reloading the page and checking the generation history sometimes surfaced the completed video. Often it was just gone.
Sora’s queue system didn’t help clarity here. During high-load periods, a job wasn’t necessarily failing — it was waiting. But the UI didn’t distinguish clearly between “queued” and “stuck.” Users canceled jobs that would have finished, then burned credits on retries.
Credits Burned on Failed Generations
This one generated consistent, legitimate anger. In February 2026, multiple users reported Sora 2 returning “service unavailable” errors with no content generated — but credits were deducted anyway.
Adobe’s community forums have a specific thread: users describe Sora 2 failing twice in a row, zero content produced, credits gone both times. Those are Adobe generative credits — Adobe’s stated position in that thread is that credits return automatically when a generation fails on a system error. The enforcement wasn’t consistent.
If you’re on the API before the September 24 sunset and hitting this: log the failure (timestamp, request ID, the error response) and contact OpenAI support with documentation. Manual credit recovery through support has worked for users who documented the failures.
Content Quality Below Expectations
Sora’s output quality varied a lot by subscription tier — and some users were surprised to discover the gap.
Plus plan ($20/month) capped at 480p resolution by default, with a monthly generation limit. Higher resolutions were available but reduced the number of clips you could generate per month.
Pro plan ($200/month) offered substantially more usage and higher resolution outputs.
Users expecting sharp HD output on a Plus subscription were getting 480p — by design, not by bug. The disappointment was real, but it was a mismatch between plan expectations and reality.
Quality also degraded significantly with complex scene descriptions. Sora handled simple, single-subject prompts better than intricate multi-element scenes. Complex backgrounds, fast motion, and multiple interacting subjects all pushed toward artifact-heavy, inconsistent output. That was a genuine capability ceiling, not a settings problem.
Audio Sync Issues
Sora 2 added lip sync for talking-head video and motion-aware sound effects. Neither feature was consistently reliable.
Lip sync quality depended heavily on source material in image-to-video mode. A clean, well-lit, forward-facing subject produced acceptable sync for casual content. Anything with complex angles, motion, or poor source quality produced noticeable drift. Users doing professional talking-head work found HeyGen and Synthesia significantly more reliable for this — those tools were purpose-built for it, and it showed.
The sound effects feature generated audio that matched on-screen action in concept but often landed a beat late or early. Regenerating sometimes helped; sometimes produced equally mistimed audio.
Prompts Not Followed Closely
Sora followed the intent of a prompt reliably. Following it precisely — specific camera movements, exact subject positioning, particular framing — was inconsistent.
Common complaints: requested camera movements not applied, backgrounds substituted for something different, subjects positioning differently than described, clip duration shorter than requested. Users who needed precise control for professional production work found this limitation real. Users making social content generally didn’t care.
Vague, evocative prompts tended to produce better results than highly technical specifications. “A cinematic slow push toward a cafe window in the rain” worked better than detailed camera instruction language. That’s fine for social content. It’s limiting for anything that requires repeatable, spec-controlled output.
Browser Compatibility
Sora required a modern browser with hardware acceleration enabled. Users running ad blockers, privacy extensions, or script blockers reported generation failures that produced no error message — just silent failure or a UI that wouldn’t respond.
Chrome and Firefox (current versions, clean of conflicting extensions) were the most reliable. Brave with aggressive tracking protection was frequently cited as problematic. Safari behavior was inconsistent.
If Sora was working in one browser but not another, extensions were almost always the cause. Incognito mode — which disables most extensions by default — was the fastest diagnostic.
Slow Generation Times
Sora was slow. Not broken — just slow.
Peak-hours generation (weekday afternoons US time) could stretch from several minutes to over 15 for longer or higher-resolution clips. Off-peak hours produced meaningfully faster results. Users who needed consistent quick turnarounds found Pika and Kling faster in practice on equivalent prompts.
This was a known characteristic of Sora’s compute-heavy model. Expecting Sora to behave like Pika’s speed was a mismatch in expectations.
What Replaced Sora: Nothing, at OpenAI
This is the part worth being precise about, because a lot of coverage got it backwards. OpenAI didn’t move video generation into ChatGPT. It exited consumer video generation.
Sam Altman told staff the app and the developer API were both being discontinued, with no plans to integrate the video generator into ChatGPT. The video generation option that Plus and Pro subscribers had is gone. As of September 2026 there is no video generation inside ChatGPT, on any plan.
ChatGPT is still useful for the pre-production half of the work — scripts, shot lists, prompt writing, captions. For the generation itself you need a different vendor. That’s what the alternatives section below is for.
If you had content in Sora, the export window has closed. OpenAI directed users to sora.chatgpt.com/sunset before the shutdown and said Sora data would be permanently deleted once that window passed.
If You’re on the Sora API
Developer note: the Sora 2 API endpoint stops accepting requests on September 24, 2026. That’s not a soft deprecation — after that date, the API is gone.
Current API pricing (until sunset): Sora 2 at $0.10/second of generated video. Sora 2 Pro at $0.30/second for 720p and $0.50/second for higher resolutions. If you’re actively using this, track your spend and start your migration now. Under three weeks isn’t much lead time for a production integration.
Best Alternatives to Sora AI
All of these are active, maintained, and available right now.
Runway is where most professionals landed after Sora closed. Runway Gen-4.5, released December 2025, is the current standard for high-quality AI video production — more creative control than Sora had, faster iteration cycles, and active feature development. If you need reliable output for actual commercial work, Runway is the default recommendation. We also have a Runway troubleshooting guide if you run into issues getting started.
Pika is faster, more accessible, and has a free tier that’s genuinely usable. Pika 2.5 is the video model for text-to-video and image-to-video; audio-aware motion, sound effects, and lip sync come from Pika’s separate audio models. Good enough for social content, still behind purpose-built tools for professional talking-head work. Lower entry cost than Runway. The Pika troubleshooting guide covers the common issues.
Kling (from Kuaishou) handles longer clips and natural motion particularly well. It’s competitive on pricing and has continued strong development. Worth testing if you found Sora’s motion quality inconsistent — Kling often produces more natural-looking movement on certain subject types.
For a full head-to-head on these three tools — quality, speed, pricing, and which use case fits each — our Runway vs Pika vs Kling comparison has the breakdown. And if you want to see the broader field beyond the top three, the best AI video generators roundup covers current options with up-to-date pricing.
Sora had a rough, brief run. The technology was real, the errors were real, and the shutdown was real. If you were mid-project when it closed, the pivot to a dedicated tool like Runway or Kling is the path forward. The video generation market has kept moving — there are better options available now than when Sora launched.