Vidu prices a ladder that starts at the vertical minimum
The API price page publishes 540p, 720p and 1080p as priced steps. Its floor sits exactly at the vertical minimum the one surface that publishes pixel floors states. As of 2026-09-12.
| Rung | Priced as | Against the vertical minimum of 540x960 |
|---|---|---|
| 540p | A step on the rate card | Meets it on the short side |
| 720p | A step on the rate card | Clears it |
| 1080p | A step on the rate card | Clears it comfortably |
Inclusion rule. Resolution steps this price page attaches a rate to, compared only against a pixel minimum a platform publishes on its own help page. Order. Lowest rung first, as the page orders them.
1The cheapest rung is a deliverable rung
A 540p short side is exactly the vertical floor the platform in this register that publishes minimums states: 540x960 or more. So nothing has to be bought above the bottom of this ladder for a vertical placement to be accepted.
That is the useful reading of a floor. On rows whose bottom rung is 720p, a draft and a delivery are the same purchase; here they can be separated, and for a campaign of many short cuts the separation is where the budget is.
2A rate per generation is not a rate per second
The ladder is priced and the duration column on this page is empty, which means the figures cannot be converted into a cost per second of output. Two rows in this register publish a per-second basis; this one publishes neither a per-second rate nor the length that would let one be computed.
For a plan that has to compare vendors on cost, that is the binding gap. Quality is priced, time is not published, and the two together are what a placement consumes.
3Three rungs and nothing else
Resolution is the only column this page fills. Shape is absent, so a widescreen Masthead requirement cannot be confirmed against it; length is absent, so a schedule cannot be built from it. The row is complete in one column and hollow in the rest.
The register prints it that way on purpose. A sheet that only listed rows it could fill would answer a different question, and the question these sheets ask is what is actually published, counted honestly.
4Where this cell sits in the column
| Generator | Resolution |
|---|---|
| Amazon Nova Reel | 1280x720 |
| CogVideoX | 720 x 480 only |
| Google Veo | 720p / 1080p / 4k |
| Grok Imagine | 480p / 720p / 1080p |
| Hedra | 540p / 720p / 1080p |
| HeyGen | 128 to 4,096 px each side |
| Kling AI | 720p / 1080p / 4K |
| LTX-Video | 1216x704 |
| MiniMax | 480P / 768P / 2K |
| Pika | 480p / 720p / 1080p |
| PixVerse | 360p / 540p / 720p / 1080p |
| Runway | Pixel pairs, not tiers |
| SceneMixer | 480P / 720P / 1080P |
| Vidu | 540p / 720p / 1080p |
| Wan 3.0 | 480P / 720P / 1080P |
Inclusion rule. Every generator in the register, carrying the resolution figure its own page prints, whether that is a ladder, a range or a single pair of numbers. Order. Alphabetical by generator name.
- Resolutions540p, 720p and 1080ppriced per step
5Sources
Read from the Vidu API price page, checked 2026-09-12. The column itself is described on resolution, and the rule that keeps surfaces and generators apart is on method. Next along this column: Wan 3.0, Amazon Nova Reel.