MiniMax M3 VRAM requirements
MiniMax M3 needs about 266 GB of VRAM at Q4_K_M with 8K context, so it needs a 640 GB setup such as 8× H100 SXM; a 24 GB card is too small. MiniMax M3 has 427.0B parameters, of which about 23B are used per token; all 128 experts still have to be in memory. With the same 8K context and one request it needs 439 GB at FP8 and 876 GB at FP16/BF16. The published weights take 796 GB (BF16). It does not fit on a 24 GB card at Q4_K_M; the smallest setup here that holds it with an 8K context is the M3 Ultra Mac Studio (512 GB, 384 GB usable).
266 GB at Q4_K_M, 8K context, one request
- FP8
- 439 GB
- FP16 / BF16
- 876 GB
- Published weights
- 796 GB
- Smallest setup, Q4_K_M
- M3 Ultra Mac Studio (512 GB, 384 GB usable)
Worked example: MiniMax M3 with 32K tokens
Inputs: MiniMax M3 · Q4_K_M weights · 32,768 tokens of context · one request · FP16 KV cache
- Weights (427.0B at Q4_K_M)
- 241 GB
- KV cache (120 KB per token)
- 3.75 GB
- Buffers and runtime (0.5 GB + 10%)
- 24.9 GB
- Total
- 269 GB
The smallest setup here that holds it is the M3 Ultra Mac Studio (512 GB, 384 GB usable), with about 115 GB to spare. Change the inputs in the calculator
What makes MiniMax M3's memory use different
As a mixture-of-experts model it reads about 13.0 GB of its 241 GB Q4_K_M weights per generated token (5%), so it writes like a much smaller model while needing memory for all of them.
How much VRAM does MiniMax M3 need?
MiniMax M3 needs 266 GB at Q4_K_M, 466 GB at Q8_0 and 876 GB at FP16 with 8,192 tokens of context and one request. Each total below is the weights plus the FP16 KV cache and the runtime overhead (0.5 GB plus 10%), and each row opens the calculator with that setting. What the GGUF names mean.
| Precision | Weights | Total | Smallest setup |
|---|---|---|---|
| As published (BF16) | 796 GB | 877 GB | 8× H200 (1,128 GB) |
| FP16 / BF16 | 795 GB | 876 GB | 8× H200 (1,128 GB) |
| FP8 / INT8 | 398 GB | 439 GB | 8× H100 SXM (640 GB) |
| INT4 (AWQ / GPTQ) | 211 GB | 234 GB | M3 Ultra Mac Studio (512 GB, 384 GB usable) |
| GGUF Q8_0 | 423 GB | 466 GB | 8× H100 SXM (640 GB) |
| GGUF Q6_K | 326 GB | 360 GB | M3 Ultra Mac Studio (512 GB, 384 GB usable) |
| GGUF Q5_K_M | 282 GB | 312 GB | M3 Ultra Mac Studio (512 GB, 384 GB usable) |
| GGUF Q4_K_M | 241 GB | 266 GB | M3 Ultra Mac Studio (512 GB, 384 GB usable) |
| GGUF IQ4_XS | 216 GB | 239 GB | M3 Ultra Mac Studio (512 GB, 384 GB usable) |
| GGUF Q3_K_M | 194 GB | 215 GB | M3 Ultra Mac Studio (512 GB, 384 GB usable) |
| GGUF IQ3_XXS | 164 GB | 182 GB | M3 Ultra Mac Studio (512 GB, 384 GB usable) |
| GGUF Q2_K | 167 GB | 185 GB | M3 Ultra Mac Studio (512 GB, 384 GB usable) |
Fine-tuning MiniMax M3? MiniMax M3 VRAM for LoRA, QLoRA and full training.
MiniMax M3 GGUF files on Hugging Face
The 8 GGUF files llama.cpp picks for MiniMax M3 with -hf <repo>:<QUANT>, with the bytes the Hugging Face file list reported on 2026-09-29. Each total is that file plus the FP16 KV cache and 0.5 GB + 10%, one request. "vs estimate" compares the file with the bits-per-weight size the table above uses.
| Quant | File | Size | vs estimate | 8K | 32K | 128K |
|---|---|---|---|---|---|---|
| Q2_K | bartowski/ | 141 GB151,886,604,736 bytes | −15% | 157 GB | 160 GB | 173 GB |
| Q3_K_M | unsloth/ | 181 GB194,578,416,896 bytes | −7% | 201 GB | 204 GB | 216 GB |
| IQ4_XS | unsloth/ | 193 GB207,559,687,520 bytes | −11% | 214 GB | 217 GB | 230 GB |
| Q4_K_M | unsloth/ | 246 GB264,031,796,736 bytes | +2% | 272 GB | 275 GB | 287 GB |
| Q5_K_M | unsloth/ | 296 GB317,838,325,344 bytes | +5% | 327 GB | 330 GB | 343 GB |
| Q6_K | unsloth/ | 330 GB354,416,850,624 bytes | +1% | 365 GB | 368 GB | 380 GB |
| Q8_0 | unsloth/ | 422 GB452,714,559,392 bytes | ±0% | 465 GB | 468 GB | 481 GB |
| BF16 | unsloth/ | 793 GB852,000,340,544 bytes | ±0% | 874 GB | 877 GB | 890 GB |
GB here is GiB (1024³ bytes), as everywhere on this site; Hugging Face shows the Q4_K_M file as 264.0 GB, in 10⁹ bytes.
Which MiniMax M3 GGUF fits a 16, 24, 32, 48 or 80 GB GPU or a Mac
From the file sizes above: the largest file that fits each machine with an 8K context and 0.5 GB left free, the longest context it then has room for, and the longest context for Q4_K_M (246 GB). One request, FP16 KV cache.
| Hardware | Largest GGUF, 8K | Its longest context | Q4_K_M, longest context |
|---|---|---|---|
| RTX 5060 Ti 16GB | None fits | — | No |
| RTX 4090 (24 GB) | None fits | — | No |
| RTX 5090 (32 GB) | None fits | — | No |
| L40S (48 GB) | None fits | — | No |
| H100 SXM (80 GB) | None fits | — | No |
| M4 Pro Mac (64 GB, 48 GB usable) | None fits | — | No |
| M4 Max Mac (128 GB, 96 GB usable) | None fits | — | No |
Run MiniMax M3 with llama.cpp
llama-server -hf unsloth/MiniMax-M3-GGUF:Q4_K_M -c 892928 UD-Q4_K_M/
MiniMax M3 at 8K, 32K, 128K and 1M (full) tokens of context
All 60 layers use full attention. Each extra token of context adds 120 KB of FP16 cache per request. The last column is the smallest setup here, one card or a group, that holds it at Q4_K_M. How the KV cache works.
| Context | KV cache, FP16 | Total at Q4_K_M | Total at Q8_0 | Smallest setup, Q4_K_M |
|---|---|---|---|---|
| 8K tokens | 960 MB | 266 GB | 466 GB | M3 Ultra Mac Studio (512 GB, 384 GB usable) |
| 32K tokens | 3.75 GB | 269 GB | 469 GB | M3 Ultra Mac Studio (512 GB, 384 GB usable) |
| 128K tokens | 15.0 GB | 282 GB | 482 GB | M3 Ultra Mac Studio (512 GB, 384 GB usable) |
| 1M tokens | 120 GB | 397 GB | 597 GB | 8× H100 SXM (640 GB) |
How fast MiniMax M3 writes
Tokens per second for one request with 8,192 tokens of context, estimated from memory bandwidth and the parameters read per token. A dash means it does not fit on one card. Try other settings in the speed calculator.
| Hardware | Bandwidth | Q4_K_M | FP8 |
|---|---|---|---|
| RTX 3060 12GB | 360 GB/s | — | — |
| RTX 4090 | 1,008 GB/s | — | — |
| RTX 5090 | 1,792 GB/s | — | — |
| M4 Max Mac (128 GB) | 546 GB/s | — | — |
| M3 Ultra Mac Studio (512 GB) | 819 GB/s | 16–27 | — |
| H100 SXM | 3,350 GB/s | — | — |
| H200 | 4,800 GB/s | — | — |
Longest context on a multi-GPU group
No single card in this table holds it at Q4_K_M, Q8_0 or FP8, so these rows use GPU groups: how many tokens of context MiniMax M3 fits on each, in one tensor-parallel group with one request, an FP16 KV cache and 0.5 GB left free. "Full" means the model's whole context window fits.
| Group | Memory | Q4_K_M | Q8_0 | FP8 |
|---|---|---|---|---|
| 2× RTX 3060 12GB | 24 GB | No | No | No |
| 2× RTX 3090 | 48 GB | No | No | No |
| 2× RTX 4090 | 48 GB | No | No | No |
| 2× RTX 5090 | 64 GB | No | No | No |
| 4× RTX 3090 | 96 GB | No | No | No |
| 8× H100 SXM | 640 GB | 1M (full) | 1M (full) | 1M (full) |
| 8× H200 | 1,128 GB | 1M (full) | 1M (full) | 1M (full) |
Model details
- Parameters
- 427.0B (427,040,140,160)
- Experts
- 128 routed experts, all loaded
- Active per token
- 23B
- Layers
- All 60 layers use full attention
- Attention cache
- 4 KV heads × 128
- Context length
- 1,048,576 tokens
- Published weights
- 796 GB (BF16)
- On Hugging Face
- MiniMaxAI/MiniMax-M3
- Reported benchmarks
- None published in the model card for GPQA, MMLU-Pro or LiveCodeBench.
Why this estimate looks this way
At Q4_K_M and an 8K-token context, MiniMax M3 uses 241 GB for weights, 960 MB for its FP16 KV cache and 24.7 GB for estimated runtime overhead, totaling 266 GB. The overhead is a 0.5 GB base plus 10% of weights and cache.
This is a mixture-of-experts model: all 128 experts contribute to the 427.0B parameters held in memory, even though only about 23B parameters run per token. Using only active parameters would understate VRAM.
The architecture and published checkpoint size come from the model's config.json and weight files. These are estimates rather than measured peak memory; inference engines can reserve extra buffers or preallocate the full configured cache.
MiniMax M3 next to similar-sized models
The three models here closest to it in parameter count, at Q4_K_M with 8,192 tokens of context.
| Model | Parameters | Total | KV per token | Smallest setup |
|---|---|---|---|---|
| MiniMax M3 | 427.0B, 23B active | 266 GB | 120 KB | M3 Ultra Mac Studio (512 GB, 384 GB usable) |
| GLM-5.3 Flash | 321.3B, 18B active | 200 GB | 19 KB | M3 Ultra Mac Studio (512 GB, 384 GB usable) |
| IQuest-Q1 320B-A15B | 320.3B, 15B active | 201 GB | 100 KB | M3 Ultra Mac Studio (512 GB, 384 GB usable) |
| Ling 3.1 Flash 560B-A25B | 572.1B, 25B active | 355 GB | 10 KB | M3 Ultra Mac Studio (512 GB, 384 GB usable) |
MiniMax M3 VRAM questions
How much VRAM do I need to run MiniMax M3 locally?
About 266 GB at Q4_K_M with an 8K context and one request, by the bits-per-weight estimate, and 876 GB at BF16. The Q4_K_M GGUF UD-Q4_K_M/
Can I run MiniMax M3 on a 24 GB GPU?
No. The RTX 4090 (24 GB) alone cannot hold it: the smallest listed GGUF, Q2_K at 141 GB, needs 157 GB with an 8K context.
Which quantization of MiniMax M3 fits in 16 GB of VRAM?
The RTX 5060 Ti 16GB alone cannot hold it: the smallest listed GGUF, Q2_K at 141 GB, needs 157 GB with an 8K context.
Can I run MiniMax M3 on a Mac?
The M4 Pro Mac (64 GB, 48 GB usable) alone cannot hold it: the smallest listed GGUF, Q2_K at 141 GB, needs 157 GB with an 8K context. The M4 Max Mac (128 GB, 96 GB usable) alone cannot hold it: the smallest listed GGUF, Q2_K at 141 GB, needs 157 GB with an 8K context. By default macOS lets the GPU use about 75% of unified memory.
How much more VRAM does MiniMax M3 need for 32K or 128K tokens of context?
Its FP16 KV cache is 960 MB at 8K, 3.75 GB at 32K, 15.0 GB at 128K for one request, so 128K adds 14.1 GB over 8K, plus 10% overhead. A q8_0 cache
Why does MiniMax M3 use more VRAM than its GGUF file size?
The file holds only the weights. At Q4_K_M with an 8K context: 246 GB of weights (the file's 264,031,796,736 bytes) + 960 MB of FP16 KV cache + 25.2 GB of compute buffers and runtime (0.5 GB + 10%) = 272 GB.
Does MiniMax M3 need less VRAM because only 23B parameters are active?
No. All 128 experts stay loaded, so the Q4_K_M file takes 246 GB. The active parameters decide speed: each generated token reads about 13.0 GB of them.
Badge for your model card
Paste it into a Hugging Face or GitHub README; it shows the Q4_K_M total above and links to this page. Q8_0 and FP16 badges.
Numbers read from the model files on Hugging Face on . Compare it with other models in the reproducible model and GPU report.