MiniMax Hailuo 2.3 vs H3 API: model ids, durations, prompt limits
MiniMax's API still lists MiniMax-Hailuo-2.3 (6 or 10 s, 2,000-character prompt) beside MiniMax-H3 (4-15 s, 7,000). Which one Sume lists, and why it matters.
MiniMax's current API docs carry two generations side by side: MiniMax-Hailuo-2.3 (and 02) with 6 or 10 second clips and a 2,000-character prompt, and MiniMax-H3 with 4 to 15 seconds and a 7,000-character prompt (both read 2026-10-02). Sume's catalog lists minimax-h3 and minimax-h3-max and no Hailuo 2.3 id, so a Hailuo 2.3 integration needs a rewrite of durations and prompts, not just a model-name swap.
How do the two generations differ in the docs?
The Hailuo 2.3 limits come from MiniMax's text-to-video reference; the H3 limits come from its video generation guide. The H3 guide also covers reference images, videos and audio, which the Hailuo reference does not.
| Model id | Durations | Resolutions | Prompt limit |
|---|---|---|---|
| MiniMax-Hailuo-2.3 | 6 s or 10 s | 768P default, 1080P at 6 s only | 2,000 characters |
| MiniMax-H3 | 4-15 s, integers | 768P, 2K | 7,000 characters |
| MiniMax-H3-Max | 5-15 s, integers | 480P, 768P | 7,000 characters |
What does Sume list?
Per Sume's video router docs, minimax-h3 takes 5 to 15 seconds at native 480p or 768p, and minimax-h3-max takes 5 to 15 seconds at 480p, 768p and 1080p, where 1080p is a latent refinement from native 768p. Both accept text-to-video, first and last frame, and reference-to-video, with native stereo audio and no audio toggle.
Notice the gaps. Sume's H3 minimum is 5 seconds even though MiniMax lists 4 for H3, and Sume prices by catalog list times 1.25 rather than MiniMax's own rate card. Check GET /v1/videos/models for the live envelope before you code against any number in a blog post.
What breaks when you migrate from Hailuo 2.3?
- Duration: 6 and 10 second requests need 5 to 15 second values; any value in between is valid on H3.
- Prompt: a 2,000-character budget grows to 7,000 on MiniMax's side, so prompts written for Hailuo fit with room to spare.
- Resolution: Hailuo's 1080P is limited to 6 seconds on MiniMax's page; Sume's
minimax-h3-maxlists 1080p across its 5 to 15 second range, as a refinement rather than native output. - Camera control: Hailuo's bracket commands are a Hailuo feature; on H3 write camera language in the prompt and test it.
Which should you pick?
If you already ship on Hailuo 2.3 and only need 6 or 10 second clips, staying on MiniMax's own API keeps your behavior unchanged. If you want one API for several video families, minimax-h3 or minimax-h3-max on Sume's /v1/videos route is the nearest match, with the changes above.
Sources
Related posts
More in Models
- Hailuo camera commands: the 15 bracket options like [Push in]
MiniMax's Hailuo API reads 15 camera commands in square brackets, such as [Truck left] or [Push in]. The full list, and what to do on Sume.
- Hailuo first frame image limits: 20 MB, 300 px, 2:5 to 5:2
MiniMax's Hailuo image-to-video wants JPG, PNG or WebP under 20 MB with a short edge over 300 px; H3 frame images list 256-5760 px and 30 MB. Compare both.
- MiniMax video API error 1026 and 1027: sensitive content
MiniMax returns 1026 when the input is flagged and 1027 when the generated video is. What 1002, 1008 and 2013 mean, and how Sume reports failures.
- MiniMax video callback_url: echo the challenge in 3 seconds
MiniMax checks a callback_url by POSTing a challenge you must echo within 3 seconds. Sume skips the handshake and signs each terminal webhook instead.
Written by Sume