HeyGen publishes three upload ceilings by asset type
The usage limits page states 100MB for a video, 50MB for an image or an audio file and 32MB for an asset upload. The ceilings are separated by what is being uploaded rather than by how, which is the opposite of the register's other file row. As of 2026-09-22.
| What is uploaded | Ceiling | Why the figure matters here |
|---|---|---|
| A video | 100MB | Conditioning footage or a clip to be extended |
| An image or an audio file | 50MB | Audio is what drives length on this row |
| An asset upload | 32MB | The tightest of the three |
Inclusion rule. Upload ceilings this usage limits page states, grouped by asset type. Output file size is not stated on this page and is therefore not recorded. Order. Largest ceiling first.
1The audio ceiling is the one that interacts with the length
This row's duration figure is governed by a supplied audio track, and the same page caps an audio upload at fifty megabytes. So the two cells are connected: the ceiling on the input is a practical ceiling on how long a performance can be, whatever the thirty minute figure says.
Fifty megabytes is a great deal of speech at ordinary bitrates, so the interaction almost never binds in advertising, where nothing runs past a minute. It is worth recording because it is the only place in the register where a file column limits a duration column.
2Ceilings by asset type rather than by route
The register's other file row separates its ceilings by how a file arrives: a URL, a data URI, an ephemeral upload. This one separates them by what the file is. Two reasonable schemes, and a plan that carries the numbers between them without noticing will compare the wrong pair.
It also means the tightest figure here is the one attached to the vaguest category. An asset upload at thirty-two megabytes is the lowest ceiling on the page and the hardest to know in advance whether a given file falls under.
3Nothing on the page about what comes out
Output size is absent, as it is on thirteen other rows. Given output dimensions run to 4,096 pixels a side and a scene can run thirty minutes, the file that comes back can be very large, and the page states no ceiling on it.
For an ad placement that is the figure a delivery check needs. The one surface here with a published file cap states 500 MB, and whether a piece from this row clears it has to be measured on the file rather than read from either page.
4Where this cell sits in the column
| Generator | File |
|---|---|
| Amazon Nova Reel | Not stated |
| CogVideoX | Not stated |
| Google Veo | Held on the server for 2 days |
| Grok Imagine | Not stated |
| Hedra | Not stated |
| HeyGen | Upload ceilings, 32MB to 100MB |
| Kling AI | Not stated |
| LTX-Video | Not stated |
| MiniMax | Not stated |
| Pika | Not stated |
| PixVerse | Not stated |
| Runway | Input ceilings, 5MB to 200MB |
| SceneMixer | Not stated |
| Vidu | Not stated |
| Wan 3.0 | A URL valid for 24 hours |
Inclusion rule. Every generator in the register against the file column. Most say nothing about files at all, which is why the column is mostly hollow and worth printing. Order. Alphabetical by generator name.
- Upload ceilings100MB for a video, 50MB for an image or an audio file, 32MB for an asset upload
- Output sizeWidth and height must each be between 128 and 4,096 pixelspublished as a range not a ladder
5Sources
Read from the HeyGen usage limits page, checked 2026-09-22. The column itself is described on file, and the rule that keeps surfaces and generators apart is on method. Next along this column: Google Veo, Wan 3.0.