What the resolution step costs on Sora
Sora publishes ten cents a second at 720p on the base model and thirty on the pro model at the same resolution, rising to seventy at 1080p. A batch tier halves all of them, which makes the range wider than resolution alone would. As of 2026-09-22.
| Model and tier | Per second, as published |
|---|---|
| sora-2 at 720p | Ten cents |
| sora-2-pro at 720p | Thirty cents |
| sora-2-pro at 1080p | Seventy cents |
| The batch tier | Half the standard figure, on every model and resolution |
Inclusion rule. Figures on the API price page, by model and resolution, plus any modifier the page applies across them. The dearest published second in this register is on this page. Order. Ascending by published figure, with the modifier last.
1Where Sora sits in this column
| Channel | Step up in resolution |
|---|---|
| Kling AI | Double to 1080p, five times to 4K |
| MiniMax | Half again from 768P to 2K |
| Replicate | Nearly three times for one step |
| Sora | Seven times from the cheapest to the dearest |
| Veo | Free on one tier, twelvefold across the range |
| Vidu | Just over double across three tiers |
| Wan | Four times from 480P to 1080P |
Inclusion rule. Channels publishing a rate at more than one resolution on the same page. A channel with a single figure has no step to price. Order. Alphabetical by channel name.
2The pro model costs three times as much at the same resolution
Thirty cents against ten at 720p is the whole difference between two models, with no change in output size. Then 1080p on the pro model adds another one hundred and thirty per cent, which is the steepest single resolution step on the ledger.
Stacked, those two decisions multiply to seven times. A shortlist built on the ten-cent figure and delivered at the top combination is wrong by a factor, and both figures are on the same page in the same table.
3A batch tier at half price changes what the ceiling means
Because the halving applies to every model and resolution rather than to one tier, the top of this page is thirty-five cents a second for work that can wait, not seventy. That is the same discount structure Vidu applies to off-peak hours, expressed as a queue rather than a clock.
For a serial production most generation is not urgent. Character sheets, scene plates and first passes can all queue, which makes the batch figure the realistic planning rate and the standard figure the cost of impatience.
4The dearest second in the register is here, and so is a cheap one
Seventy cents a second is the highest unconditional published figure anywhere on this ledger, and ten cents on the same page is unremarkable. A channel cannot usefully be ranked as dear or cheap when its own range covers that much ground.
Which is the argument for ranking rows rather than channels throughout this register. The model and the tier decide the rate; the shop mostly decides which models are on offer and what conditions come attached.
- sora-2 at 720p$0.10 per second
- sora-2-pro at 720p$0.30 per second
- sora-2-pro at 1080p$0.70 per secondthe dearest published second in this ledger
- The batch tierHalf the standard figureon every Sora model and resolution
5Inside a generated second
Price aside, what goes into the seconds behind “Sora resolution step” is described in SceneMixer's guides:
The shots add up to more than the selected video tier allows for one segment.
SceneMixer, Shot Seconds: Changing Timing, and the Limits — “What does 'over cap' mean on the segment card?” (read 2026-10-13)
Every segment it can revise starts ticked; untick any of them, or press Clear and pick.
SceneMixer, Revise the Whole Episode: One Request, Every Segment — “Can I leave some segments alone?” (read 2026-10-13)
6Sources
Read from the API price page published at developers.openai.com on 2026-09-22. The rate this column sits beside is on Sora; what the register accepts as published is on the method page. The same column on other channels: Wan, Kling AI. Every column: what each channel publishes.