Templates · Dependencies · Disk size

MiniMax H3 ComfyUI workflow templates

Comfy-Org ships six official MiniMax H3 templates. Three run on your own GPU, three call the hosted API. This page lists what each one loads and what has to be on disk first.

Checked 2026-08-13 · Independent guide, not affiliated with MiniMax or Comfy-Org

Official templates

The six official templates

TemplateRuns whereDiffusion model loadedTask
video_minimax_h3_t2v.jsonLocal GPUFL2VAText to video and audio
video_minimax_h3_i2v.jsonLocal GPUFL2VAFirst frame to video
video_minimax_h3_r2v.jsonLocal GPURef2VAReference media to video
api_minimax_h3_t2v.jsonHosted APIText to video and audio
api_minimax_h3_flf2v.jsonHosted APIFirst and last frame to video
api_minimax_h3_r2v.jsonHosted APIReference media to video

Source: Comfy-Org workflow templates. Checked 2026-08-13.

The repository contains 590 .json templates, including 56 with the video_ prefix. Verified through the GitHub Git Trees API at repos/Comfy-Org/workflow_templates/git/trees/main?recursive=1 with truncated: false.

Local files

What has to be on disk first

ComfyUI/
└── models/
    ├── diffusion_models/
    │   ├── minimax_h3_fl2va_pruned_int8_convrot.safetensors
    │   └── minimax_h3_ref2va_pruned_int8_convrot.safetensors
    ├── text_encoders/
    │   └── qwen3vl_32b_minimax_h3_nvfp4_awq.safetensors
    └── vae/
        ├── minimax_h3_video_vae_fp16.safetensors
        └── minimax_h3_audio_vae_fp32.safetensors

The Comfy-Org quantized four-file set has a static download and storage footprint of approximately 42.47GB in decimal units. Keeping the Ref2VA checkpoint as well adds approximately 20.97GB. These figures describe storage footprint, not minimum VRAM or system RAM requirements.

Set the CLIP Loader type to minimax. The workflow requires ComfyUI 0.30.0 or newer.

Sources: ComfyUI MiniMax H3 tutorial and Comfy-Org MiniMax-H3 repository. Checked 2026-08-13.

Task choice

Which template to start with

12GB benchmark

What a real run costs on a 12GB card

The R2V template ran at 1344×768 for 124 frames on an RTX 3060 12GB in 2,581.8 seconds, or approximately 43 minutes. Peak VRAM was 11,649 MiB, 94.8% of 12,288 MiB, and peak system memory was 43,587 MiB.

One machine, one configuration, with audio and every acceleration option disabled. The full test card lists every version, hash and setting behind these figures. The system memory page shows why that RAM number barely moves when the workload does.

FAQ

Frequently asked questions

How many official MiniMax H3 workflow templates are there?

Six. Three run the model on your own GPU: video_minimax_h3_t2v.json, video_minimax_h3_i2v.json and video_minimax_h3_r2v.json. Three call the hosted API through API nodes: api_minimax_h3_t2v.json, api_minimax_h3_flf2v.json and api_minimax_h3_r2v.json.

What is the difference between the video_ and api_ MiniMax H3 templates?

The video_ templates load MiniMax H3 weights on your own machine and need roughly 42GB of model files on disk. The api_ templates send the job to the hosted MiniMax API and need an API key instead of local weights.

Which MiniMax H3 template needs the Ref2VA weights?

Only video_minimax_h3_r2v.json loads the Ref2VA diffusion model. The T2V and I2V templates both load the FL2VA diffusion model, so switching between them does not require a second download.