PixVerse publishes a length per model version
The capability map publishes one to fifteen seconds on version 6 and c1, and the pricing page prices five, eight or ten on versions 5.5 and 5.6, with ten unavailable at 1080p. Length here is a property of the version, and the older versions block their own longest value at the top tier. As of 2026-10-25.
| Version | Duration | Condition |
|---|---|---|
| v6 and c1 | 1 to 15 | None stated |
| v5.5 and v5.6 | 5, 8 or 10 | 1080p cannot use 10 |
| All versions | 360p to 1080p | The quality parameter is shared |
Inclusion rule. Model versions the capability map and the pricing page name, with the duration values they state for each. A version mentioned only in a changelog is not given a row. Order. Newest version first, as the page lists them.
1Version is part of the specification here
Four versions appear across two pages with two different duration rules between them. A brief written against fifteen seconds is a brief written against v6 or c1, and a request that silently lands on 5.6 is capped at ten with no error that mentions versions.
That makes the version string a spec field rather than a housekeeping detail. It belongs in the shot list beside the length, in the same way the model identifier does on the row that gates its ceiling behind one.
2The older versions couple length to resolution the other way round
One other row in this register withholds its longest length below a resolution tier. This one withholds its longest length at the top tier: on 5.5 and 5.6, ten seconds is unavailable at 1080p. The coupling runs in the opposite direction, and a plan that learned the rule from one row gets it backwards on the other.
Read as engineering rather than policy it makes sense: the constraint is compute per frame, and either the frames or the seconds have to give. Read as a spec it is a trap, which is why the condition sits in the table beside the value it removes.
3A one second floor and a fifteen second ceiling on the same row
Version 6 publishes the widest usable range in this column among prompt-driven generators: any whole value from one to fifteen. One row matches its ceiling and another doubles it, but neither reaches as far down.
For assembly that range is the useful property. A minute is four pieces at the top of the range, and the beats that join them can be generated at their real length rather than cut out of something longer that was paid for in full.
4Where this cell sits in the column
| 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 with a row in this register, carrying whatever its own page states as a length. A page that states none keeps its row and says so. Order. Alphabetical by generator name.
- Video duration row1~15 on v6 and c1stated per model version
- Fixed-price tables for the older versions; ten seconds is not supported at 1080p5/8/10 on v5.5 and v5.6, where 1080p cannot use 10
- Quality parameter360p, 540p, 720p and 1080p
5Sources
Read from the PixVerse capability map and pricing page, checked 2026-10-25. The column itself is described on duration, and the rule that keeps surfaces and generators apart is on method. Next along this column: Runway, SceneMixer.