Fitting HeyGen output into YouTube ad formats
HeyGen publishes a page of limits rather than a price grid: thirty minutes per scene, fifty scenes per video, 16:9 or 9:16, and output dimensions given as a range from 128 to 4,096 pixels on each side. Every ad format in this register fits in a single scene. As of 2026-09-22.
| Format | Generations needed | Note |
|---|---|---|
| Bumper, 5-6 s | One scene | Thirty minutes per scene is the stated limit |
| Non-skippable, up to 60 s | One scene | A minute is well inside one scene |
| Skippable, 30 s of paid view | One scene | The limit is two orders of magnitude away |
| Masthead, 16:9 up to 30 s | One scene | 16:9 is one of the two published ratios |
Inclusion rule. Formats from Google's own help page, matched only against limits the tool vendor publishes. Where either side does not state a value, the row says so rather than estimating. Order. Shortest format first, as on the placements page.
1How much each tool puts in writing
| Tool | Limits published |
|---|---|
| Amazon Nova Reel | 4 published |
| CogVideoX | 3 published |
| Google Veo | 4 published |
| Grok Imagine | 4 published |
| Hedra | 3 published |
| HeyGen | 4 published |
| LTX-Video | 3 published |
| MiniMax | 3 published |
| Pika | 2 published |
| PixVerse | 3 published |
| Runway | 4 published |
| SceneMixer | 3 published |
| Wan 3.0 | 4 published |
Inclusion rule. Tools with a sheet on this site, counted by how many separate output limits their own pages state. A limit mentioned only in a launch post is not counted. Order. Alphabetical by tool name.
| Tool | Bumper, 5-6 s |
|---|---|
| Amazon Nova Reel | One shot |
| CogVideoX | One generation |
| Google Veo | One generation |
| Grok Imagine | One generation |
| Hedra | One generation |
| HeyGen | One scene |
| LTX-Video | One generation |
| MiniMax | One generation |
| Pika | One generation |
| PixVerse | One generation |
| Runway | One generation |
| SceneMixer | One generation |
| Wan 3.0 | One generation |
Inclusion rule. Tools publishing output limits on their own product pages. A tool silent on this particular limit keeps its row, marked hollow. Order. Alphabetical by tool name.
| Tool | Non-skippable, up to 60 s |
|---|---|
| Amazon Nova Reel | One request of ten shots |
| CogVideoX | Ten generations |
| Google Veo | Eight generations |
| Grok Imagine | Four generations |
| Hedra | One generation |
| HeyGen | One scene |
| LTX-Video | Seven generations |
| MiniMax | Four generations |
| Pika | Six or more generations |
| PixVerse | Four generations |
| Runway | Four generations |
| SceneMixer | Two generations on Wan 3.0 |
| Wan 3.0 | Two generations |
Inclusion rule. Tools publishing output limits on their own product pages. A tool silent on this particular limit keeps its row, marked hollow. Order. Alphabetical by tool name.
| Tool | Skippable, 30 s of paid view |
|---|---|
| Amazon Nova Reel | One request of five shots |
| CogVideoX | Five generations |
| Google Veo | Four generations |
| Grok Imagine | Two generations |
| Hedra | One generation |
| HeyGen | One scene |
| LTX-Video | Four generations |
| MiniMax | Two generations |
| Pika | Two to three generations |
| PixVerse | Two generations |
| Runway | Two generations |
| SceneMixer | One generation on Wan 3.0 |
| Wan 3.0 | One generation |
Inclusion rule. Tools publishing output limits on their own product pages. A tool silent on this particular limit keeps its row, marked hollow. Order. Alphabetical by tool name.
2Limits published as limits, which reads differently
Almost every vendor figure on these sheets is a by-product of billing: a duration appears because a duration is charged for, a resolution appears because each rung costs more. This page exists to say where the walls are, and the difference shows in what it covers. Scene count, upload ceilings and a pixel range are not priced levers, and none of them would appear on a pricing table.
For matching against an ad slot the effect is that the length column stops mattering and the shape column starts. Thirty minutes per scene clears every format here without discussion, while 16:9 or 9:16 is a firm choice of two that has to be made before anything is generated.
3A pixel range instead of a resolution ladder
Width and height each between 128 and 4,096 pixels is a different kind of statement from 720p or 1080p. It describes a space of legal outputs rather than a set of tiers, so a request can ask for the exact pixel dimensions a placement wants instead of picking the nearest rung and living with the shape that comes out.
The megabyte figures on the same page belong to uploads rather than output: 100MB for a video going in, 50MB for an image or an audio file, 32MB for an asset. They are worth recording because the file column on these sheets is otherwise empty on the vendor side, but they answer a question about what goes in, not about what an ad platform will be asked to accept.
4Sources
Output limits read from the usage limits page at developers.heygen.com, checked 2026-09-22. Format requirements are from Google Ads Help, and the matching rule is on method. Next along the register: LTX-Video, MiniMax. The whole set of 15 is on published limits, and the sheets for each are indexed at tools.
- Longest output stated anywhere in this register30 minutes per scene, with 50 scenes per video
- Aspect ratios accepted16:9 or 9:16
- Output sizeWidth and height must each be between 128 and 4,096 pixelspublished as a range not a ladder
- Upload ceilings100MB for a video, 50MB for an image or an audio file, 32MB for an asset upload