Can DeepSeek R1 Distill 32B run on MacBook Air M4 24GB?

YES — With Q2_K

B62Good
Estimated — low-sample bucket· few comparable runs

DeepSeek R1 Distill 32B needs ~19.9 GB VRAM. MacBook Air M4 24GB has 17.3 GB. With Q2_K quantization, expect ~9 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.

DeepSeek R1 Distill 32B at Q4_K_M needs 26.9 GB — too much for MacBook Air M4 24GB (17.3 GB). Runs at Q2_K (19.9 GB) with low quality.
Capabilities:

Select quantization to explore

Q4_K_M (Medium quality) 26.9 GB, exceeds 17.3 GB available
26.9 GB required17.3 GB available
155% VRAM needed

9.6 GB over capacity — needs offload or smaller quantization

Fit status

Too heavy

Decode

4.8 tok/s

TTFT

40157 ms

Safe context

4K

Memory

26.9 GB / 17.3 GB

Offload

40%

Memory breakdown

Weights19.5 GB
KV Cache3.9 GB
Runtime0.9 GB
Headroom2.6 GB

See how fast it feels

With memory offload — actual speed may be lower
See how fast it feelsDeepSeek R1 Distill 32B on MacBook Air M4 24GB
1st promptCold start — includes initialization
>Solve: If a train travels at 60 mph for 2.5 hours, how far does it go?
Let me work through this step by step. Given information: - Speed = 60 mph (miles per hour) - Time = 2.5 hours Formula: Distance = Speed x Time Calculation: Distance = 60 mph x 2.5 h = 150 miles The train travels 150 miles. Double-check: at 60 mph the train covers 60 miles each hour. In half an hour it covers 30 miles. So in 2.5 hours: 60 + 60 + 30 = 150 miles. Confirmed.
2nd promptWarm — model ready, no init overhead
>What if the train stops for 20 minutes halfway?
The stop doesn't change the total distance covered while moving, but it affects total trip time. Breakdown: - First half: 1.25 hours at 60 mph = 75 miles - Stop: 20 minutes (no distance) - Second half: 1.25 hours at 60 mph = 75 miles Total distance: 150 miles (same) Total time: 2.5 h + 0.33 h = 2.83 hours Average speed: 150 / 2.83 = 53 mph The distance stays the same but average speed drops to 53 mph because of the stop.
Estimated: 4.8 tok/s decode · 40.2s TTFT (warm) · 12 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 heavy5.3 tok/s20107 ms4K
CodingFToo heavy4.8 tok/s40157 ms4K
Agentic CodingFToo heavy4.1 tok/s67892 ms4K
ReasoningFToo heavy4.8 tok/s47458 ms4K
RAGFToo heavy4.1 tok/s84865 ms4K

Quantization options

How DeepSeek R1 Distill 32B (32B params) fits at each quantization level on MacBook Air M4 24GB (17.3 GB usable).

QuantBitsVRAMQualityFit
Q2_KBest for your GPU
2
12.5 GB
LowA76
Q3_K_S
3
15.7 GB
LowF0
NVFP4
4
17.9 GB
MediumF0
Q4_K_M
4
19.5 GB
MediumF0
Q5_K_M
5
23.0 GB
HighF0
Q6_K
6
26.2 GB
HighF0
Q8_0
8
34.2 GB
Very HighF0
F16
16
65.6 GB
MaximumF0

Get started

Copy-paste commands to run DeepSeek R1 Distill 32B on your machine.

Run

ollama run deepseek-r1:32b

アップグレードオプション

DeepSeek R1 Distill 32Bを快適に動かすハードウェア

Frequently asked questions

Can MacBook Air M4 24GB run DeepSeek R1 Distill 32B?

Yes, MacBook Air M4 24GB can run DeepSeek R1 Distill 32B at Q2_K quantization (Very compromised (needs ~1.6 GB host RAM)). The recommended Q4_K_M requires 26.9 GB which exceeds available memory, but at Q2_K it needs only 19.9 GB. Expected decode speed: 9.2 tok/s.

How much VRAM does DeepSeek R1 Distill 32B need?

DeepSeek R1 Distill 32B (32B parameters) requires approximately 26.9 GB at Q4_K_M quantization. On MacBook Air M4 24GB, it fits at Q2_K using 19.9 GB.

What is the best quantization for DeepSeek R1 Distill 32B?

The recommended quantization is Q4_K_M, but on MacBook Air M4 24GB the best fitting quantization is Q2_K, which uses 19.9 GB.

What speed will DeepSeek R1 Distill 32B run at on MacBook Air M4 24GB?

On MacBook Air M4 24GB, DeepSeek R1 Distill 32B achieves approximately 9.2 tokens per second decode speed with a time-to-first-token of 21058ms using Q2_K quantization.

Can MacBook Air M4 24GB run DeepSeek R1 Distill 32B for coding?

For coding workloads, DeepSeek R1 Distill 32B on MacBook Air M4 24GB receives a F grade with 4.8 tok/s and 4K context.

What context window can DeepSeek R1 Distill 32B use on MacBook Air M4 24GB?

On MacBook Air M4 24GB, DeepSeek R1 Distill 32B can safely use up to 5K tokens of context at Q2_K quantization. The model's official context limit is 33K, but available memory constrains the safe maximum.

What should I upgrade first if DeepSeek R1 Distill 32B feels slow on MacBook Air M4 24GB?

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.

Is unified memory on MacBook Air M4 24GB as fast as VRAM for DeepSeek R1 Distill 32B?

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.

See all results for MacBook Air M4 24GBSee all hardware for DeepSeek R1 Distill 32B
Embed this result

Paste this snippet into any page to show a live fit card.

<iframe src="https://willitrunai.com/embed/deepseek-r1-distill-32b-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: