MiniMax H3 768p: why 720p is refused and what to send instead

MiniMax H3 renders natively at 768p, not 720p. Sume refuses resolution 720p on H3 and H3 Max and tells you to use 768p. The accepted values per id.

4 min readSume
All posts

If a request to MiniMax H3 on Sume with resolution: "720p" fails, that is by design: H3's native tier is 768p, and Sume's code answers 720p with a message to use 768p. Send 768p or 480p on minimax-h3 or minimax-h3-max.

Native canvas facts are from ComfyUI's H3 tutorial and MiniMax's model card; accepted values from the Sume Video generation docs and validation code, read 2026-09-29.

What is the native size?

ComfyUI's H3 tutorial says H3's native canvas is a 768 px short edge, which is 1344x768 at 16:9, with sizes rounded to a multiple of 32. MiniMax's model card describes H3-Base as the 768p generation module. Sume's docs say 768p is first-class and not 720p.

Which resolutions does each id take?

Accepted resolution values in Sume code and docs, read 2026-09-29.
Value`minimax-h3``minimax-h3-max`
480pAcceptedAccepted
720pRefused, use 768pRefused, use 768p
768pAccepted (default)Accepted
1080pRefusedAccepted, a latent refinement from 768p
2KAccepted, priced upscaleRefused
4KAccepted, priced upscaleRefused

What is the default if I omit resolution?

768p in Sume's pricing code, described there as the product default, not a 2K upscale. A prompt-only request is priced as 5 seconds at 768p.

How do I list what an id accepts?

Call GET /v1/videos/models with your key and read supported_resolutions, supported_durations and supported_aspect_ratios for the id. The 2K and 4K upscales on minimax-h3 do not appear in supported_resolutions, so the table above is the reference for those.

Sources

Related posts

More in Developers

All Developers posts

Written by Sume