Skip to content
Bitpute

How much VRAM does MiniMax-Text-01 456B (46B active) Chat need?

By Bitpute · Published 12 July 2026 · Updated 24 July 2026 · How we estimate · Sources · Editorial policy · Version history · Report an error · Figures re-checked against the calculation engine on every build

MiniMax-Text-01 456B (46B active) Chat needs about 271.1 GB of VRAM at Q4_K_M, or 474.5 GB at Q8_0 and 892.6 GB at FP16. No single GPU in our set holds it even at Q4_K_M; it needs multi-GPU or offload. Weights plus runtime overhead. Budget separately for KV cache, which at 1M is a material share.

Weights-plus-runtime footprint across the six most common quantizations. KV cache is context-dependent and comes on top. At 1M it is gigabytes on its own, before the weights; size it precisely in the GPU Memory Calculator.

This is a mixture-of-experts model: all 456B parameters must sit in memory, but only about 46B are active per token — so it loads like a 456B model and runs closer to a 46B one.

Parameters456B
Active / token46B
Context1000K
VendorMiniMax
LicenseOpen weights (see card)
Released2025

Can your GPU run MiniMax-Text-01 456B (46B active) Chat?

Pick your card — the answer below is computed by the same engine that produces every figure on this page.

No — not enough VRAM
Estimated VRAM271.1 GB
GPU VRAM141 GB
Short by137.1 GB

H200 141GB cannot hold MiniMax-Text-01 456B (46B active) Chat at Q4_K_M: it needs 271.1 GB against 133.9 GB usable; a heavier quantization, a larger card, or splitting across GPUs are the ways forward; as a mixture-of-experts model all 456B parameters must be resident even though only 46B are active per token.

Weights plus runtime overhead. KV cache is not included — it depends on context length and this model’s published architecture.

Why
Weights (Q4_K_M)257.5 GB
Runtime overhead13.6 GB
Estimated total271.1 GB
Usable VRAM (95% of 141 GB)133.9 GB

Across every GPU we track

Estimates, not guarantees: real usage moves with runtime, driver, batch size and context. Size a specific context window in the GPU Memory Calculator.

How was this number calculated? Every figure here comes from Bitpute’s documented calculation methodology — parameters, precision, quantization, runtime overhead and usable VRAM, each formula written out in full.

Memory by quantization

QuantWeights+ runtime overhead
FP16849.4 GB892.6 GB
Q8_0451.2 GB474.5 GB
Q6_K348.2 GB366.4 GB
Q5_K_M302.1 GB317.9 GB
Q4_K_M257.5 GB271.1 GB
Q4_0238.9 GB251.6 GB

Overhead = 0.75 GB + 5% of weights (CUDA context, buffers). Add KV cache on top. Weights dominate at this size, but a 1M window still costs gigabytes.

Which quantization should you actually run?

MiniMax-Text-01 456B (46B active) Chat is a multi-GPU or datacenter model: even Q4_K_M needs about 271.1 GB, beyond any single card. Plan for several 80 GB GPUs or a hosted endpoint; FP16 (892.6 GB) is server-only. As a mixture-of-experts model it must hold all 456B in VRAM but activates only about 46B per token, so it runs much faster than its footprint suggests — memory is the limit here, not speed.

Single-GPU fit at Q4_K_M (271.1 GB + KV)

RTX 3060 12GBRTX 4060 Ti 16GBRTX 4070 Ti SUPERRTX 3090RTX 4090RTX 5090A100 40GBRTX A6000L40SA100 80GBH100 80GBH200 141GB

Size it exactly →Rent a GPU for it →

Common questions

How much VRAM does MiniMax-Text-01 456B (46B active) Chat need?

MiniMax-Text-01 456B (46B active) Chat needs about 271.1 GB of VRAM at Q4_K_M, 474.5 GB at Q8_0, or 892.6 GB at FP16. That is weights plus about 0.75 GB of runtime overhead and 5% of weight size; KV cache is additional and depends on context length.

What GPU can run MiniMax-Text-01 456B (46B active) Chat?

No single GPU in our set fits it at Q4_K_M; it needs multiple GPUs or CPU offload. At FP16 no single GPU in our set is sufficient.

Can MiniMax-Text-01 456B (46B active) Chat run on 24 GB?

Not at Q4_K_M: it needs about 271.1 GB, more than the ~22.8 GB usable on a 24 GB card. Use a larger card, multiple GPUs, or offload.