Sora shutdown audit: which feature did you use, what replaces it
OpenAI shut down Sora 2 and the Videos API on September 24 with no replacement. A feature-by-feature checklist of what Sume covers and what it does not.
Start by listing which Sora features your code called, because OpenAI's own page says there is no one-to-one replacement and the shutdown on September 24, 2026 has passed. Text-to-video, image-guided clips and long-form assembly have a path on Sume; character uploads and the Sora editing endpoint do not map one for one.
What did OpenAI list as gone?
The video generation guide I read on 2026-10-02 names these Sora capabilities as no longer available: text-to-video, image references, character uploads for consistency, video extensions, editing (which replaced the older remix endpoint) and Batch API support. The deprecations page lists sora-2, sora-2-pro and the dated snapshots, with the Videos API, and states the replacement as none.
Which Sume feature covers each one?
Read the table as a starting point, then check the model's catalog entry, because Sume documents limits per model.
| Sora feature | Sume path | Gap to check |
|---|---|---|
| Text-to-video | POST /v1/videos with a catalog model or sume/auto | Pick durations from supported_durations |
| Image-guided clip | Image-to-video through the video catalog | Model-specific frame image inputs |
| Offline batch queue | Async jobs, queue, signed webhooks | No batch discount documented |
| Character uploads | Reference images on models that accept them | Check which reference inputs the chosen model accepts |
| Extensions and editing | Longer clips and Timeline assembly | Not an in-place extend call |
What are Sume's real limits?
The video docs say limits are per model: for example seedance-2.5 accepts 4 to 30 seconds at 480p, 720p and 1080p, and Auto defaults to 720p and 8 seconds with 3 to 10 second clips at 16:9 or 9:16. size returns 400 unsupported_parameter on v1 models that report supported_sizes: null, so use resolution plus aspect_ratio.
Query GET /v1/video-router/models for the live catalog instead of copying numbers from a blog.
What should I do this week?
Grep your code for the retired model ids, the /v1/videos OpenAI path, and any code that stored Sora job ids. Decide per feature whether you rebuild, drop it or pin a Sume catalog id. Test one real prompt per feature, and check the job result rather than assuming parity with Sora output.
For a deeper per-feature comparison, read Sora API shutdown and video migration.
Sume does not promise Sora-looking output, and no model here replicates a Sora clip. Judge the results on your own prompts.
Sources
Related posts
More in Use cases
- Where is the Save button on YouTube Shorts? Save to playlist
YouTube Help describes saving a Short through More, then Save to playlist. What that page says, the playlist limits it names, and what a creator can do with it.
- Which LLM should drive an AI video agent on Sume? A catalog table
Five orchestrator families sit in Sume's Agents catalog. The vendor-page limits that matter for a video agent, and what the LLM does and does not decide.
- Why is my YouTube Short private? The default for ages 13 to 17
YouTube sets new Shorts to private by default for creators aged 13 to 17 and public for 18 and up. Change it at upload, then publish; Sume does not upload.
- Wix Stores wants 3000x3000 images: check your model's cap
Wix Stores lists 3000 x 3000 px as its minimum product image. Check GET /v1/images/models for each model's largest size before you generate for it.
Written by Sume