ArtArch Newsroom
AcademyMiniMax H3 API Media Formats and URL Input Checklist
Prepare MiniMax H3 API media with supported codecs, image and audio formats, file limits, 64 MB request bodies, and URL-based inputs.
MiniMax H3 API media formats and URL input checklist
MiniMax H3 API media formats need validation before a multimodal request is assembled. A file that plays locally may still use an unsupported codec, exceed a per-file limit, or push the request body beyond its cap. The launch manual recommends URL-based inputs because the API body is limited to 64 MB.
Treat transport checks and creative checks as separate preflight stages.
Validate containers, codecs, and files
For video, the manual lists H.264/AVC and H.265/HEVC, with AAC or MP3 audio. Each video file is limited to 50 MB. Reference videos must last 2 to 15 seconds, and all video references in one request total at most 15 seconds.
Supported image formats are JPG, JPEG, PNG, WEBP, HEIC, and HEIF, with a 30 MB per-file limit. Standalone audio references can be WAV or MP3 and are limited to 15 MB each. Audio clips also follow the 2-to-15-second rule and 15-second combined total.
Prefer verifiable URL inputs
Before submitting a URL, confirm that the service can fetch it without an interactive login, expired session, or blocked redirect. Check the final response status, content type, size, and that the bytes decode as the expected media. Use stable URLs for a reviewable production workflow.
Do not assume that an upload response proves the CDN object is available. Read the delivered URL back and verify the real media.
Check the assembled request
Omni Reference accepts up to nine images, three videos, and three audio clips, with 12 mixed files maximum. Audio cannot be the only input. Confirm that every URL maps to the prompt's named role and that the prompt stays within 7,000 characters.
After generation, verify the returned video itself: it should decode, report the expected duration and frame rate, include audio, and match the requested aspect ratio. A successful request status alone is not acceptance.
Frequently asked questions
What is the H3 API body limit?
The manual lists 64 MB and recommends URL input.
Are MOV and MP4 automatically supported?
Check the underlying codec. The listed video codecs are H.264/AVC and H.265/HEVC with AAC or MP3 audio.
Can audio be the only URL in a request?
No. Audio references must accompany image or video input.
Validate codecs, duration, size, access, reference roles, and final media readback in ArtArch before treating an H3 API workflow as complete.
Keep exploring
More in Academy
MiniMax H3 Production Checklist for Commercial Video Teams
Review MiniMax H3 inputs, rights, prompt scope, identity, product accuracy, audio, format, retries, approvals, and delivery before production.
How to Plan 12 Reference Files for MiniMax H3
Assign clear identity, product, style, motion, camera, and audio roles across a MiniMax H3 mixed request without creating contradictory references.
Use MiniMax H3 for Storyboard and Visual Pitch Previews
Turn keyframes and a creative brief into a MiniMax H3 motion preview for shot order, transitions, timing, sound, and stakeholder review.
MiniMax H3 Clay Animation Prompt for Dynamic Action
Write a MiniMax H3 clay animation shot with material rules, a readable action arc, dramatic camera movement, scale cues, and physical continuity.