text model · Granite · iOS
Can I run Granite 3.1 2B on iPhone 17?
Yes. Granite 3.1 2B runs on iPhone 17 at Q4_K_M (~2.8 GB of ~4.5 GB usable).
Runs at Q4_K_M using ~2.8 GB of ~4.5 GB usable. You have room for Q8_0 for higher quality.
- Q4_K_M needed
- ~2.8 GB
- Usable on device
- ~4.5 GB
- Device memory
- 8 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
- 8 GB unified
- Usable for weights
- ~4.5 GB
- Best runtime
- llama.cpp + Metal (via PocketPal or Off Grid app)
You could also run
Run Granite 3.1 2B on other hardware
FAQ
Can iPhone 17 run Granite 3.1 2B?
Yes. Granite 3.1 2B runs on iPhone 17 at Q4_K_M (~2.8 GB of ~4.5 GB usable).
How much memory does Granite 3.1 2B need?
iPhone 17 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.