Four thousand pixels against fifteen hundred

Two pages state output size in pixels rather than in named tiers. One permits any dimension between 128 and 4,096. The other lists seven exact pairs whose longest side is 1584. A tier name would have hidden both facts. As of 2026-09-22.

Inclusion rule. Output size statements from each page, in pixels as each page prints them. No tier name is inferred and no pair is converted into a ratio. Order. The form of the statement first, then the ceiling.

1Pixels make the comparison possible and the column harder

Thirteen rows here publish names. Two publish numbers, and those two can be put side by side and read off: 4,096 against 1,584 on the longest side. Nothing else in this column supports that without assuming what a tier name contains.

The cost is that neither row can be lined up against the thirteen. A register that converted them into tiers would publish its own arithmetic with a check date, which is exactly what these sheets refuse to do.

2The lower ceiling belongs to the more flexible shape list

The row with seven shapes, including a square pair, tops out well below 1080p on its long axis. The row that reaches 4,096 pixels publishes two shapes and no square option.

So neither is simply larger. One is a service for short conditioned pieces in many shapes, the other a renderer that will produce very large frames in two, and a campaign chooses on which constraint it is actually fighting.

3What each ceiling is worth against the placements here

Nothing in the formats this register reads asks for 4,096 pixels. The surface that publishes minimums tops out well below it, so the large figure is for reuse beyond the placement rather than for the placement.

The smaller ceiling is the one that could bite, and only outside a feed. For vertical short-form, 720 by 1280 clears every published floor comfortably, and both rows deliver it without buying anything.

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. These are the two rows that publish pixels instead of tiers, so they are the only pair in this column that can be compared without arithmetic. The comparison puts them two and a half times apart.

• 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
• Gen-4.5 image-to-video
  Landscape 1280:720, 1584:672 and 1104:832, portrait 720:1280, 832:1104 and 672:1584, square 960:960shape given as a pixel pair rather than a ratioRunway API, input parameters / recorded 2026-09-22

5Sources

Read from the HeyGen usage limits page and the Runway API input reference, both checked 2026-09-22. The column is described on resolution, and each entry has its own cell page at HeyGen and Runway, and the rule that keeps surfaces and generators apart is on method. Nearby pairs: TikTok and YouTube, Hedra and Wan 3.0.