A fixed format against a ladder with a default
One page states 1280x720 as the resolution, full stop. The other states 1080p, 720p and 480p and names 480p as the default. Neither leaves an unspecified request undefined, and they get there by opposite routes. As of 2026-09-22.
| What the pages state | Amazon Nova Reel | Grok Imagine |
|---|---|---|
| Values available | One | Three |
| If the field is omitted | The same single value | 480p, the stated default |
| Cheap draft | Not available | The default rung |
Inclusion rule. Resolution statements from each page, including any default it names. A value offered in a user interface but absent from the documentation is not recorded. Order. How many values first, then what happens when none is chosen.
1Predictability by two different means
An unset parameter is still a parameter. On most rows in this column nothing on the page says what an omitted field returns, so a pipeline that forgets it produces output the documentation cannot predict.
Here one page removes the field entirely and the other publishes its fallback. For unattended batch work both are safe, which puts these two rows in a small group on these sheets.
2Only one of them can be drafted cheaply
A named default at the bottom rung is an invitation: explore at 480p, deliver at 1080p, pay the difference once. The fixed row has no rung to drop to, so exploration costs what delivery costs.
That matters for a campaign of variants rather than for a single piece. Forty attempts at the bottom of a ladder and forty attempts at a fixed format are very different numbers on an invoice, and nothing in either resolution cell shows it.
3What each page says about shape
The fixed row names no shape at all, although its pixels are widescreen by arithmetic, so a vertical placement cannot be planned from it. The ladder row publishes seven shapes and names sixteen by nine as the default.
Read together that is the sharper difference. One page answers the size question completely and the shape question not at all; the other answers both and names a fallback for each, which is as complete as this column gets.
4The rest of the column behind these two
| 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 this register carries, on the one column this pair disagrees about. Rows that state nothing keep their place and are marked hollow. Order. Alphabetical by generator name.
Why these two. Both rows are predictable when a request says nothing, which most of this column is not. One achieves it by having no choice and the other by publishing its fallback, and only one of those leaves room for a cheap draft.
- Video resolution1280x720the single value in the table
- Resolution parameter1080p, 720p and 480p, with 480p the default
5Sources
Read from the Amazon Nova user guide and the xAI video generation docs, both checked 2026-09-22. The column is described on resolution, and each entry has its own cell page at Amazon Nova Reel and Grok Imagine, and the rule that keeps surfaces and generators apart is on method. Nearby pairs: Veo and Grok Imagine, Veo and PixVerse.