MiniMax publishes two ranges for two models
The API reference publishes four to fifteen seconds on MiniMax-H3 and five to fifteen on H3-Max, stating that four seconds is not supported on the second. The ceiling is shared; the floor is not, and the model with the higher floor also drops the highest resolution. As of 2026-09-22.
| Model | Duration range | What it does not carry |
|---|---|---|
| MiniMax-H3 | 4 to 15 seconds | 480P is not among its resolutions |
| MiniMax-H3-Max | 5 to 15 seconds | Four seconds and 2K are both unsupported |
| Both | Fifteen seconds at the top | Nothing; the ceiling is common |
Inclusion rule. Models this API reference documents for video generation, with the duration and resolution values the same page states for each. Earlier model generations are not listed. Order. As the reference orders the models.
1A vendor-internal difference is easy to flatten
A register that carried one line per vendor would print four to fifteen seconds here and be wrong for half the requests made against it. The floor moves by a second between two models sold from the same reference page, and a four second beat exists on one and not on the other.
One second sounds trivial until it is the length of an insert. A cutaway written at four seconds either gets regenerated at five and trimmed, or the shot list is re-cut around the model that was chosen for reasons unrelated to duration.
2The ranges move in the opposite direction from the tiers
The model with the narrower duration range is also the one missing the highest resolution: H3 carries 768P and 2K, H3-Max carries 480P and 768P. So the two axes disagree about which model is the more capable, and neither ordering is the vendor's.
That is why these sheets keep the columns apart. A single verdict about MiniMax would have to pick an axis to be right about, and a buyer choosing on resolution and a buyer choosing on a four second floor need opposite answers.
3Fifteen seconds is where the joins start
The shared ceiling is what a plan actually runs into. A five to six second bumper is one call. Thirty seconds is two, sixty is four, and each of those joins has to hold a face and a key light across separate requests.
Four calls is the middle of this register rather than the worst of it. Two rows here need eight or ten for the same minute, and three need one. The number that decides it is this ceiling, and the floor only decides what the last piece is allowed to be.
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.
- Durations4-15 seconds on MiniMax-H3, and 5-15 on H3-Max where 4 seconds is not supportedstated per model
- Resolutions768P and 2K on MiniMax-H3; 480P and 768P on H3-Max, where 2K is not supportedstated per model
5Sources
Read from the MiniMax video task reference, checked 2026-09-22. The column itself is described on duration, and the rule that keeps surfaces and generators apart is on method. Next along this column: Pika, PixVerse.