Hailuo H3 is the newest video generation model from MiniMax, the Shanghai AI lab behind the Hailuo video app and the MiniMax text and audio model families. H3 generates native 2K video with synchronized audio in a single pass, at clip lengths up to 15 seconds.
Developed by MiniMax. All credit for the model goes to the MiniMax team. This is a hosted integration, not a weight mirror - H3 is a closed model served through the MiniMax API, and Civitai runs your generations against it so you can work on-site alongside the rest of your library. There are no weights to download here or anywhere else.
Background
MiniMax has shipped video models under the Hailuo name since 2024, moving from the I2V-01 series through Hailuo 02 and Hailuo 2.3. Those earlier models topped out around 1080p with fixed 6 or 10 second clips and no native sound. H3 is the step past that: it raises the ceiling to 2K, opens the clip length to any integer from 4 to 15 seconds, and folds audio generation into the same pass as the picture rather than bolting it on afterward.
Capabilities
• Native 2K output (2560x1440 at 16:9)
• Clips from 4 to 15 seconds, in one second increments
• Synchronized audio generated with the video - dialogue, effects, and ambience timed to what is on screen
• Text-to-video, image-to-video, and first frame plus last frame control
• Omni-reference conditioning: up to 9 reference images, 3 reference video clips, and 3 reference audio clips
• Multi-shot sequences and instruction-based editing
On Civitai
H3 is wired into the video generator across four workflows: Create Video (text only), Image to Video (single first frame), First/Last Frame (both endpoints), and Reference to Video (up to 9 reference images). Resolution is fixed at 2K because that is the only output H3 produces. Aspect ratio is selectable at 21:9, 16:9, 4:3, 1:1, 3:4, and 9:16 for text prompts; when you supply a frame image, H3 adapts the framing to that image instead.
Reference video and reference audio inputs are supported by the model but are not exposed in the Civitai form yet.
Notes
H3 is a new model and MiniMax has not published a full spec sheet or a stable pricing page for it. Behavior and cost may shift as they finish the rollout. Prompt handling follows the usual MiniMax posture - this is a commercially hosted service and content is subject to the provider's policies, so expect refusals on material their API declines.
Links
• MiniMax video generation docs
• Hailuo AI
• MiniMax
• MiniMax Hailuo AI Terms of Service
Description
FAQ
Comments (16)
MINIMAX PLEASE OPENSOURCE YOUR NEXT MODEL ASWELL
no they will not, just look at civitai.red under loras thats why
@RedditUser9811 I feel like if you're developing any kind of creative software in 2026 and you don't go into it expecting this use case, you're beyond naive. I'm sure they already knew where users would take their model when they made the decision to open source it.
No, it's usually bait and switch.
@unbound_rider1 Yep. It's human nature, apparently. Civitai creators are doing that now too. Release an awesome Lora, get people to follow, then start dropping the really high-demand stuff behind a forever paywall.
Don't fret. If they don't, it'll just be another WAN situation where they fall off the map and some other startup looking to make a name will take their spot.
@busy_ad6969 exactly, there is so much competition at the moment we shouldn't have to worry about that. I thought we would have to wait a couple years to reach seedance 2 level for open source but here we are (very close). I think this is the first omni reference for local models!
Is there a solution to the low framerate issue in I2VA/FL2VA mode? Minimax generates fake duplicate frames as if the scene was animated at 12-14 FPS despite being targeted at 24 FPS. I'm using the official comfyui workflow and I tried literally everything, from not having anything related to slow/chopped motion and low framerate in the prompt to explicitly specifying "cinematic smooth motion". Nothing helps. Same issue no matter what, with or without Turbo LoRA and/or SAGE Attention. It seems like the model somehow infers low-fps anime style from my projects and I don't know how to make it synthesize smooth videos without duplicate frames.
Civitai renames all files to "minimax_h3Comfy", so you have to rename them back to what they were supposed to be named manually, just to tell them apart. So dumb.
minimax_h3_video_vae_fp32.safetensors for anyone interested. (probably no visible difference from fp16)
Using the on-site generator, my I2V always comes out 16:9 regardless of the image ratio. Is there something I'm missing?
You can use reference image.
When choosing reference image instead you can choose between different formats.
@reikasama thanks! It works
@hamburglerreturns973 if you want more coherent results, reference images are better anyway. You can even reference start and ending image.
When using on-site Turbo, the image becomes very pixelated. Looks like a bitrate issue. Base works fine.
Details
Files
minimax_h3Comfy.safetensors
Mirrors
minimax_h3_ref2va_pruned_int8_convrot.safetensors
minimaxH3INT8INT4_ref2vaINT8Pruned.safetensors
minimax_h3_ref2va_pruned_int8_convrot.safetensors
minimax_h3_ref2va_pruned_int8_convrot.safetensors
minimax_h3_ref2va_pruned_int8_convrot.safetensors
minimax_h3_ref2va_pruned_int8_convrot.safetensors
minimax_h3_ref2va_pruned_int8_convrot.safetensors
minimax_h3_ref2va_pruned_int8_convrot.safetensors
minimax_h3_ref2va_pruned_int8_convrot.safetensors
minimax_h3_ref2va_pruned_int8_convrot.safetensors
minimax_h3Comfy.safetensors
Mirrors
qwen3vl_32b_minimax_h3_nvfp4_awq.safetensors
qwen3vl_32b_minimax_h3_nvfp4_awq.safetensors
qwen3vl_32b_minimax_h3_nvfp4_awq.safetensors
qwen3vl_32b_minimax_h3_nvfp4_awq.safetensors
qwen3vl_32b_minimax_h3_nvfp4_awq.safetensors
qwen3vl_32b_minimax_h3_nvfp4_awq.safetensors
qwen3vl_32b_minimax_h3_nvfp4_awq.safetensors
qwen3vl_32b_minimax_h3_nvfp4_awq.safetensors
qwen3vl_32b_minimax_h3_nvfp4_awq.safetensors
qwen3vl_32b_minimax_h3_nvfp4_awq.safetensors
qwen3vl_32b_minimax_h3_nvfp4_awq.safetensors
minimax_h3_video_vae_fp16.safetensors
Mirrors
minimax_h3_video_vae_fp16.safetensors
minimax_h3_video_vae_fp16.safetensors
minimax_h3_video_vae_fp16.safetensors
minimax_h3_video_vae_fp16.safetensors
minimax_h3_video_vae_fp16.safetensors
minimax_h3_video_vae_fp16.safetensors
minimax_h3_video_vae_fp16.safetensors
minimax_h3_video_vae_fp16.safetensors
minimax_h3_video_vae_fp16.safetensors
minimax_h3_video_vae_fp16.safetensors
minimax_h3_video_vae_fp16.safetensors
minimax_h3_video_vae_fp16.safetensors
minimax_h3_video_vae_fp16.safetensors
minimax_h3_video_vae_fp16.safetensors
minimax_h3_video_vae_fp16.safetensors
minimax_h3_video_vae_fp16.safetensors
mini_h3_video_vae_fp16.safetensors
minimax_h3_video_vae_fp16.safetensors
minimax_h3_video_vae_fp16.safetensors
minimax_h3_audio_vae_fp32.safetensors
Mirrors
minimax_h3_audio_vae_fp32.safetensors
minimax_h3_audio_vae_fp32.safetensors
minimax_h3_audio_vae_fp32.safetensors
minimax_h3_audio_vae_fp32.safetensors
minimax_h3_audio_vae_fp32.safetensors
minimax_h3_audio_vae_fp32.safetensors
minimax_h3_audio_vae_fp32.safetensors
minimax_h3_audio_vae_fp32.safetensors
minimax_h3_audio_vae_fp32.safetensors
minimax_h3_audio_vae_fp32.safetensors
minimax_h3_audio_vae_fp32.safetensors
minimax_h3_audio_vae_fp32.safetensors
minimax_h3_audio_vae_fp32.safetensors
minimax_h3_audio_vae_fp32.safetensors
minimax_h3_audio_vae_fp32.safetensors
minimax_h3_audio_vae_fp32.safetensors
minimax_h3_audio_vae_fp32.safetensors
mini_h3_audio_vae_fp32.safetensors
minimax_h3_audio_vae_fp32.safetensors
minimax_h3_audio_vae_fp32.safetensors
minimax_h3Comfy.safetensors
Mirrors
minimax_h3_fl2v_lightx2v_turbo_4step_v0.1_comfy.safetensors
minimax_h3_fl2v_lightx2v_turbo_4step_v0.1_comfy.safetensors
minimax_h3_fl2v_lightx2v_turbo_4step_v0.1_comfy.safetensors
minimax_h3_fl2v_lightx2v_turbo_4step_v0.1_comfy.safetensors
minimax_h3_fl2v_lightx2v_turbo_4step_v0.1_comfy.safetensors
minimax_h3_fl2v_lightx2v_turbo_4step_v0.1_comfy.safetensors