minimax-h3 vs minimax-h3-max on Sume: price per clip at 768p and 1080p
At 768p, minimax-h3-max costs $0.10 a second on Sume against $0.075 for minimax-h3. 1080p exists only on Max. Per-clip prices for 5, 10 and 15 seconds.

At 768p, Sume charges $0.10 per second for minimax-h3-max and $0.075 for minimax-h3, so Max costs 1.33x as much (0.10 / 0.075). Only Max lists 1080p, at $0.20 per second. Both take 5 to 15 seconds. Prices are provider list x 1.25 from the repo pricing table, as of 2026-10-08; Sume's docs call Max the faster 768p variant.
Per-second and per-clip prices
Per-clip = seconds x the per-second price.
| Sume model id | Resolution | Per second | 5 s clip | 10 s clip | 15 s clip |
|---|---|---|---|---|---|
| minimax-h3 | 480p | $0.0625 | $0.3125 | $0.625 | $0.9375 |
| minimax-h3 | 768p | $0.075 | $0.375 | $0.75 | $1.125 |
| minimax-h3-max | 480p | $0.0625 | $0.3125 | $0.625 | $0.9375 |
| minimax-h3-max | 768p | $0.10 | $0.50 | $1.00 | $1.50 |
| minimax-h3-max | 1080p | $0.20 | $1.00 | $2.00 | $3.00 |
What the docs say separates them
Both are in the same catalog and reached through the same endpoint; the differences below are from Sume's video docs.
minimax-h3: 5 to 15 seconds at native 480p or 768p; Sume bills 2K or 4K upscales if the request includes them.minimax-h3-max: the faster 768p variant, with text-to-video, first and last frame, and reference-to-video at 480p, 768p and 1080p; 1080p is a latent refinement from native 768p.- Both report image, video and audio input references; Sume's docs describe native stereo audio for
minimax-h3-max.
When the premium is worth it
The extra $0.025 per second at 768p adds $0.125 to a five-second clip (5 x ($0.10 - $0.075)). On 200 clips that is $25.00 a month. If Max's speed or its 1080p output saves a re-run or a separate upscale, it can pay for itself; if you draft at 480p, both ids cost the same $0.0625 per second.
A cheap loop is to draft on minimax-h3 at 480p, $0.3125 for five seconds, and move the keepers to a higher tier.
Open weights and the hosted ids
MiniMax's H3 page says the open weights generate natively at 768p and that 2K output uses API-only stages. Sume does not claim parity with local weights, and its docs do not list a 2K tier for minimax-h3-max. The H3 license excludes the EU, UK, US and South Korea for the weights, which is another reason many teams use a hosted id.
A simple test plan
Run the same five prompts on both ids at 768p, five seconds each. The cost is 5 x $0.375 = $1.875 on minimax-h3 and 5 x $0.50 = $2.50 on minimax-h3-max. Compare motion, audio and prompt adherence yourself; this post does not rank their quality, because the pages cited give no Sume-side benchmark.
What the repo table covers
The prices above come from the repo's provider pricing table, multiplied by 1.25 as the Sume docs describe. The H3 family also has h3-max-recast, a separate catalog entry that takes one source video plus one to four person photos at 768p or 1080p for 5 to 30 seconds. It is a different tool from text-to-video, so it is not priced in this comparison.
Sources
Related posts
More in Pricing
- Omni Flash forecast: 200, 500 or 2,000 eight-second clips a month
A monthly forecast for gemini-omni-flash-1.1 on Sume: 200, 500 or 2,000 eight-second clips cost $60 to $6,000 depending on resolution. Four-column table.
- The most one Sume TTS request can cost: $0.95 at 20,000 characters
One maximum Sume TTS request of 20,000 characters is $0.95. MAI-Voice-2.1 would be $0.44 and Flash $0.30 for the same characters. Arithmetic shown.
- Museum audio guide: 40 stops at 600 characters, voice cost
A 40-stop audio guide at 600 characters a stop is 24,000 characters: $0.528 on MAI-Voice-2.1, $0.36 on Flash, $1.20 on Sume as 40 jobs.
- Music 1.0 at $0.125 a generation: budget five takes per final track
Music 1.0 has no seed or duration field, so plan retries. At a fixed $0.125 a generation, five takes cost $0.625 and 12 tracks at five takes cost $7.50.
Written by Sume