Can Codestral 2 25.08 run on Mac Studio M3 Ultra 256GB?
YES — Runs Great
Codestral 2 25.08 needs ~44.4 GB VRAM. Mac Studio M3 Ultra 256GB has 184.3 GB. With Q4_K_M quantization, expect ~42 tok/s.
Operating mode
Choose the run profile you care about
Interactive favors responsiveness, while light API and scale-out lean harder on serving readiness. The fit stays the same, but the recommendation lens changes.
Current mode
Balanced
Balanced for general local use. Keeps the ranking neutral across personal and serving workflows.
Select quantization to explore
Fit status
Runs well
Decode
41.9 tok/s
TTFT
4617 ms
Safe context
256K
Memory
44.4 GB / 184.3 GB
Memory breakdown
See how fast it feels
What limits this setup
This setup is broadly balanced for this model.
Shared-memory contention still exists
The OS, browser, and inference runtime all compete for the same physical memory pool, so real-world headroom is less forgiving than raw capacity suggests.
Best improvement path
Performance by workload
| Workload | Grade | Fit | Decode | TTFT | Context |
|---|---|---|---|---|---|
| Chat | A | Runs well | 41.9 tok/s | 2518 ms | 256K |
| Coding | A | Runs well | 41.9 tok/s | 4617 ms | 256K |
| Agentic Coding | A | Runs well | 41.9 tok/s | 6715 ms | 256K |
| Reasoning | A | Runs well | 41.9 tok/s | 5456 ms | 256K |
| RAG | A | Runs well | 41.9 tok/s | 8394 ms | 256K |
Quantization options
How Codestral 2 25.08 (22B params) fits at each quantization level on Mac Studio M3 Ultra 256GB (184.3 GB usable).
| Quant | Bits | VRAM | Quality | Fit |
|---|---|---|---|---|
Q2_K | 2 | 8.6 GB | Low | A71 |
Q3_K_S | 3 | 10.8 GB | Low | A71 |
NVFP4 | 4 | 12.3 GB | Medium | A71 |
Q4_K_M | 4 | 13.4 GB | Medium | A71 |
Q5_K_M | 5 | 15.8 GB | High | A72 |
Q6_K | 6 | 18.0 GB | High | A72 |
Q8_0 | 8 | 23.5 GB | Very High | A72 |
F16Best for your GPU | 16 | 45.1 GB | Maximum | A75 |
Get started
Copy-paste commands to run Codestral 2 25.08 on your machine.
Run
lms load codestral-2508 && lms server startYour hardware
More models your Mac Studio M3 Ultra 256GB can run
| Model | Params | Grade | Decode | Capabilities |
|---|---|---|---|---|
| 123B | S | 8.1 tok/s | ||
| 30.5B | S | 84.2 tok/s | ||
| 27B | S | 36.5 tok/s | ||
| 27B | S | 27.8 tok/s | ||
| 122B | S | 34.7 tok/s |
Frequently asked questions
Can Mac Studio M3 Ultra 256GB run Codestral 2 25.08?
Yes, Mac Studio M3 Ultra 256GB can run Codestral 2 25.08 with a A grade (Runs well). Expected decode speed: 41.9 tok/s.
How much VRAM does Codestral 2 25.08 need?
Codestral 2 25.08 (22B parameters) requires approximately 44.4 GB of memory with Q4_K_M quantization.
What is the best quantization for Codestral 2 25.08?
The recommended quantization for Codestral 2 25.08 is Q4_K_M, which balances quality and memory efficiency.
What speed will Codestral 2 25.08 run at on Mac Studio M3 Ultra 256GB?
On Mac Studio M3 Ultra 256GB, Codestral 2 25.08 achieves approximately 41.9 tokens per second decode speed with a time-to-first-token of 4617ms using Q4_K_M quantization.
Can Mac Studio M3 Ultra 256GB run Codestral 2 25.08 for coding?
For coding workloads, Codestral 2 25.08 on Mac Studio M3 Ultra 256GB receives a A grade with 41.9 tok/s and 256K context.
What context window can Codestral 2 25.08 use on Mac Studio M3 Ultra 256GB?
On Mac Studio M3 Ultra 256GB, Codestral 2 25.08 can safely use up to 256K tokens of context. The model's official context limit is 256K, but available memory constrains the safe maximum.
Is unified memory on Mac Studio M3 Ultra 256GB as fast as VRAM for Codestral 2 25.08?
Not always. Mac Studio M3 Ultra 256GB can often fit larger models thanks to unified memory, but a discrete GPU with dedicated high-bandwidth VRAM may still decode faster once the model fits. For this combination, the important distinction is capacity versus sustained throughput.
Embed this result▼
Paste this snippet into any page to show a live fit card.
<iframe src="https://willitrunai.com/embed/codestral-2-25.08-on-m3-ultra-256gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>
Preview: