MiniMax-H3-encoder

About

What MiniMax-H3-encoder is

MiniMax-H3 Text Encoder — GGUF GGUF quantizations of the Qwen3-VL-32B vision-language text encoder used by MiniMax-H3 in ComfyUI. The H3 DiT quants are here: joeygambino/MiniMax-H3-GGUF. You need one file from each repo to run H3 — the DiT alone will not generate anything. Troubleshooting: statedict / vision mismatch with the -mmproj file Load these encoders with H3 Clip Loader (Any) from ComfyUI-H3-Multishot, not the stock CLIPLoaderGGUF node. The H3 text encoder is a truncated Qwen3-VL-32B - 50 layers, no final norm, no lmhead - and its vision tower ships separately as the -mmproj-F16.gguf sidecar. Stock ComfyUI-GGUF only merges an mmproj when the encoder's architecture is qwen2vl; Qwen3-VL reports qwen3vl, so the sidecar is never merged at all, and the resulting missing vision tensors surface as a statedict mismatch. Its mmproj key map is also qwen2vl-era: wrong merger keys, and no rules for H3's deepstack mergers or split QKV, so even forcing the merge would not line up. The pack's loader does all three things stock cannot - truncates the text tower to H3's shape, merges the sidecar explicitly, and renames the vision tensors to H3's layout (including remapping deepstack mergers, which llama.cpp indexes by vision layer 8/16/24 and H3 indexes by position 0/1/2). Keep the -mmproj-F16.gguf in the same folder as the encoder and do not rename either file: they are paired by filename stem. Why does a .safetensors encoder work without any of this? Because a full safetensors encoder (fp8, int8, NVFP4-AWQ, ...) is a complete, pre-shaped model with its vision tower already inside. It needs no sidecar and no remapping. That is a property of the container, not of the quantization - NVFP4 is not doing anything special here. Files The mmproj is not optional if you use reference images H3's reference-to-video (ref2va) and image-to-video paths feed images into the text encoder. Without mmproj, the encoder is text-only: reference images are ignored and reference/I2V workflows will not behave correctly. CLIPLoaderGGUF (from ComfyUI-GGUF) auto-pairs the mmproj sidecar by filename, so keep the names exactly as downloaded and put the mmproj in the same folder as the encoder. Inst

Summarised from the published model card. Read the full card on the HuggingFace links below.

Specifications

What it is

How it works

How video models work

Variants

Sizes & precisions

Open weights ship in several sizes and precisions. One page, all the variants — pick the one that fits your GPU. VRAM figures are estimates from model size.

Using it via the API

Call it like any OpenAI endpoint

Once AxForge deploys minimax-h3-encoder for you, it answers on the OpenAI-compatible API — the same base URL and keys as every other model. (minimax-h3-encoder below is illustrative; you get the exact model name on deployment.)

$ curl -sS https://api.axforge.ai/v1/videos/generations \
  -H "Authorization: Bearer $AXFORGE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model":"minimax-h3-encoder","prompt":"a drone shot over a forest"}'

Details

Languages, data & research

Licence

Commercial licence needed

Sources

Weights & code

Explore

More video models