Command R 35B needs ~19.6 GB VRAM. MacBook Air M4 24GB has 17.3 GB. With Q2_K quantization, expect ~9 tok/s.
Operating mode
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
10.0 GB over capacity — needs offload or smaller quantization
Fit status
Too heavy
Decode
4.4 tok/s
TTFT
44284 ms
Safe context
4K
Memory
27.3 GB / 17.3 GB
Offload
40%
It fits through host-memory offload, and offload is the main reason performance drops.
CPU or host-memory offload is active
About 10% of the working set spills out of accelerator memory, which usually hurts latency and sustained decode throughput.
Very little memory headroom
You can run the model, but there is not much room left for longer context, bigger batches, extra apps, or future model updates.
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.
Remove offload with more accelerator memory
Prioritize a GPU or unified-memory tier that fits the whole model natively. Removing offload usually helps more than small compute gains.
Buy headroom, not only minimum fit
A slightly larger memory tier gives you safer context growth and makes the recommendation more future-proof.
Increase host RAM if you keep offloading
This setup may need roughly 1.6 GB of extra host RAM just for the offloaded portion, before OS and other tools.
| Workload | Grade | Fit | Decode | TTFT | Context |
|---|---|---|---|---|---|
| Chat | F | Too heavy | 4.6 tok/s | 22939 ms | 4K |
| Coding | F | Too heavy | 4.4 tok/s | 44284 ms | 4K |
| Agentic Coding | F | Too heavy | 4.0 tok/s | 70856 ms | 4K |
| Reasoning | F | Too heavy | 4.4 tok/s | 52336 ms | 4K |
| RAG | F | Too heavy | 4.0 tok/s | 88570 ms | 4K |
How Command R 35B (35B params) fits at each quantization level on MacBook Air M4 24GB (17.3 GB usable).
| Quant | Bits | VRAM | Quality | Fit |
|---|---|---|---|---|
Q2_K | 2 | 13.7 GB | Low | F0 |
Q3_K_S | 3 | 17.2 GB | Low | F0 |
NVFP4 | 4 | 19.6 GB | Medium | F0 |
Q4_K_M | 4 | 21.3 GB | Medium | F0 |
Q5_K_M | 5 | 25.2 GB | High | F0 |
Q6_K | 6 | 28.7 GB | High | F0 |
Q8_0 | 8 | 37.5 GB | Very High | F0 |
F16 | 16 | 71.8 GB | Maximum | F0 |
Copy-paste commands to run Command R 35B on your machine.
Run
ollama run command-rUpgrade options
Makes the model fit on the accelerator instead of staying completely out of reach.
Removes host-memory offload, which is usually the single biggest latency and throughput win.
~$1,099 MSRP
Makes the model fit on the accelerator instead of staying completely out of reach.
Removes host-memory offload, which is usually the single biggest latency and throughput win.
~$1,599 MSRP
Makes the model fit on the accelerator instead of staying completely out of reach.
Adds memory headroom for longer context windows and future model growth.
~$1,999 MSRP
Yes, MacBook Air M4 24GB can run Command R 35B at Q2_K quantization (Very compromised (needs ~1.6 GB host RAM)). The recommended Q4_K_M requires 27.3 GB which exceeds available memory, but at Q2_K it needs only 19.6 GB. Expected decode speed: 8.6 tok/s.
Command R 35B (35B parameters) requires approximately 27.3 GB at Q4_K_M quantization. On MacBook Air M4 24GB, it fits at Q2_K using 19.6 GB.
The recommended quantization is Q4_K_M, but on MacBook Air M4 24GB the best fitting quantization is Q2_K, which uses 19.6 GB.
On MacBook Air M4 24GB, Command R 35B achieves approximately 8.6 tokens per second decode speed with a time-to-first-token of 22430ms using Q2_K quantization.
For coding workloads, Command R 35B on MacBook Air M4 24GB receives a F grade with 4.4 tok/s and 4K context.
On MacBook Air M4 24GB, Command R 35B can safely use up to 4K tokens of context at Q2_K quantization. The model's official context limit is 131K, but available memory constrains the safe maximum.
Remove offload with more accelerator memory. Prioritize a GPU or unified-memory tier that fits the whole model natively. Removing offload usually helps more than small compute gains.
Not always. MacBook Air M4 24GB 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.
Paste this snippet into any page to show a live fit card.
<iframe src="https://willitrunai.com/embed/command-r-35b-on-m4-air-24gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>
Preview: