MODEL PROFILE

MiniMax-H3-Qwen3-VL-NVFP4

6block · MiniMax-H3-Qwen3-VL-NVFP4

An **NVFP4 (4-bit) Qwen3-VL-32B text encoder** for MiniMax-H3, made with `convert-to-quant`. It is a drop-in replacement for the H3 conditioning text encoder (ComfyUI `CLIPLoader`, type `minimax`). The H3 video weights are unchanged — only the text encoder is quantized to 4-bit, to bring the full H3 stack onto consumer GPUs. This encoder deliberately keeps more of the network in bf16 than a minimum-size 4-bit encoder does. The `--qwen_vlm` filter protects — at bf16 — the token embeddings, the **first and last language layers**, and the **entire vision tower**, quantizing only the middle language-layer linears to NVFP4. The result is 16.64 GiB, about 2 GiB above the most aggressively quantized community NVFP4 encoders (≈14.6 GiB, e.g. the AWQ-quantized encoder in `Comfy-Org/MiniMax-H3`), in exchange for leaving the precision-sensitive layers (embeddings, boundary layers, vision) untouched. It is a fidelity-first tradeoff: spend ~2 GiB more VRAM to keep the layers that most affect conditioning at full precision. Everything still fits a 24 GB card with offload. Everything is held constant except encoder precision — the bf16 encoder vs this NVFP4 encoder, same prompts, same seeds, same DiT — over a 16-clip paired set.

Video generationlicense:other
Context windowNot disclosed
Input → OutputText → Video
Model weightsNot verified
Profile updated2026/11/2 19:16:13
OVERVIEW

Model overview

An **NVFP4 (4-bit) Qwen3-VL-32B text encoder** for MiniMax-H3, made with `convert-to-quant`. It is a drop-in replacement for the H3 conditioning text encoder (ComfyUI `CLIPLoader`, type `minimax`). The H3 video weights are unchanged — only the text encoder is quantized to 4-bit, to bring the full H3 stack onto consumer GPUs. This encoder deliberately keeps more of the network in bf16 than a minimum-size 4-bit encoder does. The `--qwen_vlm` filter protects — at bf16 — the token embeddings, the **first and last language layers**, and the **entire vision tower**, quantizing only the middle language-layer linears to NVFP4. The result is 16.64 GiB, about 2 GiB above the most aggressively quantized community NVFP4 encoders (≈14.6 GiB, e.g. the AWQ-quantized encoder in `Comfy-Org/MiniMax-H3`), in exchange for leaving the precision-sensitive layers (embeddings, boundary layers, vision) untouched. It is a fidelity-first tradeoff: spend ~2 GiB more VRAM to keep the layers that most affect conditioning at full precision. Everything still fits a 24 GB card with offload. Everything is held constant except encoder precision — the bf16 encoder vs this NVFP4 encoder, same prompts, same seeds, same DiT — over a 16-clip paired set.

Key features

特点摘要待依据来源补齐,不凭模型名称推断能力。

Limitations & considerations

Sources are insufficient to establish specific limitations. Verify task performance, latency, data policies, licensing and version lifecycle.

PRICING & COST

Source prices & cost analysis

Prices vary by channel, region and configuration. Channel quotes are listed independently and are not treated as a single official provider price.

Source / channelInputOutputBilling unitCollected at
No verified prices yet. Check the source channel.

Estimate monthly base token costs

—

Estimates exclude cache discounts, tiered pricing, multimodal surcharges, web search, taxes and additional reasoning output.

INDEPENDENT BENCHMARKS

Public benchmarks & run configuration

暂无已采集的可核验公开评分。模型未上榜不代表能力较低。

View full indexed rankings →

Frequently asked questions

Do open weights permit free commercial use?

Not necessarily. Check the version license, commercial conditions and usage policies. Self-hosting incurs compute and maintenance costs.

Are these real-time billing prices?

These are timestamped source snapshots, not live billing prices. Check the channel for current versions, regions, discounts and billing methods.

Sources & traceability

许可证:other。模型介绍与第三方评测均以原来源的具体版本和方法为准。