Sora removes web access on Apr. 26 and API access on Sep. 24

• OpenAI has now put dates on Sora’s retirement: according to the shutdown post, the web and mobile app end on April 26, 2026, and the official notice says the API follows on September 24, 2026.
• The split timeline gives developers about five more months beyond the consumer shutdown to wind down integrations, even as the support screenshot makes clear that exported access to existing content is still time-limited.
• Sora is telling users to export before the app cutoff, and the FAQ screenshot shows downloads are currently per-item rather than bulk, which turns migration into a manual library pull for heavier users.
• Community discussion on Hacker News is treating the shutdown as a product-strategy signal toward coding and business products, but that broader motive remains interpretation rather than an official technical explanation.

The dates are now explicit. The shutdown post says “Sora web & app will be shut down April 26, 2026” and that “the Sora API will be discontinued September 24, 2026.” That creates two different deadlines: one for interactive product access and a later one for programmatic access.

For engineers, the important change is certainty. The earlier official notice had said only that Sora was “saying goodbye” and would share more on “timelines for the app and API”; now those dates are fixed. The roughly five-month gap suggests OpenAI is not pulling the API on the same day as the app, which gives teams a defined window to remove dependencies, swap vendors, or archive generated assets.

Hacker News discussion summarized in the thread roundup goes further, with commenters claiming OpenAI is also winding down a developer version of Sora and deprioritizing video inside ChatGPT. Those points are useful as community context, but they are still secondhand claims rather than details confirmed in the shutdown notice itself.

The operational burden is clearest in the support copy captured in the FAQ screenshot. It says users who want to keep Sora content should export it before the web and app discontinuation date, and that they can “download individual images and videos from your Library.” The same screenshot says OpenAI is “still determining” whether any post-shutdown export window will exist, so continued access after April 26 is not something teams can count on.

That matters because the current export path appears manual. As one user’s note put it, “No bulk exporter is being offered atm,” which matches the screenshot’s item-by-item wording. For teams with larger libraries, that turns preservation into a throughput problem rather than a simple account offboarding step.

The asymmetry between app and API deadlines also means there are really two migration tracks. Content preservation is tied to the April 26 product shutdown, while integration removal can extend until September 24 under the posted API date. That separation is useful, but it does not remove the immediate need to pull assets out of the Sora library before the consumer surface disappears.