Datasheet for local AI49 models98 GPUsData read 2026-09-25
No adsNo tracking
Check my GPU →

MiniMax H3 Pruned on 10 GB of VRAM

Video model · pruned 33BAny 10 GB GPUData 2026-09-25
Offload
Not entirely in VRAM, but it can still run.

The smallest sensible file, Q4_K_M (11.6 GB), needs about 17.4 GB — 7.4 GB more than 10 GB GPU has. ComfyUI can still run it by streaming part of the model from system RAM. How much slower that is depends on your ComfyUI version, the file format and the PCIe link — see the note below.

Best fileQ4_K_M
File size11.6 GB
VRAM needed~17.4 GB
System RAM64 GB+
Memory map · 10 GB GPU17.4 GB needed · 7.4 GB over 10 GB
09 GB17 GB
Weights Q4_K_M · 11.6 GBWorking memory · 5.0 GBReserve · 0.8 GBSpills to system RAM · 7.4 GB
calculated from real file sizes plus working memory. Not yet measured on this setup. How this works.

Worth trying on NVIDIA GPUs: with an up-to-date ComfyUI, Dynamic VRAM (on by default for NVIDIA since March 2026) streams whatever does not fit from system RAM, and ComfyUI's own start-up message recommends native FP8/INT8 files over GGUF, saying they “will be faster even if they are larger than your memory”. So before settling for a heavily compressed GGUF, try the native FP8 file (21.0 GB). The file recommended above is the best one that fits entirely — the safe choice on older ComfyUI versions, AMD and Intel. Comfy blog: Dynamic VRAM →

01What to download

PartFileFolderSize
ModelMiniMax-H3-FL2VA-Pruned-Q4_K_M.gguf
Q4_K_M · Abiray/MiniMax-H3-Pruned-GGUF
models/unet11.6 GBDownload →
Text encoderqwen3vl_32b_minimax_h3_int8_convrot.safetensors
Qwen3-VL 32B INT8 (convrot) · Comfy-Org/MiniMax-H3
models/text_encoders27.1 GBDownload →
VAEminimax_h3_video_vae_fp16.safetensors
MiniMax H3 video VAE FP16 · Comfy-Org/MiniMax-H3
models/vae5.2 GBDownload →
Also neededminimax_h3_audio_vae_fp32.safetensors
MiniMax H3 audio VAE FP32 · Comfy-Org/MiniMax-H3
models/vae0.6 GBDownload →
Total download · keep about the same free on disk44.5 GB

Alternatives: Qwen3-VL 32B NVFP4 (AWQ) (15.7 GB); Qwen3-VL 32B BF16 (51.5 GB). The 16-bit text encoder is a little more faithful; the smaller one is chosen here because it loads faster and needs less RAM. FP4 files are listed only as alternatives unless the GPU is an RTX 50 (Blackwell). Sizes read from Hugging Face (2026-09-25). “Download” links start the file directly; the file name links are the same files the official ComfyUI workflows use.

System RAM: 64 GB or more. ComfyUI keeps the model file, the text encoder and the VAE in system RAM and moves them to the GPU as needed. With this set of files that is about 44.5 GB, plus roughly 6 GB for Windows, ComfyUI and a browser: 50.5 GB in total. With less RAM it still runs, but Windows starts swapping to disk and loading gets very slow. calculated

02Every file, on 10 GB

FileSizeNeededOn this cardQualityDownload
16-bit
SAFETENSORS · Comfy-Org
40.2 GB46.0 GB36.0 GB too bigthe original weightsHugging Face →
Q8_0
GGUF · Abiray
21.6 GB27.4 GB17.4 GB too bigpractically identical to the originalHugging Face →
FP8
SAFETENSORS · Comfy-Org
21.0 GB26.8 GB16.8 GB too bigpractically identical to the originalHugging Face →
INT8
SAFETENSORS · Comfy-Org
21.0 GB26.8 GB16.8 GB too bigpractically identical to the originalHugging Face →
Q6_K
GGUF · Abiray
16.7 GB22.5 GB12.5 GB too bigvery close to the originalHugging Face →
Q5_K_M
GGUF · Abiray
14.1 GB19.9 GB9.9 GB too bigclose; small differences in fine detailHugging Face →
Q4_K_M ←
GGUF · Abiray
11.6 GB17.4 GB7.4 GB too biggood; some loss in fine detail and textHugging Face →
Q3_K_M
GGUF · Abiray
8.9 GB14.7 GB4.7 GB too bignoticeable loss of detailHugging Face →

Sizes from the Hugging Face file listing, read 2026-09-25. “Needed” = file + 5 GB working memory for this model + 0.8 GB kept free for the system.

03The text encoder

Qwen3-VL 32B: 51.5 GB as 16-bit, 27.1 GB as INT8, 15.7 GB as NVFP4. ComfyUI encodes the prompt first and can push the encoder out of VRAM before sampling, so it does not have to fit together with the model. On 10 GB the encoder itself is too big for VRAM, so let it run from system RAM: slower prompt encoding, same images.