text model · MiniCPM · iOS
Can I run MiniCPM-V 4.6 on iPhone 17?
Yes. MiniCPM-V 4.6 runs on iPhone 17 at Q4_K_M (~1.6 GB of ~4.5 GB usable).
Runs at Q4_K_M using ~1.6 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 ~2.9 GB of headroom, room to step up to FP16 for higher quality.
- Q4_K_M needed
- ~1.6 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
- 1.3B
- Q4_K_M size
- 0.53 GB
- Q8_0 size
- 0.81 GB
- Context
- 256k
- Ollama tag
- minicpm-v4.6
- 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 MiniCPM-V 4.6 on other hardware
FAQ
Can iPhone 17 run MiniCPM-V 4.6?
Yes. MiniCPM-V 4.6 runs on iPhone 17 at Q4_K_M (~1.6 GB of ~4.5 GB usable).
How much memory does MiniCPM-V 4.6 need?
iPhone 17 has room to spare. At Q4_K_M the weights are ~0.53 GB; with KV cache and runtime overhead, budget ~1.6 GB at a 4k context.
What is the best tool to run MiniCPM-V 4.6 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
[](https://localmodel.run/can-i-run/minicpm-v-4.6/iphone-17) Sources
- apple.com
- developer.apple.com
- en.wikipedia.org/wiki/Apple_A19
- en.wikipedia.org/wiki/IPhone_17
- enclaveai.app
- github.com/a-ghorbani
- github.com/google-ai-edge
- github.com/mainframecomputer
- huggingface.co/openbmb/MiniCPM-V-4_6
- huggingface.co/openbmb/MiniCPM-V-4_6-gguf
- layla-network.ai
- macrumors.com
- ollama.com
- privatellm.app
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.