text model · Olmo · macOS
Can I run Olmo 3.1 32B Instruct on Apple M2 (16GB)?
No. Olmo 3.1 32B Instruct needs ~20.3 GB even at Q4_K_M, but Apple M2 (16GB) only has ~10.5 GB usable.
Needs ~20.3 GB even at Q4_K_M, but only ~10.5 GB is usable.
That figure is at a 4k context and moves about ±15% as context length changes.
The gap is about 9.8 GB: Olmo 3.1 32B Instruct needs roughly 20.3 GB at Q4_K_M and Apple M2 (16GB) leaves only about 10.5 GB usable for a model. The lightest tracked hardware that runs Olmo 3.1 32B Instruct is the Nvidia GeForce RTX 4090 (24GB) at 24 GB. See Olmo 3.1 32B Instruct on Nvidia GeForce RTX 4090 (24GB).
- Q4_K_M needed
- ~20.3 GB
- Usable on device
- ~10.5 GB
- Device memory
- 16 GB
Which quant fits
- Parameters
- 32B
- Q4_K_M size
- 18.14 GB
- Q8_0 size
- 31.9 GB
- Context
- 64k
- Ollama tag
- olmo-3.1:32b-instruct
- Memory
- 16 GB unified
- Usable for weights
- ~10.5 GB
- Power draw
- ~50 W
- Best runtime
- Ollama (llama.cpp Metal backend) / MLX
What you can run instead
Run Olmo 3.1 32B Instruct on other hardware
FAQ
Can Apple M2 (16GB) run Olmo 3.1 32B Instruct?
No. Olmo 3.1 32B Instruct needs ~20.3 GB even at Q4_K_M, but Apple M2 (16GB) only has ~10.5 GB usable.
How much memory does Olmo 3.1 32B Instruct need?
Apple M2 (16GB) does not have enough memory. 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
A live badge for your model card or README, updated as the data is. [](https://localmodel.run/can-i-run/olmo-3.1-32b-instruct/apple-m2-16gb) 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.