MiniMax M2.1 (230B-A10B) on Apple M3 Ultra (256 GB)
Can the Apple M3 Ultra (256 GB) run MiniMax M2.1 (230B-A10B)?
Yes, it runs well
Runs well. At Q4_K_M it needs about 158 GB of 192 GB usable, with an estimated speed of 43.3 tok/s.
- Best quant
Q4_K_M- Generation speed
- 43.3 tok/s
- Prompt processing
- 1,761 tok/s
- First token (1K prompt)
- 0.6 s
- Largest safe context
- 140K
Download MiniMax M2.1 (230B-A10B)
Recommended for the Apple M3 Ultra (256 GB): Q4_K_M. Every other quantization has its own download link in the table below.
Ollama
Ollama only offered this as a cloud model, and has since retired it. To run it locally, use the GGUF files below with llama.cpp or LM Studio.
Quantized files · GGUF
Works in LM Studio, llama.cpp, Jan and Ollama. No sign-in needed.
Download the Q4_K_M files (opens in a new tab)
huggingface.co/unsloth/MiniMax-M2.1-GGUF (opens in a new tab)
ollama run hf.co/unsloth/MiniMax-M2.1-GGUFOriginal weights · Hugging Face
Full-precision files from MiniMax, for fine-tuning, vLLM, Transformers.
Official repo · GitHub
Reference code, inference scripts and docs from MiniMax. The weights themselves download from Hugging Face.
github.com/MiniMax-AI/MiniMax-M2.1 (opens in a new tab)
git clone https://github.com/MiniMax-AI/MiniMax-M2.1How the S grade is scored
Every result gets up to 100 points from four parts. The points decide the letter grade.
| Model quality | 38.9 / 45 | |
|---|---|---|
| Memory fit | 25.0 / 25 | |
| Speed | 15.0 / 15 | |
| Memory use | 15.0 / 15 | |
| Total | 93.9 / 100 | 93 ptsExcellent (S) · 93 of 100 points: Model quality 38.9/45, Memory fit 25.0/25, Speed 15.0/15, Memory use 15.0/15 |
Every quantization on the Apple M3 Ultra (256 GB)
| Quant | Memory needed | Available | Speed | Fit | Grade · points | Download |
|---|---|---|---|---|---|---|
Q2_K | 110 GB | 192 GB | 71.1 tok/s | Runs well | 81 ptsGreat (A) · 81 of 100 points: Model quality 28.7/45, Memory fit 25.0/25, Speed 15.0/15, Memory use 13.2/15 | GGUF · folder (opens in a new tab) |
Q3_K_M | 130 GB | 192 GB | 56.0 tok/s | Runs well | 89 ptsExcellent (S) · 89 of 100 points: Model quality 34.4/45, Memory fit 25.0/25, Speed 15.0/15, Memory use 15.0/15 | GGUF · folder (opens in a new tab) |
Q4_K_M | 158 GB | 192 GB | 43.3 tok/s | Runs well | 93 ptsExcellent (S) · 93 of 100 points: Model quality 38.9/45, Memory fit 25.0/25, Speed 15.0/15, Memory use 15.0/15 | GGUF · folder (opens in a new tab) |
Q5_K_M | 180 GB | 192 GB | 35.8 tok/s | Tight fit | 92 ptsExcellent (S) · 92 of 100 points: Model quality 39.7/45, Memory fit 24.0/25, Speed 14.2/15, Memory use 15.0/15 | GGUF · folder (opens in a new tab) |
Q6_K | 206 GB | 192 GB | 25.5 tok/s | Runs with offload | 77 ptsGreat (A) · 77 of 100 points: Model quality 40.5/45, Memory fit 10.0/25, Speed 12.0/15, Memory use 15.0/15 | GGUF · folder (opens in a new tab) |
Q8_0 | 260 GB | 192 GB | — | Won't run | 12 ptsWon't run (F) · 12 of 100 points: Model quality 12.3/45, Memory fit 0.0/25, Speed 0.0/15, Memory use 0.0/15 | GGUF · folder (opens in a new tab) |
F16 | 475 GB | 192 GB | — | Won't run | 12 ptsWon't run (F) · 12 of 100 points: Model quality 12.3/45, Memory fit 0.0/25, Speed 0.0/15, Memory use 0.0/15 | GGUF · folder (opens in a new tab) Original weights (opens in a new tab) |
Memory figures assume 8K of context. Longer conversations or documents grow the KV cache.
Other hardware that runs it
- 90 ptsExcellent (S) · 90 of 100 points: Model quality 39.7/45, Memory fit 25.0/25, Speed 14.2/15, Memory use 11.8/15 Apple M3 Ultra (512 GB)
- 88 ptsExcellent (S) · 88 of 100 points: Model quality 34.4/45, Memory fit 24.0/25, Speed 15.0/15, Memory use 15.0/15 Apple M2 Ultra (192 GB)
- 80 ptsGreat (A) · 80 of 100 points: Model quality 28.7/45, Memory fit 24.0/25, Speed 12.4/15, Memory use 15.0/15 NVIDIA GB10 (128 GB)
- 68 ptsGood (B) · 68 of 100 points: Model quality 28.7/45, Memory fit 10.0/25, Speed 15.0/15, Memory use 15.0/15 Apple M4 Max (128 GB)
- 68 ptsGood (B) · 68 of 100 points: Model quality 28.7/45, Memory fit 10.0/25, Speed 15.0/15, Memory use 15.0/15 NVIDIA RTX PRO 6000 Blackwell
Estimates come from published hardware specs and our open formulas, not from running the model on your machine. Real speed varies with runtime, drivers and settings. Numbers marked “Measured” come from a linked benchmark.