text model · Granite · iOS
Can I run Granite 3.1 2B on iPad Pro M4 (16GB, 1TB/2TB config)?
Yes. Granite 3.1 2B runs on iPad Pro M4 (16GB, 1TB/2TB config) at Q4_K_M (~2.8 GB of ~12 GB usable).
Runs at Q4_K_M using ~2.8 GB of ~12 GB usable. You have room for FP16 for higher quality.
- Q4_K_M needed
- ~2.8 GB
- Usable on device
- ~12 GB
- Device memory
- 16 GB
- Best quant
- Q4_K_M
How to run it
On iOS use Apple Foundation Models (Built into iOS 26, ~3B on-device model, zero download, fully private.). Phones realistically run 1B-4B class models. Anything larger thermally throttles or OOMs.
- Parameters
- 2.53B
- Q4_K_M size
- 1.55 GB
- Q8_0 size
- 2.69 GB
- Context
- 128k
- Ollama tag
- granite3.1-dense:2b
- Memory
- 16 GB unified
- Usable for weights
- ~12 GB
- Best runtime
- MLX (via Python or Swift; mlx-lm package)
You could also run
Run Granite 3.1 2B on other hardware
FAQ
Can iPad Pro M4 (16GB, 1TB/2TB config) run Granite 3.1 2B?
Yes. Granite 3.1 2B runs on iPad Pro M4 (16GB, 1TB/2TB config) at Q4_K_M (~2.8 GB of ~12 GB usable).
How much memory does Granite 3.1 2B need?
iPad Pro M4 (16GB, 1TB/2TB config) has room to spare. At Q4_K_M the weights are ~1.55 GB; with KV cache and runtime overhead, budget ~2.8 GB at a 4k context.
What is the best tool to run Granite 3.1 2B on iOS?
On iPhone and iPad, Apple Foundation Models (Built into iOS 26, ~3B on-device model, zero download, fully private.) is the standard choice. Phones realistically run 1B-4B class models. Anything larger thermally throttles or OOMs.
Sources
Memory figures are estimates. See methodology.