VOOZH about

URL: https://willitrunai.com/can-run/command-r-35b-on-m3-air-24gb


Can Command R 35B run on MacBook Air M3 24GB?

YES — With Q2_K

B60Good
Estimated from fit model

Command R 35B needs ~19.6 GB VRAM. MacBook Air M3 24GB has 17.3 GB. With Q2_K quantization, expect ~4 tok/s.

Runtime: llama.cppCapacity: OffloadBandwidth: Very lowStack: StandardBottleneck: Host offload
Share:

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.

Command R 35B at Q4_K_M needs 27.3 GB — too much for MacBook Air M3 24GB (17.3 GB). Runs at Q2_K (19.6 GB) with low quality.
Capabilities:

Select quantization to explore

Q4_K_M (Medium quality) — 27.3 GB, exceeds 17.3 GB available
27.3 GB required17.3 GB available
158% VRAM needed

10.0 GB over capacity — needs offload or smaller quantization

Fit status

Too heavy

Decode

2.0 tok/s

TTFT

96800 ms

Safe context

4K

Memory

27.3 GB / 17.3 GB

Offload

40%

Memory breakdown

Weights21.3 GB
KV Cache2.4 GB
Runtime0.9 GB
Headroom2.6 GB

See how fast it feels

With memory offload — actual speed may be lower
See how fast it feelsCommand R 35B on MacBook Air M3 24GB
1st promptCold start — includes initialization
>What is local AI inference?
Local AI inference means running an AI language model directly on your own hardware — your laptop, desktop, or server — instead of sending requests to a remote cloud API. When you run inference locally the model weights are loaded into your GPU or unified memory. Each token you generate requires reading those weights from memory, so memory bandwidth is the main bottleneck for decode speed. Key benefits of running locally: - Full privacy: your prompts never leave your machine - No per-token cost or rate limits - Works offline once the model is downloaded - Latency depends only on your hardware
2nd promptWarm — model ready, no init overhead
>How much VRAM do I need?
It depends on the model size and quantization level. A rough rule of thumb: Model size Q4 (4-bit) Q8 (8-bit) FP16 7B params ~4.3 GB ~7.5 GB ~14 GB 13B params ~7.9 GB ~13.9 GB ~26 GB 70B params ~42.7 GB ~74.9 GB ~140 GB Most people use 4-bit quantization (Q4_K_M) which gives 90-95% of full quality at a fraction of the memory. A 24 GB GPU can comfortably run most 7B-13B models.
Estimated: 2.0 tok/s decode · 96.8s TTFT (warm) · 5 tok/s prefill

What limits this setup

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.

Best improvement path

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.

Performance by workload

WorkloadGradeFitDecodeTTFTContext
ChatFToo heavy2.0 tok/s52800 ms4K
CodingFToo heavy2.0 tok/s96800 ms4K
Agentic CodingFToo heavy2.0 tok/s140800 ms4K
ReasoningFToo heavy2.0 tok/s114400 ms4K
RAGFToo heavy2.0 tok/s176000 ms4K

Quantization options

How Command R 35B (35B params) fits at each quantization level on MacBook Air M3 24GB (17.3 GB usable).

QuantBitsVRAMQualityFit
Q2_K
2
13.7 GB
LowF0
Q3_K_S
3
17.2 GB
LowF0
NVFP4
4

Get started

Copy-paste commands to run Command R 35B on your machine.

Run

ollama run command-r

Upgrade options

Hardware that runs Command R 35B well

Mac mini M4 64GBBudget pick
64 GB Unified (+40)120 GB/s (+20)
A
Makes the model fit on the accelerator instead of staying completely out of reach.7.9 tok/s decode

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

MacBook Pro M4 Pro 64GBBest value
64 GB Unified (+40)273 GB/s (+173)
A
Makes the model fit on the accelerator instead of staying completely out of reach.19.3 tok/s decode

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

MacBook Pro M3 Pro 36GBApple upgrade
36 GB Unified (+12)150 GB/s (+50)
B
Makes the model fit on the accelerator instead of staying completely out of reach.4.7 tok/s decode

Makes the model fit on the accelerator instead of staying completely out of reach.

Raises estimated decode speed by about 135%.

~$1,999 MSRP

Frequently asked questions

See all results for MacBook Air M3 24GBSee all hardware for Command R 35B
19.6 GB
Medium
F0
Q4_K_M
4
21.3 GB
MediumF0
Q5_K_M
5
25.2 GB
HighF0
Q6_K
6
28.7 GB
HighF0
Q8_0
8
37.5 GB
Very HighF0
F16
16
71.8 GB
MaximumF0

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.