image model · flux · iOS
Can I run FLUX.1 dev on iPhone 15 Pro?
Needs ~6.5 GB at Q4 GGUF, but only ~4.5 GB is usable on iPhone 15 Pro. With aggressive CPU offload it can run on as little as ~3 GB, much slower.
Needs ~6.5 GB at Q4 GGUF, but only ~4.5 GB is usable on iPhone 15 Pro. With aggressive CPU offload it can run on as little as ~3 GB, much slower.
The gap is about 2 GB: FLUX.1 dev needs roughly 6.5 GB and iPhone 15 Pro leaves only about 4.5 GB usable for a model. The lightest tracked hardware that runs FLUX.1 dev is the Nvidia GeForce RTX 3060 Ti (8GB) at 8 GB. See FLUX.1 dev on Nvidia GeForce RTX 3060 Ti (8GB).
- Peak VRAM
- ~6.5 GB
- Usable on device
- ~4.5 GB
- Device memory
- 8 GB
- Quant
- Q4 GGUF
- Type
- image (DIT)
- Parameters
- 12B
- Peak VRAM
- ~6.5 GB at Q4 GGUF
- Resolution
- 1024×1024
- License
- FLUX.1-dev Non-Commercial License
- Memory
- 8 GB unified
- Usable for weights
- ~4.5 GB
- Power draw
- ~14 W
- Best runtime
- llama.cpp + Metal (via PocketPal or Off Grid app)
What you can run instead
Run FLUX.1 dev on other hardware
FAQ
Can iPhone 15 Pro run FLUX.1 dev?
Needs ~6.5 GB at Q4 GGUF, but only ~4.5 GB is usable on iPhone 15 Pro. With aggressive CPU offload it can run on as little as ~3 GB, much slower.
How much VRAM does FLUX.1 dev need?
iPhone 15 Pro does not have enough memory. At Q4 GGUF the realistic peak is ~6.5 GB of VRAM, versus ~33 GB with every component kept resident (no offload). With aggressive CPU offload it drops to ~3 GB, much slower.
What do I use to run FLUX.1 dev locally?
FLUX.1 dev runs in ComfyUI or Draw Things (among others). It loads as a diffusion checkpoint plus its text encoder and VAE, not a single chat command.
Sources
-
cpu-monkey.com · 1 source
-
developer.apple.com · 1 source
-
enclaveai.app · 1 source
-
forums.macrumors.com · 1 source
-
github.com · 3 sources
-
gsmarena.com · 1 source
-
helloexpress.net · 1 source
-
layla-network.ai · 1 source
-
privatellm.app · 1 source
-
support.apple.com · 1 source
-
techinsights.com · 1 source
-
wccftech.com · 1 source
VRAM figures are sourced peak-usage anchors at the noted quant; catalog updated 2026-10-05. See methodology.