Sora Problems & Issues

Real user-reported problems, complaints, and limitations for Sora. Based on analysis of 12 signals.

Overall score: 20/100

Issues by Category

reliability3 issues

Sora shut down: app and website closed April 26, 2026

OpenAI announced on March 24, 2026 that it was discontinuing Sora, about six months after the Sora 2 app launched in September 2025. The web and app experiences ended April 26, 2026; OpenAI did not give a detailed reason beyond focusing compute on other work.

Frequency: 10%Sentiment: -0.90/1008 sources
Impact
10

Videos not exported in time are permanently deleted

OpenAI says it permanently deletes Sora data once the discontinuation has happened and any final export window has passed. The export at sora.chatgpt.com/sunset sends an email when ready, so users who waited until the last day risked losing their library.

Frequency: 7%Sentiment: -0.80/1004 sources
Impact
9

Sora 1 removed in the US on March 13, 2026, with its images and videos

Before the full shutdown, OpenAI retired the original Sora 1 for US users on March 13, 2026 and made Sora 2 the default. Users were told to download Sora 1 images and videos they wanted to keep before the cutoff.

Frequency: 5%Sentiment: -0.60/1003 sources
Impact
6
pricing2 issues

Credits charged for videos that failed

Several community threads report generations or API runs that failed (sometimes at 100% progress) but still consumed credits or money. Users had to chase support for the lost credits.

Frequency: 6%Sentiment: -0.80/1003 sources
Impact
6

Free generations cut from 30 to 6 a day, extra videos sold separately

At launch most users got about 30 generations a day (Pro: 100). From late October 2025 OpenAI sold 10 extra generations for $4, and in November 2025 cut free users to 6 a day, with longer clips counting as multiple generations.

Frequency: 6%Sentiment: -0.50/1004 sources
Impact
5
security2 issues

Deepfakes and likeness misuse despite cameo consent rules

Unauthorized videos of real people, including actor Bryan Cranston, led to complaints from SAG-AFTRA, and a watchdog group urged OpenAI to pull the app. The visible watermark could be removed with editing tools within days of launch.

Frequency: 6%Sentiment: -0.70/1004 sources
Impact
7

Copyright opt-out policy reversed after launch

Sora 2 launched letting copyrighted characters appear unless rights holders opted out, which produced viral videos of SpongeBob, Pikachu and others. OpenAI then switched to opt-in for rights holders, which tightened filters for users.

Frequency: 5%Sentiment: -0.50/1004 sources
Impact
5
integrations1 issue

Sora API retired September 24, 2026 with no replacement

OpenAI's deprecations page lists the Videos API and the sora-2, sora-2-pro and dated snapshot models as shut down on September 24, 2026, with 'No one-to-one replacement'. Apps and pipelines built on Sora had to migrate to Veo, Kling, Runway or other video models.

Frequency: 8%Sentiment: -0.80/1005 sources
Impact
9
usability1 issue

Content violation errors blocked ordinary prompts

Days after the Sora 2 launch, users reported a wave of 'content violation' and 'similarity to third-party content' rejections, including for public-domain characters. Some called the app unusable for creative work, while critics said the same guardrails still let violent and offensive videos through.

Frequency: 8%Sentiment: -0.70/1004 sources
Impact
7
performance1 issue

Sora videos stuck at 0% or 99% for hours

OpenAI and Adobe community threads describe Sora 2 jobs sitting at 0% or 99% progress for hours, or failing after a long wait with 'Something went wrong, please try again later'. API users reported multi-hour queue backlogs at busy times.

Frequency: 7%Sentiment: -0.70/1005 sources
Impact
7
onboarding1 issue

Invite codes and 'not available in your country'

Sora 2 launched invite-only and limited to a few markets. The Android app arrived in November 2025 in only seven regions (US, Canada, Japan, South Korea, Taiwan, Thailand, Vietnam); users elsewhere, including India, saw 'not available in your country'.

Frequency: 6%Sentiment: -0.50/1004 sources
Impact
5
support1 issue

No dedicated refund for Sora, only ChatGPT's standard process

OpenAI's discontinuation help page points refund questions to the standard ChatGPT subscription refund process and says credits bought for ChatGPT and Sora can be used in Codex instead. There was no automatic Sora-specific refund.

Frequency: 5%Sentiment: -0.60/1002 sources
Impact
6

Regret Patterns

Common reasons users regret choosing Sora.

Waiting too long to export

Users who assumed their Sora library would stay viewable found the app closed on April 26, 2026 and the data subject to permanent deletion after the export window.

Frequency: 7%At the April 26, 2026 shutdown

Building a product on the Sora API

Developers who built apps and pipelines on sora-2 had six months to migrate after the March 2026 notice, with no OpenAI replacement model.

Frequency: 6%September 24, 2026

Upgrading to ChatGPT Pro for Sora 2 Pro

Some users paid $200/month mainly for Sora 2 Pro and its higher limits, only to see the product closed months later with refunds handled through the generic ChatGPT process.

Frequency: 4%Within months of upgrading

Buying extra generation packs

Users who bought $4 packs of extra generations were offered Codex credit rather than a Sora-specific refund.

Frequency: 4%After the March 2026 announcement

Losing Sora 1 work at the March 13 cutoff

US users of the original Sora had their Sora 1 images and videos removed when Sora 2 became the default, weeks before the full shutdown.

Frequency: 4%March 13, 2026

Burning credits on stuck generations

Users lost daily generations or paid API time on jobs that stuck at 0% or 99% and then failed.

Frequency: 5%During busy periods

When Sora Breaks Down

Specific scenarios where Sora fails or underperforms.

Opening the Sora app after April 26, 2026

The app and sora.com can no longer generate or show your feed; only OpenAI's sunset/export page remained.

Calling /v1/videos after September 24, 2026

Requests to the Videos API and sora-2 models fail; scheduled jobs and third-party integrations using Sora break.

Exporting a large library at the last minute

Exports are prepared and emailed, not instant, so late requests risked missing the deadline.

Prompts mentioning famous characters or people

Sora 2 often rejected these with content violation or 'similarity to third-party content' errors.

Peak-hour generation

Jobs could sit at 0% or 99% for hours, and some failed after consuming credits.

Using Sora outside supported countries

The app showed 'not available in your country' outside the US, Canada, Japan, South Korea, Taiwan, Thailand and Vietnam.