Skip to content
RfRigFit

No. Qwen2.5 32B Instruct does not fit on the Mac mini M4 16GB at Q4. The estimate is 22.0 GB and usable memory is 11.2 GB.

Can the Mac mini M4 16GB run Qwen2.5 32B Instruct?

Data updated . Last reviewed the same day, when this catalog snapshot was written.

Usable memory on this 16 GB unified-memory config is 11.2 GB (70% of the sticker figure). A result under 2 GB of headroom is labeled tight.

Quant ladder

Estimated memory for Qwen2.5 32B Instruct on Mac mini M4 16GB
QuantEstimateHeadroomEst. tok/sVerdict
Q422.0 GB-10.8 GB6.04 tok/sNo
Q837.0 GB-25.8 GB3.45 tok/sNo
FP1678.6 GB-67.4 GB1.83 tok/sNo

KV cache at 8K and 32K

FP16 KV-cache estimate: 2.1 GB at 8,192 tokens and 8.6 GB at 32,768 tokens. GQA counts two tensors (K and V) for the stored KV heads and head dimension. config.json also sets a sliding window of 131,072 tokens. The figures above assume every counted layer stores the full context, so they can overstate cache on sliding layers.

Offload

The Q4 estimate is 10.8 GB over usable unified memory. There is no separate GPU to spill from.

Ollama

This command pulls the Q4_K_M file from Qwen/Qwen2.5-32B-Instruct-GGUF, the Hub repo whose file size is used above. It is not an official Ollama library tag.

ollama run hf.co/Qwen/Qwen2.5-32B-Instruct-GGUF:Q4_K_M

What fits instead

All hardware for Qwen2.5 32B Instruct · All models for the Mac mini M4 16GB

Questions

How much memory does Qwen2.5 32B Instruct need at Q4?
The Q4 figure used here is 22.0 GB. GGUF file size plus an FP16 KV-cache estimate at 8,192 tokens. The cache counts only the layers and heads named in the method on the About page.
Can the Mac mini M4 16GB run Qwen2.5 32B Instruct?
No. Qwen2.5 32B Instruct does not fit on the Mac mini M4 16GB at Q4. The estimate is 22.0 GB and usable memory is 11.2 GB.
What is the cheapest catalog device that runs Qwen2.5 32B Instruct at Q4?
Radeon RX 7900 XTX, list price $999.
How fast is Qwen2.5 32B Instruct on the Mac mini M4 16GB, as a bandwidth estimate?
About 6.04 tok/s at Q4. That is device bandwidth divided by active weight bytes, not a measured run.