Step 1 – Update ComfyUI
Use a current ComfyUI build compatible with current H3 support.
Installation and support
MiniMax H3 can run locally in current ComfyUI workflows for text-to-video, image-to-video and reference-based generation. Local setup requires the correct H3 model files, a compatible ComfyUI build and enough GPU and system memory for the selected workflow.
This guide focuses on installation, model placement, hardware constraints and troubleshooting. For ready-to-import JSON files, use MiniMax H3 workflow JSON downloads.
Last reviewed: September 15, 2026
Yes. MiniMax H3 can run locally through current ComfyUI-compatible workflows for text-to-video, image-to-video and reference-based generation.
The main practical constraint is hardware. MiniMax does not publish one universal VRAM requirement for every H3 setup because memory use depends on model format, workflow, resolution, video length, system RAM and offloading. If you only need JSON files, use the MiniMax H3 workflow JSON downloads; if you need to make a local graph run, continue below.
Install a current ComfyUI build, download the required H3 diffusion model, text encoder and video/audio VAE components, place them in the correct ComfyUI model directories, then import a compatible H3 workflow JSON. Hardware requirements depend on workflow, resolution, duration, model precision and offloading.
ComfyUI/
└── models/
├── diffusion_models/
├── text_encoders/
└── vae/Place the required MiniMax H3 diffusion model here.
Place the required H3-compatible text encoder here.
Place the required video and audio VAE components here.
Exact filenames may change as official or community packages evolve. Verify the current model repository rather than relying on historical filenames. See the MiniMax H3 model guide for model-family definitions.
Use a current ComfyUI build compatible with current H3 support.
Choose T2V, I2V, FL2VA or R2V / Ref2VA from the separate workflow library. Do not download every graph by default. Download workflow JSON files from the MiniMax H3 Workflow Library.
Obtain the H3 diffusion model, compatible text encoder, video VAE and audio VAE required by the selected workflow.
Place each component in its matching diffusion_models, text_encoders or vae directory.
Open ComfyUI and load the JSON from the MiniMax H3 workflow library.
Use ComfyUI Manager or the appropriate package installation process, restart ComfyUI, and reload the graph.
Start with lower resolution and shorter duration before increasing either setting.
Observe GPU VRAM, system RAM and the VAE decoding stage during the first run.
| Input | Workflow |
|---|---|
| Text | T2V |
| One image | I2V |
| First + last frame | FL2VA |
| Multimodal references | R2V / Ref2VA |
Download all currently verified JSON files in the MiniMax H3 Workflow Library.
Configuration-dependent
Likely causes include insufficient VRAM, high resolution, long duration or a high-precision model.
Configuration-dependent
The text encoder may create memory pressure before generation starts.
Configuration-dependent
Sampling can finish successfully and the job can still fail while decoding video.
Setup issue
The workflow may require a newer ComfyUI build or node package.
Setup issue
A model component is absent, placed in the wrong directory or not selected by the loader.
Community-reported issue
Some users report dark output in particular workflow, precision, VAE or sampler combinations. This is not established as a universal H3 defect.
Configuration-dependent
Video diffusion is compute-intensive; CPU offloading, VRAM pressure, precision, resolution and duration can all add latency.
These answers distinguish official requirements from MiniMax3 tests, community measurements and inference. For the primary hardware analysis, use MiniMax H3 local hardware requirements.
Unverified / evidence-scoped
No single official minimum covers every setup. Model format, workflow, resolution, duration, system RAM and offloading determine memory use.
Unverified / evidence-scoped
Unverified as a general recommendation. Treat any successful 12GB report as configuration-specific community evidence, not an official requirement.
MiniMax3 tested
MiniMax3 has recorded a reproducible optimized 16GB configuration, but that result does not prove every 16GB GPU or workflow will run.
Inference
A 24GB RTX 4090 is a practical candidate, but this is an inference from capacity and community configurations rather than an official compatibility guarantee.
Inference
A 32GB RTX 5090 is a practical candidate, but workflow settings can still cause OOM and no universal performance figure applies.
Unverified / evidence-scoped
Do not assume parity with CUDA workflows. Current framework, precision and memory-support details must be checked for the exact Apple Silicon configuration.