Decision page · H3 versus H3 Max

Pick the route that matches the deliverable.

MiniMax H3 is the wider multimodal model. H3 Max is the faster, narrower route. This comparison uses published API contracts and provider-specific pricing; it does not declare a universal quality winner.

Last source check · 04 Sep 2026

Published capability comparison · checked 04 Sep 2026
Decision fieldMiniMax H3MiniMax H3 Max
Primary jobGeneral-purpose multimodal productionFast prompt-led and keyframe-led iteration
InputsText, image, video and audio referencesMiniMax direct: text and first/last-frame image
Resolution768P and 2K480P and 768P
Duration4–15 seconds5–15 seconds
AudioNative stereo audioGenerated with the clip on documented routes
Extra tasksContext-IR and 768P → 2K regenerationVideo generation task only on MiniMax direct API
Published rateMiniMax: $0.08/s at 768P; $0.13/s at 2KMiniMax direct rate unavailable; fal: $0.05/s at 480P and $0.08/s at 768P

Scenario guide

A route decision in two questions

Short, fast, reversible

Is 480P or 768P enough?

If yes, and you are iterating prompt or keyframe ideas, H3 Max is the focused route. A fal rate estimate is available in the cost calculator.

Control and resolution

Do you need 2K or references?

If yes, start with H3. The official H3 contract covers the broader multimodal reference and regeneration workflow.

Source boundary

Speed and quality need a matched test

fal reports a five-second 768P H3 Max clip in under three seconds on its stack. That is a provider statement, not a runtime result from this directory; queue, upload and download time still vary.

Read MiniMax video docs → Read fal H3 Max guide →

Provider speed statement · Open reference · checked 04 Sep 2026