MiniMax H3 Max 1080p: a latent refinement from native 768p

MiniMax H3 Max can return 1080p on Sume, but Sume's docs describe that tier as a latent refinement from native 768p: the clip is generated at 768p and refined, not rendered natively at 1080p. Ask for it with model: "minimax-h3-max" and resolution: "1080p"; minimax-h3 refuses 1080p.

Sume facts are from its Video generation and Video Router docs and pricing code; vendor listings from fal's page and MiniMax's API docs, read 2026-09-29.

What does 1080p cost?

Per output second, higher than 768p. Sume bills the provider list × 1.25, plus the 5.5% agent fee by default.

Do the vendors list 1080p for H3 Max?

fal's model page lists 480p, 768p and 1080p for H3 Max. MiniMax's own API docs list only 480P and 768P for it. Sume lists 1080p for minimax-h3-max and documents it as the refinement described above.

How should I check a 1080p clip?

Look at the opening frames. Sume's catalog notes for H3 Max say some 1080p image-to-video outputs have a crop jump after the first two frames. Only when you confirm one, the notes suggest starting the clip at its first stable frame (2/24 seconds for the 24 fps clips observed). Inspect the raw clip before you trim anything.

Should I use 768p instead?

If the delivery target is a phone or a feed, 768p may be enough and costs less per second. Use 1080p when the platform or client requires it. Compare a 768p and a 1080p clip of the same prompt before you commit a batch.