CogVideoX and HeyGen, three hundred times apart
Six seconds at forty-nine frames against thirty minutes per scene with fifty scenes per video. The ratio is three hundred to one, which is the widest gap anywhere in this register, and it marks the boundary between two product categories rather than two grades. As of 2026-09-22.
| What the pages state | CogVideoX | HeyGen |
|---|---|---|
| Longest single run | 6 seconds, fixed | 30 minutes per scene |
| Assembly inside the product | None stated | 50 scenes per video |
| What sets the length | A 49 frame budget at 8 fps | How long the supplied audio runs |
Inclusion rule. The length figures each page states, and what each page says decides them. No figure here is converted or combined. Order. The single-run figure first, then what surrounds it.
1The gap is a category boundary, not a ranking
One figure comes out of a frame count: forty-nine frames at eight a second, rounded to six seconds. The other comes out of a speech file: the picture runs for as long as the audio does, and thirty minutes is where file handling stops.
Ranking them would say that one product is three hundred times better at the same job, which is not what either page claims. The honest reading is that a prompt-driven scene and an audio-driven performance are answers to different briefs that happen to share a unit.
2Against a sixty second slot the two behave completely differently
Ten runs and nine joins against one run and no joins. On the short row every seam has to hold a face, a key light and a background across separate inferences that shared nothing. On the long row the question of seams does not arise.
Impression billing sharpens that. A non-skippable slot delivers and charges for its whole length, so a visible join is a second the advertiser paid to show. The join count is the number this pair actually decides.
3What each page does not say
Neither publishes anything about how many attempts a usable take costs, and neither publishes an output file size. The short row states its frame rate at eight a second, which is a stronger constraint on whether the output belongs in a paid placement than the length ever was.
The long row publishes output dimensions as a range up to 4,096 pixels a side and says nothing about the size of the resulting file. Against a surface that caps an upload at 500 MB, that is the figure a delivery check would want and neither page provides.
4The rest of the column behind these two
| Generator | Duration |
|---|---|
| Amazon Nova Reel | 6 s increments, up to two minutes |
| CogVideoX | 6 s, at 49 frames |
| Google Veo | 4, 6 or 8 s |
| Grok Imagine | 1 to 15 s |
| Hedra | 10 minutes |
| HeyGen | 30 minutes per scene |
| Kling AI | Not stated |
| LTX-Video | Frames, never seconds |
| MiniMax | 4 to 15 s |
| Pika | 5 s and 10 s, 20-25 s on Pikaframes |
| PixVerse | 1 to 15 s on version 6 |
| Runway | 5 to 15 s on Gen-4.5 |
| SceneMixer | Thirty seconds on the Wan tiers, fifteen on H3 |
| Vidu | Not stated |
| Wan 3.0 | 2 to 30 s |
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. Three hundred to one is not a difference of degree. One page publishes a frame budget from a research release, the other publishes a performance bound by a speech file, and putting them in one column is only useful if the reason is printed beside the numbers.
- Video length6 seconds, at 49 framesfrom the model card table
- Longest output stated anywhere in this register30 minutes per scene, with 50 scenes per video
5Sources
Read from the CogVideoX-5B model card and the HeyGen usage limits page, both checked 2026-09-22. The column is described on duration, and each entry has its own cell page at CogVideoX and HeyGen, and the rule that keeps surfaces and generators apart is on method. Nearby pairs: Wan 3.0 and Veo, Nova Reel and Runway.