MiniMax-M2.5: hardware requirements
MiniMax-M2.5 needs about 143 GB of memory at Q4 quantization — a 138 GB download plus room for context and overhead. That is beyond consumer hardware; use it through an API instead.
This is a mixture-of-experts model. Only a fraction of its 229B parameters are used for each token, so it runs faster than its size suggests — but all of it still has to fit in memory. The speed is that of a small model; the memory requirement is that of a large one. More on this →
Will it run on your machine?
Download sizes by quantization
Lower quantization means a smaller file and less memory, at some cost to quality. Q4_K_M is the usual starting point. What is this?
| Quant | Download | RAM @ 4K | RAM @ 32K | Source |
|---|---|---|---|---|
| Q4_K_Mrecommended | 138 GB | 143 GB | 150 GB | measured |
| Q5_K_M | 162 GB | 167 GB | 174 GB | measured |
| Q6_K | 188 GB | 192 GB | 199 GB | measured |
| Q8_0 | 243 GB | 247 GB | 255 GB | measured |
| BF16 | 457 GB | 462 GB | 469 GB | measured |
“Measured” sizes are read from published GGUF files (unsloth/MiniMax-M2.5-GGUF). “Estimated” sizes are derived from the parameter count and are typically within a few percent. The RAM columns add the context cache and runtime overhead to the download size.