text model · Mistral · iOS
Can I run Devstral Small on iPhone 16?
No. Devstral Small needs ~15.4 GB even at Q4_K_M, but iPhone 16 only has ~4.5 GB usable.
Needs ~15.4 GB even at Q4_K_M, but only ~4.5 GB is usable.
That figure is at a 4k context and moves about ±15% as context length changes.
The gap is about 10.9 GB: Devstral Small needs roughly 15.4 GB at Q4_K_M and iPhone 16 leaves only about 4.5 GB usable for a model. The lightest tracked hardware that runs Devstral Small is the Apple M4 (24GB) at 24 GB. See Devstral Small on Apple M4 (24GB).
- Q4_K_M needed
- ~15.4 GB
- Usable on device
- ~4.5 GB
- Device memory
- 8 GB
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
- 24B
- Q4_K_M size
- 13.35 GB
- Q8_0 size
- 23.33 GB
- Context
- 128k
- Ollama tag
- devstral:24b
- Memory
- 8 GB unified
- Usable for weights
- ~4.5 GB
- Power draw
- ~11 W
- Best runtime
- llama.cpp + Metal (via PocketPal or Off Grid app)
What you can run instead
Run Devstral Small on other hardware
FAQ
Can iPhone 16 run Devstral Small?
No. Devstral Small needs ~15.4 GB even at Q4_K_M, but iPhone 16 only has ~4.5 GB usable.
How much memory does Devstral Small need?
iPhone 16 does not have enough memory. At Q4_K_M the weights are ~13.35 GB; with KV cache and runtime overhead, budget ~15.4 GB at a 4k context.
What is the best tool to run Devstral Small 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/devstral-small/iphone-16) Sources
-
apple.com · 1 source
-
developer.apple.com · 1 source
-
en.wikipedia.org · 2 sources
-
enclaveai.app · 1 source
-
github.com · 3 sources
-
gsmarena.com · 1 source
-
huggingface.co · 2 sources
-
layla-network.ai · 1 source
-
macrumors.com · 1 source
-
ollama.com · 1 source
-
privatellm.app · 1 source
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.