One reference page, two models that disagree
One API reference documents two models. They share a fifteen second ceiling, differ by a second at the floor, and carry resolution ladders that cross rather than nest. Neither model is the more capable on both columns. As of 2026-09-22.
| What the pages state | MiniMax-H3 | MiniMax-H3-Max |
|---|---|---|
| Duration range | 4 to 15 seconds | 5 to 15 seconds; four is unsupported |
| Resolutions | 768P and 2K | 480P and 768P; 2K is unsupported |
| Aspect ratios | Six, required for text-to-video | The same six |
Inclusion rule. Values this API reference states for each model it documents. Earlier model generations are not given rows. Order. As the reference orders the models.
1One second at the floor is the length of an insert
A four second beat exists on one model and not the other. For a cutaway or a join that is the whole request, so the shot list either gets regenerated at five and trimmed or re-cut around a model chosen for unrelated reasons.
Ceilings get the attention because they decide join counts. Floors decide what the smallest useful request is, and in short-form advertising a campaign is mostly made of small requests.
2The ladders cross, so only the middle rung is safe
One model reaches 2K and has no cheap rung. The other has 480P and cannot reach 2K. 768P is the value available whichever model a request names, and anything above or below it pins the request to one model and its duration floor.
Usually a cheaper model is a subset of a dearer one and a plan can be made against the union. Here the union does not exist as a single product, which is the practical content of this comparison.
3The shape column is the one thing they agree on
Six ratios, required on the text path and never adaptive, apply to both. So shape is the axis where the model choice does not matter, and duration and resolution are the two where it decides everything.
A vertical piece at the cheapest available tier resolves to one model and a five second floor. The same piece at 2K resolves to the other and a four second floor. The ratio parameter has to be supplied either way.
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. A register carrying one line per vendor would be wrong for half the requests made against this one. The floor moves, the top rung disappears, and the model with the higher floor is the one missing the higher rung.
- 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 is described on duration, and each entry has its own cell page at MiniMax, and the rule that keeps surfaces and generators apart is on method. Nearby pairs: Runway and SceneMixer, Veo and Wan 3.0 on retention.