MiniMaxAI.MiniMax M2.5 needs about 140.9 GB of memory at Q4_K_M (a 138.3 GB file) with an 8K context window, which is more than a 48 GB GPU holds. This repository has 9 quants, from 51.6 GB (IQ1_M) to 243.1 GB (Q8_0). Longer context needs more: at 32K tokens the KV cache alone adds about 8.3 GB.
MiniMaxAI.MiniMax M2.5 is a 229B-parameter Minimax model in GGUF format, quantized by DevQuasar. Its trained context length is 192K tokens. The repository has 9 quant files, from 51.6 GB (IQ1_M) to 243.1 GB (Q8_0).
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| IQ1_M | 51.6 GB (4 parts) | 54.2 GB | Too big | Get file → | |
| IQ2_XXS | 60.1 GB (4 parts) | 62.7 GB | Too big | Get file → | |
| Q2_K | 83.3 GB (6 parts) | 85.9 GB | Too big | Get file → | |
| Q3_K_M | 109.3 GB (7 parts) | 111.9 GB | Too big | Get file → | |
| MXFP4_MOE | 123.8 GB (8 parts) | 126.4 GB | Too big | Get file → | |
| Q4_K_M | 138.3 GB (9 parts) | 140.9 GB | Too big | Get file → | |
| Q5_K_M | 162.3 GB (11 parts) | 164.9 GB | Too big | Get file → | |
| Q6_K | 187.8 GB (13 parts) | 190.3 GB | Too big | Get file → | |
| Q8_0 | 243.1 GB (16 parts) | 245.7 GB | Too big | Get file → |
What GPU do you need for MiniMaxAI.MiniMax M2.5?
These figures add the file size, an fp16 KV cache at an 8K context window (worked out from this model’s own header) and about 0.5 GB for the runtime. They are estimates, so leave a little headroom, and expect to use less context or a smaller quant if you are right at the limit.
- 4 GB VRAM: no quant fits at an 8K context.
- 6 GB VRAM: no quant fits at an 8K context.
- 8 GB VRAM: no quant fits at an 8K context.
- 12 GB VRAM: no quant fits at an 8K context.
- 16 GB VRAM: no quant fits at an 8K context.
- 24 GB VRAM: no quant fits at an 8K context.
- 32 GB VRAM: no quant fits at an 8K context.
- 48 GB VRAM: no quant fits at an 8K context.
Which MiniMaxAI.MiniMax M2.5 quant should you choose?
Q4_K_M is the usual starting point for MiniMaxAI.MiniMax M2.5: it balances file size and quality well. Here it is a 138.3 GB file.
The Q8_0 file is 243.1 GB, about 1.8 times the size of Q4_K_M. It keeps the weights closer to the original, which only matters if you have the memory to spare.
If memory is tight, the smallest file is IQ1_M at 51.6 GB, with the quality trade-offs that come with fewer bits. Use it only when memory is very tight. Expect a clear drop in quality, which is usually worse on small models and easier to live with on large ones.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about MiniMaxAI.MiniMax M2.5
How much VRAM does MiniMaxAI.MiniMax M2.5 need?
About 140.9 GB at Q4_K_M with an 8K context window. That is the 138.3 GB file, plus the KV cache and roughly 0.5 GB of runtime overhead. Smaller quants need less and longer context needs more.
Can I run MiniMaxAI.MiniMax M2.5 on an 8 GB GPU?
Not at an 8K context. The smallest file needs about 54.2 GB, so you would need a larger GPU or CPU offloading.
What is the file size of MiniMaxAI.MiniMax M2.5 GGUF?
It depends on the quant: IQ1_M is 51.6 GB, IQ2_XXS is 60.1 GB, Q2_K is 83.3 GB, Q3_K_M is 109.3 GB, MXFP4_MOE is 123.8 GB, Q4_K_M is 138.3 GB and 3 more.
What context length does MiniMaxAI.MiniMax M2.5 support?
The GGUF header lists a trained context length of 196,608 tokens (192K). The KV cache grows with the context you use: about 2.1 GB at 8K and 8.3 GB at 32K.
Where can I download MiniMaxAI.MiniMax M2.5 GGUF?
The files are on Hugging Face in the DevQuasar/MiniMaxAI.MiniMax-M2.5-GGUF repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.
What license does MiniMaxAI.MiniMax M2.5 use?
Hugging Face lists the license as other. Licenses can differ between the quantized files and the original model, so check the repository and the base model before commercial use.