text model · Qwen3 · iOS
Can I run Qwen3 32B on iPhone 17?
No. Qwen3 32B needs ~22 GB even at Q4_K_M, but iPhone 17 only has ~4.5 GB usable.
Needs ~22 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 17.5 GB: Qwen3 32B needs roughly 22 GB at Q4_K_M and iPhone 17 leaves only about 4.5 GB usable for a model. The lightest tracked hardware that runs Qwen3 32B is the Nvidia GeForce RTX 4090 (24GB) at 24 GB. See Qwen3 32B on Nvidia GeForce RTX 4090 (24GB).
- Q4_K_M needed
- ~22 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
- 32B
- Q4_K_M size
- 19.8 GB
- Q8_0 size
- 34.8 GB
- Context
- 32k
- Ollama tag
- qwen3:32b
- Memory
- 8 GB unified
- Usable for weights
- ~4.5 GB
- Best runtime
- llama.cpp + Metal (via PocketPal or Off Grid app)
What you can run instead
Run Qwen3 32B on other hardware
FAQ
Can iPhone 17 run Qwen3 32B?
No. Qwen3 32B needs ~22 GB even at Q4_K_M, but iPhone 17 only has ~4.5 GB usable.
How much memory does Qwen3 32B need?
iPhone 17 does not have enough memory. At Q4_K_M the weights are ~19.8 GB; with KV cache and runtime overhead, budget ~22 GB at a 4k context.
What is the best tool to run Qwen3 32B 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/qwen3-32b/iphone-17) Sources
- aider.chat
- 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
- gorilla.cs.berkeley.edu
- huggingface.co
- layla-network.ai
- lmarena.ai
- macrumors.com
- ollama.com
- privatellm.app
- qwenlm.github.io
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.