Skip to content

text model · Olmo · macOS

Can I run Olmo 3.1 32B Instruct on Apple M5 (32GB)?

Compatibility verdict VRAM threshold engine
Yes, but tight GPU accelerated ~7 tok/s est.

Yes. Olmo 3.1 32B Instruct runs on Apple M5 (32GB) at Q4_K_M (~20.3 GB of ~21 GB usable).

Needs ~20.3 GB Device usable ~21 GB

Fits at Q4_K_M (~20.3 GB of ~21 GB usable) but with little headroom. Close other apps, or drop to a 2k context to free about a gigabyte.

That figure is at a 4k context and moves about ±15% as context length changes. Apple M5 (32GB) leaves ~0.7 GB of headroom.

Q4_K_M needed
~20.3 GB
Usable on device
~21 GB
Device memory
32 GB
Best quant
Q4_K_M
Share on X Share on Reddit

Which quant fits

Quant ladder vs ~21 GB usable
Q2_K
~15.6 GB
Q3_K_M
~17.8 GB
Q4_K_M
~20.3 GB
Q5_K_M
~25 GB
Q6_K
~28.4 GB
Q8_0
~34.1 GB
FP16
~66.2 GB
The line marks Apple M5 (32GB)'s ~21 GB budget; rungs past it are too large.

Run it

Install commands macOS

Pick your tool. All 3 load the same Q4_K_M weights.

Ollama
$ ollama run olmo-3.1:32b-instruct
llama.cpp
$ llama-cli -hf bartowski/allenai_Olmo-3.1-32B-Instruct-GGUF:Q4_K_M
LM Studio
$ lms get bartowski/allenai_Olmo-3.1-32B-Instruct-GGUF
Model Olmo
Parameters
32B
Q4_K_M size
18.14 GB
Q8_0 size
31.9 GB
Context
64k
Ollama tag
olmo-3.1:32b-instruct
Full Olmo 3.1 32B Instruct requirements →
Device macOS
Memory
32 GB unified
Usable for weights
~21 GB
Best runtime
MLX direct / Ollama (MLX backend)
Best models for Apple M5 (32GB) →

You could also run

Run Olmo 3.1 32B Instruct on other hardware

FAQ

Can Apple M5 (32GB) run Olmo 3.1 32B Instruct?

Yes. Olmo 3.1 32B Instruct runs on Apple M5 (32GB) at Q4_K_M (~20.3 GB of ~21 GB usable).

How much memory does Olmo 3.1 32B Instruct need?

It is a tight fit on Apple M5 (32GB). At Q4_K_M the weights are ~18.14 GB; with KV cache and runtime overhead, budget ~20.3 GB at a 4k context.

What is the best tool to run Olmo 3.1 32B Instruct on macOS?

LM Studio for a simple setup; mlx-lm for the most speed. vLLM is NOT a Mac tool, it is a CUDA/Linux serving engine. Unified memory is not a fixed VRAM slice; ~70% is usable for weights.

Embed this

Olmo 3.1 32B Instruct on Apple M5 (32GB) compatibility badge A live badge for your model card or README, updated as the data is.
Markdown
$ [![Olmo 3.1 32B Instruct on Apple M5 (32GB)](https://localmodel.run/badge/olmo-3.1-32b-instruct/apple-m5-32gb.svg)](https://localmodel.run/can-i-run/olmo-3.1-32b-instruct/apple-m5-32gb)

Sources

Weights are measured from GGUF files; KV cache and overhead are computed, so totals can vary ~15% with context and runtime. Any tok/s is a bandwidth estimate. See methodology.