Launch
MiniMax published the H3 announcement on 2026-07-31.
Official MiniMax H3 page
Independent MiniMax H3 tracker
H3 is MiniMax's July 31, 2026 general-purpose multimodal generation model. This page turns the launch into a practical check: what is official, what still needs proof, and how to run a first evaluation without confusing H3 with older Hailuo or M-series models.
Quick answer
MiniMax H3 is a general-purpose multimodal generation model for creative video work. The official announcement says H3 understands unified context across text, images, video, and audio, and can generate video with native stereo sound up to 15 seconds at 2K resolution. The same announcement says model weights are planned in the coming days, which means production teams should separate the launch claim from the later verification packet.
Launch
Official MiniMax H3 page
Input context
Official MiniMax H3 page
Output
Official MiniMax H3 page
Weights
Official MiniMax H3 page
Core technology
Official MiniMax H3 page
Verification gap
MiniMax API docs and official H3 page
Do not mix these up
H3 sits in MiniMax's H-series video generation line, but it is not just a longer Hailuo 02 setting. It is framed around task and modality generalization. M3 belongs to the M-series frontier model line and is useful context for MiniMax's broader multimodal work, not a substitute H3 source.
Evaluation planner
Pick the creative job, the input mix, and the proof that matters most. The planner gives a starter sequence you can copy into your team's test sheet.
Choose a job and generate a first H3 evaluation sheet.
Acceptance checklist
A good MiniMax H3 test should be small enough to repeat and strict enough to reject a beautiful but unusable clip. Use this checklist when the team moves from launch reading to a real evaluation packet.
Save the official MiniMax H3 announcement, the exact API documentation you used, any model-weight page, license terms, tokenizer notes, and hardware guidance. If one item is missing, record it as a launch gap instead of hiding it inside a generic model note.
Run at least twelve prompts across the same jobs your team cares about: product shot, brand spot, UI motion, scene extension, motion transfer, and audio-led timing. Keep the text, image, video, and audio references attached to every output for later review.
Score each result on instruction following, small text, color accuracy, character continuity, audio-video sync, editability, and the cost per accepted second. A clip should pass the brief, a regenerate, and one edit pass before it counts as usable evidence.
Do not call MiniMax H3 self-hosted until weights, terms, inference recipe, and hardware notes are public and archived. For hosted API tests, keep the current model name, price, rate limits, safety rules, and data handling policy in the acceptance sheet.
The point is not to prove MiniMax H3 is best from one launch demo. The point is to know whether MiniMax H3 can survive the exact multimodal workflow your team would otherwise send to a designer, editor, or motion system. Keep rejected examples because they often explain the real integration risk better than polished winners.
A pass is a clip that keeps the same object, timing, camera intent, and sound cue after a regenerate. MiniMax H3 should also preserve the reason each source was included, so reviewers can explain which text, image, video, or audio reference shaped the final result.
A review signal is not a failure. It means MiniMax H3 produced something promising but exposed a boundary: weak small text, drifting color, uncertain license status, unclear API naming, missing weight files, or audio that works in a browser but falls apart in editing software.
A stop signal is any result that looks good only as a single demo. If the second prompt loses the product, the stereo track is decorative, the edit path is unclear, or the model source cannot be archived, keep MiniMax H3 in research mode instead of a production plan.
Where the launch matters
Test logo text, product color, camera movement, sound design, and whether the clip survives a second edit pass without losing the brief.
Use H3 when a storyboard needs image references, interface surfaces, narration timing, and video transitions in the same request.
Evaluate character consistency, cut rhythm, audio-video alignment, and whether a short clip can be reused inside a larger sequence.
Wait for public weights and terms before promising self-hosting; prepare hardware, tokenizer, and inference checks now.
Common questions
MiniMax published the H3 launch article on July 31, 2026. Treat model weights, API names, tokenizer files, and license terms as items to verify before production adoption.
The promise is unified multimodal generation: text, images, video, and audio can sit in one context, and H3 can produce video with native stereo sound.
MiniMax says it plans to open the model weights in the coming days, subject to laws and regulations. This site does not mark self-hosting ready until those files and terms are public.
Start with a small creative acceptance sheet: 12 prompts, four input mixes, one cost column, one editability column, and one human review note per accepted second.