Can I Run Codestral on Mac mini (M4 Pro, 64 GB)?

Superseded model. Codestral has been superseded by Devstral. This page is kept for reference; the newer family is a better starting point. View Devstral →

Written by Jakub Rusinowski · Last updated May 29, 2024

Yes — comfortably

Yes, comfortably — Codestral 22B at Q8_0 needs about 26.3 GB of the 48 GB usable on Mac mini (M4 Pro, 64 GB), leaving ~21.7 GB spare and running at ~6 tok/s (estimated), with room for about 32,768 tokens of context.

Confidence: high · Recommended quantization: Q8_0 · Estimated speed: ~6 tok/s

Mac mini (M4 Pro, 64 GB) — what it gives a model

Usable memory for models	48 GB
Memory bandwidth	273 GB/s
Form factor	Mini PC
Operating system	macOS
Memory upgradeable	No — soldered

Codestral on Mac mini (M4 Pro, 64 GB): memory by quantization

Quant	Memory needed	Fits 48 GB?	Max context	Est. speed	Download
F16	47.1 GB	✓ Yes	8K	~3.3 tok/s	44.4 GB
Q8_0	26.3 GB	✓ Yes	32K	~6 tok/s	23.6 GB
Q6_K	20.9 GB	✓ Yes	32K	~7.6 tok/s	18.2 GB
Q5_K_M	18.4 GB	✓ Yes	32K	~8.7 tok/s	15.7 GB
Q4_K_M	16.1 GB	✓ Yes	32K	~10.1 tok/s	13.4 GB
Q3_K_M	12.1 GB	✓ Yes	32K	~13.8 tok/s	9.5 GB
Q2_K	10 GB	✓ Yes	32K	~17.2 tok/s	7.3 GB

What to watch out for

Memory on this machine is not upgradeable, so the configuration you buy is the ceiling for every model you will ever run on it.

Mac mini M4 Pro 64 GB limitations

M4 Pro memory bandwidth is half the M4 Max's, so large models that fit will still generate roughly half as fast.

Recommended setup

Ollama or LM Studio (Metal) — MLX for the fastest Apple-native throughput

How these numbers are calculated

Memory need = quantized weights + KV cache at 8,192 tokens (f16) + 0.8 GB runtime overhead.
64 GB unified memory at 273 GB/s, shared between CPU and GPU.
macOS reserves a share of unified memory for the system, so not all of it is available to a model.
Throughput is a memory-bandwidth roofline estimate, not a measurement. It is labelled "estimated" everywhere it appears.
KV cache is computed from this model's published attention configuration.

FAQ