text model · Gemma · iOS
Can I run Gemma 3 270M on iPhone 17?
Yes. Gemma 3 270M runs on iPhone 17 at Q4_K_M (~1.1 GB of ~4.5 GB usable).
Runs at Q4_K_M using ~1.1 GB of ~4.5 GB usable. You have room for FP16 for higher quality.
That figure is at a 4k context and moves about ±15% as context length changes. iPhone 17 leaves ~3.4 GB of headroom, room to step up to FP16 for higher quality.
- Q4_K_M needed
- ~1.1 GB
- Usable on device
- ~4.5 GB
- Device memory
- 8 GB
- Best quant
- Q4_K_M
Which quant fits
How to run it
On iOS use Apple Foundation Models (Built into iOS 26, ~3B on-device model, zero download, fully private.).
- Parameters
- 0.27B
- Q4_K_M size
- 0.2 GB
- Q8_0 size
- 0.27 GB
- Context
- 32k
- Ollama tag
- gemma3:270m
- 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 Gemma 3 270M on other hardware
FAQ
Can iPhone 17 run Gemma 3 270M?
Yes. Gemma 3 270M runs on iPhone 17 at Q4_K_M (~1.1 GB of ~4.5 GB usable).
How much memory does Gemma 3 270M need?
iPhone 17 has room to spare. At Q4_K_M the weights are ~0.2 GB; with KV cache and runtime overhead, budget ~1.1 GB at a 4k context.
What is the best tool to run Gemma 3 270M 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.
Embed this
A live badge for your model card or README, updated as the data is. [](https://localmodel.run/can-i-run/gemma-3-270m/iphone-17) 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.