MiniMax H3 has no 1080p on Sume: use H3 Max at $0.20 a second
minimax-h3 on Sume tops out at native 768p (2K and 4K are priced upscales). minimax-h3-max has 1080p at $0.20 a second, refined up from 768p.
minimax-h3 on Sume has native 480p and 768p. It does not list 1080p; 2K and 4K exist only as upscales from 768p, and Sume bills them if your request includes them. For 1080p, use minimax-h3-max, which lists 480p, 768p and 1080p at $0.20 per second at the Sume rate for 1080p.
On H3 Max, 1080p is a latent refinement from native 768p, not a native render, which is worth knowing before you promise a client a true 1080p source.
Rows side by side
Both ids take 5 to 15 seconds, native stereo audio, and the same reference envelope.
| minimax-h3 | minimax-h3-max | |
|---|---|---|
| Resolutions | 480p, 768p (upscales optional) | 480p, 768p, 1080p |
| Native resolution | 480p and 768p | 480p and 768p |
| Sume rate, 480p | $0.0625 per s | $0.0625 per s |
| Sume rate, 768p | $0.075 per s | $0.10 per s |
| Sume rate, 1080p | not offered | $0.20 per s |
Using the 1080p tier well
Check the opening frames of 1080p image-to-video clips before you assemble them. The catalog notes that some outputs show a baked crop jump after two frames, and suggests trimming to the first stable frame with a timeline source_in only when you have confirmed the problem. Use a draft at 768p first to see the motion, then spend the extra $0.10 per second on the keeper.
A 10-second 1080p H3 Max clip is $2.00. The same clip at 768p is $1.00.
Pick H3 or H3 Max
If 768p is enough, H3 at $0.075 per second is the cheaper id, 25% under H3 Max at the same resolution. If you need 1080p, there is no choice: it has to be H3 Max. Neither id accepts a request for a resolution it does not list, so confirm the row before you submit.
Before you submit
A few checks stop a wasted job.
If you only deliver on mobile, 768p often suffices, and the money saved pays for more takes. Save 1080p for the clips that will be shown large.
On minimax-h3, reference images past the fifth carry an extra per-image charge, so reference-heavy clips cost more than the per-second figure suggests. Read the H3 Max row for how it bills references.
- Ask for 1080p only on
minimax-h3-max. - Keep duration between 5 and 15 seconds.
- Stay under 12 reference items and never send audio alone.
- Remember 2K and 4K on
minimax-h3are priced upscales from 768p.
Sources
Related posts
More in Models
- MiniMax H3 open weights: 768p locally, 2K only hosted
MiniMax's open H3 Base checkpoints top out at 768p. The 2K tier needs a proprietary module. What that means if you want to self-host or call H3 through Sume.
- MiniMax H3 Max 1080p: docs list 768P, Sume lists 1080p
MiniMax's own guide gives H3 Max 480P and 768P. Sume's minimax-h3-max row also lists 1080p. Here is the gap, and what the extra tier means for you.
- MiniMax H3 audio references: 2 to 15 s each, 15 s combined
On Sume, MiniMax H3 audio references must be 2 to 15 seconds each, 15 seconds combined, at most 3 files, and never the only reference. Here is how to prep them.
- MiniMax H3 reference limits: 9 images, 3 videos, 3 audios on Sume
MiniMax H3 reference-to-video on Sume takes up to 9 images, 3 videos and 3 audio clips, 12 in total. The duration rules, the extra-image fee and a request.
Written by Sume