MiniMax H3 vs H3-Max limits: the MiniMax page next to Sume's catalog
MiniMax lists H3 at 4 to 15 s and H3-Max at 5 to 15 s with different resolutions. Sume's catalog states its own ranges. Side by side, with the file-size limits.
On the MiniMax guide, H3 accepts 4 to 15 second clips at 768P or 2K, and H3-Max (listed with fal.ai) accepts 5 to 15 seconds at 480P or 768P. Sume's catalog states its own ranges for minimax-h3 and minimax-h3-max, which do not match the MiniMax page row for row, so read both before you code against either.
The two sources side by side
The two sources disagree in small ways that matter for validation. The table lists them as stated on 2026-10-03.
| Model | MiniMax page | Sume docs |
|---|---|---|
| H3 | 4 to 15 s; 768P and 2K | minimax-h3: 5 to 15 s; native 480p and 768p; 2K or 4K upscales priced if requested |
| H3-Max | 5 to 15 s; 480P and 768P | minimax-h3-max: 5 to 15 s; 480p, 768p, 1080p (a latent refinement from native 768p); native stereo audio |
Reference and file limits on MiniMax
The MiniMax page also lists a prompt limit of 7,000 characters, up to 9 reference images, up to 3 reference videos, and up to 3 reference audio files. File limits are 50 MB for video, 30 MB for images, and 15 MB for audio. Those are MiniMax's limits for its own API.
What Sume accepts
Sume documents its own reference vocabulary. On the legacy Video 1.0 route, reference_image_urls takes 1 to 9 images, reference_video_urls takes 1 to 3 videos, and reference_audio_urls takes 1 to 3 audio files and needs at least one image or video. Media must be public HTTPS URLs. The video docs say MiniMax H3 and H3 Max honor audio and video references.
Why catalogs and vendor pages differ
A platform that serves a model often applies its own limits. It may enforce a stricter minimum, add an upscale step, or expose only some variants. Neither side is wrong: the vendor page describes the model, and the catalog describes what that platform will accept.
The practical rule is to validate against the catalog you will call. Vendor pages are for understanding capability, and the live catalog is for writing validation. If the two disagree, the catalog wins for your integration, and the disagreement itself is worth a line in your internal notes.
- Vendor page: what the model can do.
- Platform catalog: what this API accepts.
- Your validator: built from the catalog, tested monthly.
- Disagreements: record with the date read.
A practical check
Because Sume's minimum is 5 seconds for minimax-h3, a 4 second request that works on MiniMax can return a validation error on Sume. Query the catalog rather than hard-coding, and validate duration against supported_durations before you submit.
curl "https://api.sume.com/v1/videos/models" \
-H "Authorization: Bearer $SUME_API_KEY"
# read supported_durations and supported_resolutions
# on the minimax-h3 and minimax-h3-max rowsSources
Related posts
More in Comparisons
- Pika API Club: 100+ models at reduced pricing, questions to ask first
Pika's API Club (Aug 5) offers 100+ models at reduced pricing, and the Sep 17 relaunch adds audio models. Seven questions to ask an aggregator.
- Capacity fallbacks: Replicate's model swap vs pinning on Sume
Replicate lists a model falling back to another at capacity. On Sume you pin a model or send sume/auto, and a capacity error is retried with the same key.
- Prediction deadlines vs a Sume client deadline: stopping isn't cancel
A client-side deadline stops you watching a Sume job; it does not cancel it. Cancel works only before generation starts, so a missed deadline still bills.
- Runway enterprise exception requests vs Sume's queue-first admission
Runway's docs mention enterprise exception requests for higher volume. Sume takes extra jobs as queued and sets concurrency by plan. How to plan a big batch.
Written by Sume