Wan 3.0 publishes three tiers with no conditions
The reference publishes 1080P, 720P and 480P and attaches no condition to any of them. Read beside the two to thirty second range on the same page, that makes the widest prompt-driven length in this register available at the cheapest tier. As of 2026-09-22.
| Property | Value | Coupling |
|---|---|---|
| Resolution tiers | 1080P, 720P, 480P | None stated |
| Duration | An integer in [2, 30] seconds | None stated against any tier |
| Aspect ratios | adaptive, then six named shapes | None stated against any tier |
Inclusion rule. Values this API reference states for the model this register reads. Values for other models on the same platform are not carried on this sheet. Order. As the reference lists its parameters.
1Three unlinked parameters make the plainest row here
Length, size and shape are published as three lists with no cross-conditions. Thirty seconds at 480P in a vertical shape is a request the page supports on its face, and so is two seconds at 1080P in an ultrawide one.
Two other rows in this register annotate a tier with a length, and reading either of them teaches a rule that does not apply here. The absence of conditions is itself a fact worth recording, which is why the coupling column on this table says none stated three times.
2A 480P floor under a thirty second ceiling
The combination is what makes this row the usual answer for a long placement. A thirty second piece at the cheapest tier is one request, and the Masthead autoplay window and the point a skippable view is charged both land at exactly thirty.
It also makes the cheap iteration loop long enough to be useful. Timing, blocking and pacing can be judged at full length before anything is bought at 1080P, which is not possible on a row whose cheapest tier is capped at eight seconds.
3What the register does not take from the tier names
480P, 720P and 1080P are names rather than pixel pairs, and the page does not print the dimensions behind them. Against a platform that states pixel minimums, that means the check is done on the name and the arithmetic is assumed rather than read.
Two rows here publish exact pairs instead and are harder to compare for exactly that reason. Neither style is better; the register records which one each page used, because a reader checking a placement minimum needs to know whether the figure was named or measured.
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.
- Resolution tiers1080P, 720P and 480P
- Duration parameterAn integer in the range [2, 30] seconds, and input plus output must not exceed 30 seconds
5Sources
Read from the Wan3.0 API reference, checked 2026-09-22. The column itself is described on resolution, and the rule that keeps surfaces and generators apart is on method. Next along this column: Amazon Nova Reel, CogVideoX.