As of , according to OpenAI’s official deprecations page, the Videos API, sora-2, and sora-2-pro are scheduled to be removed on September 24, 2026. The API is still documented today, but a new production integration now has a fixed end date, and OpenAI lists no recommended replacement.
According to OpenAI’s current API pricing page, Standard Sora 2 requests cost $0.10 to $0.70 per generated second. Batch prices are exactly half of the Standard rates: $0.05 to $0.35 per second. An eight-second clip therefore costs from $0.80 with Sora 2 at 720p to $5.60 with Sora 2 Pro at 1080p before retries or other workflow costs.
Developer decision summary: use the official API only for work that can finish before September 24, 2026. Use Batch for non-urgent queues. For any product that must operate beyond that date, start migration testing now.
As of July 17, 2026, the GlobalGPT Sora 2 generator still lists Sora 2, while the platform’s public plan page starts at $11.90 month to month or $5.80 per month with annual billing for Basic. Those subscription prices are not a published Sora-specific per-second API rate, so they should not be compared directly with OpenAI’s API invoice. Because this article is published by the team behind GlobalGPT, treat references to the platform as first-party product information.
This comparison is for developers and buyers choosing between direct API billing and third-party platform access. It covers official prices, Batch discounts, current public platform evidence, and shutdown planning; it does not treat ChatGPT Sora subscriptions or undocumented endpoints as substitutes for OpenAI’s documented API.
In this guide
- Official Sora 2 API pricing
- Official API vs third-party access
- Content restrictions and real cost
- Developer migration checklist
- Pricing FAQ
Official Sora 2 API Pricing (OpenAI)
OpenAI prices video generation by output duration and resolution. Sora 2 is the lower-cost 720p model. Sora 2 Pro adds 720p, 1024p, and 1080p options at progressively higher rates. The full current price table is below.
| Model and size | Processing | Price per second | 8-second cost | 20-second cost |
|---|---|---|---|---|
sora-2720 × 1280 or 1280 × 720 | Standard | $0.10 | $0.80 | $2.00 |
sora-2720 × 1280 or 1280 × 720 | Batch | $0.05 | $0.40 | $1.00 |
sora-2-pro720 × 1280 or 1280 × 720 | Standard | $0.30 | $2.40 | $6.00 |
sora-2-pro720 × 1280 or 1280 × 720 | Batch | $0.15 | $1.20 | $3.00 |
sora-2-pro1024 × 1792 or 1792 × 1024 | Standard | $0.50 | $4.00 | $10.00 |
sora-2-pro1024 × 1792 or 1792 × 1024 | Batch | $0.25 | $2.00 | $5.00 |
sora-2-pro1080 × 1920 or 1920 × 1080 | Standard | $0.70 | $5.60 | $14.00 |
sora-2-pro1080 × 1920 or 1920 × 1080 | Batch | $0.35 | $2.80 | $7.00 |
OpenAI Sora 2 API prices checked July 17, 2026. Clip totals are the published per-second rate multiplied by duration.
Official API vs third-party Sora access: what are you actually buying?
The phrase “unofficial Sora 2 API” often mixes three different products: a consumer web interface, an aggregator’s own API, and an undocumented endpoint. They are not equivalent. A lower subscription price does not prove a lower API cost unless the provider publishes the credits consumed per completed second, resolution, retry policy, concurrency limits, and failed-job rules.
| Decision factor | OpenAI direct API | GlobalGPT platform access | Other third-party offers |
|---|---|---|---|
| Price basis | Published per generated second; Standard and Batch rates | Subscription and platform credits; no stable public Sora-specific per-second rate in logged-out view | Varies by provider, plan, credits, and job rules |
| Developer interface | Documented Videos API and official model IDs | Current browser-based video generator; do not assume it is a drop-in OpenAI API replacement | Could be a web UI, proxy API, or undocumented integration |
| Lifecycle visibility | Removal date published: September 24, 2026 | Sora 2 is currently listed, but continued access after OpenAI’s deadline is not guaranteed | Depends on the provider’s upstream access and product decisions |
| Support evidence | Official documentation and account support | Platform-level support and terms | Review the provider’s own SLA, terms, refund policy, and status history |
| Best fit | Existing API workloads that will finish before shutdown | No-code testing and comparing multiple video models in one interface | Only after the exact product, effective cost, and continuity plan are verified |
A useful effective-cost formula is: total subscription fees, top-ups, and charged failures divided by the number of completed video seconds you can actually use. Apply that formula to the same resolution, duration, and quality target before calling one route cheaper.
In short, while unofficial providers can be cost-efficient for experimentation, users should approach them with caution, especially for commercial or enterprise use.
Content restrictions can change the real cost
OpenAI’s current guide says the API accepts only content suitable for audiences under 18, rejects copyrighted characters and copyrighted music, and does not generate real people, including public figures. Human-likeness character uploads are blocked by default, and input images containing human faces are currently rejected.
These restrictions matter to pricing because a technically valid request can still fail at the content-policy stage. Test representative prompts and reference assets before estimating cost from the per-second table alone. A workflow that depends on recognizable people, copyrighted franchises, or face-based references needs a different creative approach, not merely a larger API budget.
What developers should do before September 24, 2026
- Stop adding long-lived Sora dependencies. New features that must work after September should start with another video model or a provider-neutral adapter.
- Inventory every affected call. Search for the Videos API, model aliases, dated snapshots, webhooks, stored video IDs, and any polling or download code tied to Sora.
- Export what you need to retain. Save finished videos, prompts, reference assets, settings, and evaluation notes while the current workflow still runs.
- Separate your application from one provider. Normalize prompt, duration, aspect ratio, status, download, and error handling behind an internal interface.
- Benchmark alternatives on matched prompts. GlobalGPT currently lists models including Veo 3.1, Seedance 2.0, Kling 3.0, Wan 2.7, Grok Imagine, and Sora 2 in its multi-model video generator. Compare usable-output rate, latency, prompt adherence, audio, and policy fit rather than selecting by headline price alone.
- Set an internal migration deadline earlier than OpenAI’s. Leave enough time for production testing, data retention, contract review, and rollback before September 24.
OpenAI’s deprecations table currently shows dashes in the recommended-replacement column for the Videos API and every listed Sora 2 model. That makes independent evaluation essential. The current Sora 2 alternatives guide provides a wider shortlist, while the Sora 2 access status page tracks where the model can still be used.
Which Sora 2 pricing route is best now?
| Your situation | Best current route | Why |
|---|---|---|
| You already run Sora 2 in production and need fast results | Official Standard API while it remains available | Documented behavior and lower latency than an offline queue, with a mandatory migration plan |
| You already have a large non-urgent render backlog | Official Batch processing | Half the published Standard price for offline jobs that can finish before shutdown |
| You want to test Sora 2 without building an API integration | Current platform access such as GlobalGPT | Browser-based generation and side-by-side access to alternative models |
| You are starting a product that must run after September 2026 | Choose a different model and use a provider-neutral architecture | OpenAI has already published the Sora 2 API removal date and no replacement |
If you still need to compare the two official models, the practical split remains simple: Sora 2 is the lower-cost 720p option, while Sora 2 Pro adds higher-resolution output at a higher price. The detailed Sora 2 vs Sora 2 Pro comparison covers that model choice, but the shutdown deadline should now come before quality differences in any buying decision.
Why developers are re-evaluating Sora 2 economics
- The price is transparent, but the remaining lifecycle is short. Teams can forecast render spend while still facing an unavoidable migration.
- Batch makes volume work cheaper, not permanent. The 50% discount helps existing queues but does not extend the API’s life.
- High-resolution iteration is expensive. One 20-second Sora 2 Pro 1080p output is $14 at the Standard rate before any rejected attempts or revisions.
- The missing official replacement increases engineering cost. Teams must compare providers, adapt parameters, and rebuild evaluation baselines instead of switching to a named successor.
Sora 2 API pricing FAQ
How much does the Sora 2 API cost per second?
As of July 17, 2026, OpenAI lists Sora 2 at $0.10 per second for 720p. Sora 2 Pro costs $0.30 at 720p, $0.50 at 1024p, and $0.70 at 1080p with Standard processing.
How much does a 20-second Sora 2 video cost?
At Standard rates, 20 seconds costs $2 with Sora 2 720p or $6, $10, and $14 with Sora 2 Pro at 720p, 1024p, and 1080p. Batch cuts each total in half.
Is the Sora 2 API shutting down?
Yes. OpenAI says the Videos API, Sora 2 model aliases, and listed snapshots will be removed on September 24, 2026. The deprecation notice was issued on March 24, 2026.
Is Sora 2 cheaper through the Batch API?
Yes. OpenAI’s current Batch prices are 50% below Standard: $0.05 per second for Sora 2 and $0.15, $0.25, or $0.35 for Sora 2 Pro, depending on resolution.
Does OpenAI recommend a Sora 2 API replacement?
No. As of July 17, 2026, OpenAI’s deprecations table shows no recommended replacement for the Videos API, Sora 2, Sora 2 Pro, or the listed dated snapshots.
Is third-party Sora 2 access the same as OpenAI’s API?
Not necessarily. A third-party offer may be a web interface, a provider’s own API, or an undocumented integration. Compare the actual interface, credit rules, support, output terms, and shutdown exposure.
Should developers start a new Sora 2 integration now?
Only for short-lived work that can finish before September 24, 2026. Products that must operate after that date should choose another model and keep the video provider behind a replaceable internal interface.
Final verdict
OpenAI’s official Sora 2 API currently costs $0.10 to $0.70 per generated second, or $0.05 to $0.35 through Batch. The most important number, however, is now the date: September 24, 2026. Existing teams can use the remaining window to finish work and lower non-urgent costs with Batch. New production projects should benchmark alternatives and avoid building a long-term dependency on an API that already has a published removal date.
