Can Codestral 2 25.08 run on MacBook Pro M3 Max 64GB?
YES — Runs Great
Codestral 2 25.08 needs ~23.7 GB VRAM. MacBook Pro M3 Max 64GB has 46.1 GB. With Q4_K_M quantization, expect ~18 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
18.1 tok/s
TTFT
10713 ms
Safe context
163K
Memory
23.7 GB / 46.1 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 | 18.1 tok/s | 5843 ms | 163K |
| Coding | A | Runs well | 18.1 tok/s | 10713 ms | 163K |
| Agentic Coding | A | Runs well | 18.1 tok/s | 15583 ms | 163K |
| Reasoning | A | Runs well | 18.1 tok/s | 12661 ms | 163K |
| RAG | A | Runs well | 18.1 tok/s | 19478 ms | 163K |
Quantization options
How Codestral 2 25.08 (22B params) fits at each quantization level on MacBook Pro M3 Max 64GB (46.1 GB usable).
| Quant | Bits | VRAM | Quality | Fit |
|---|---|---|---|---|
Q2_K | 2 | 8.6 GB | Low | A77 |
Q3_K_S | 3 | 10.8 GB | Low | A78 |
NVFP4 | 4 | 12.3 GB | Medium | A78 |
Q4_K_M | 4 | 13.4 GB | Medium | A78 |
Q5_K_M | 5 | 15.8 GB | High | A79 |
Q6_K | 6 | 18.0 GB | High | A80 |
Q8_0Best for your GPU | 8 | 23.5 GB | Very High | A82 |
F16 | 16 | 45.1 GB | Maximum | F0 |
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 MacBook Pro M3 Max 64GB can run
| Model | Params | Grade | Decode | Capabilities |
|---|---|---|---|---|
| 30.5B | S | 36.3 tok/s | ||
| 27B | S | 15.7 tok/s | ||
| 27B | S | 12 tok/s | ||
| 35B | S | 33.5 tok/s | ||
| 30B | S | 37.5 tok/s |
Frequently asked questions
Can MacBook Pro M3 Max 64GB run Codestral 2 25.08?
Yes, MacBook Pro M3 Max 64GB can run Codestral 2 25.08 with a A grade (Runs well). Expected decode speed: 18.1 tok/s.
How much VRAM does Codestral 2 25.08 need?
Codestral 2 25.08 (22B parameters) requires approximately 23.7 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 MacBook Pro M3 Max 64GB?
On MacBook Pro M3 Max 64GB, Codestral 2 25.08 achieves approximately 18.1 tokens per second decode speed with a time-to-first-token of 10713ms using Q4_K_M quantization.
Can MacBook Pro M3 Max 64GB run Codestral 2 25.08 for coding?
For coding workloads, Codestral 2 25.08 on MacBook Pro M3 Max 64GB receives a A grade with 18.1 tok/s and 163K context.
What context window can Codestral 2 25.08 use on MacBook Pro M3 Max 64GB?
On MacBook Pro M3 Max 64GB, Codestral 2 25.08 can safely use up to 163K tokens of context. The model's official context limit is 256K, but available memory constrains the safe maximum.
Is unified memory on MacBook Pro M3 Max 64GB as fast as VRAM for Codestral 2 25.08?
Not always. MacBook Pro M3 Max 64GB 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-max-64gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>
Preview: