Bounds on a size against a ladder of named tiers

One page permits any width and height between 128 and 4,096 pixels. The other names 720p, 1080p and 4k and ties the upper two to an eight second run. One cell describes a region and the other a ladder with conditions attached to its rungs. As of 2026-09-22.

Inclusion rule. Resolution statements from each page, kept in the form each uses. A tier name is not converted into pixels and bounds are not converted into tiers. Order. The form of the statement first.

1Exactness is worth something at upload

Odd pixel counts after a crop are a common cause of rejection. A row that accepts arbitrary even dimensions can be asked for the exact frame a surface expects, so the crop that introduced the problem never happens.

A named tier cannot do that. The pixels behind 1080p are whatever the vendor decided, the page does not print them, and a placement minimum has to be checked against an assumption rather than against a figure.

2Conditions live on rungs, not on regions

Because the ladder row ties its two upper rungs to a single length, choosing quality there also chooses duration. The bounds row states no such interaction, so size and length can be settled independently.

That makes the bounds row simpler to plan and the ladder row cheaper to draft on: there is a bottom rung to iterate at, which a region with no priced steps does not offer at all.

3What the shape column does to both

Both pages publish exactly two shapes: widescreen and vertical. So the freedom on one row and the tiers on the other are both bounded by the same short list, and a square placement is unserved by either.

Reading the two columns together is the point. Bounds from 128 to 4,096 pixels sound like any frame at all until the shape list is read, and a 4k tier sounds like the top of the register until the eight second annotation is.

4The rest of the column behind these two

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. A region and a ladder answer different questions. One can be asked for an exact frame a placement wants; the other cannot be asked for a short run at its top two rungs. Neither limitation is visible in the other's units.

• Output size
  Width and height must each be between 128 and 4,096 pixelspublished as a range not a ladderHeyGen documentation, usage limits / recorded 2026-09-22
• Resolutions
  720p, 1080p (8s length only), 4k (8s length only)tied to the lengthGoogle AI for Developers, Veo 3.1 / recorded 2026-09-22

5Sources

Read from the HeyGen usage limits page and Google's Veo documentation, both checked 2026-09-22. The column is described on resolution, and each entry has its own cell page at HeyGen and Google Veo, and the rule that keeps surfaces and generators apart is on method. Nearby pairs: Hedra and HeyGen on shape, Runway and MiniMax.