text model · Laguna · iOS
Can I run Laguna XS 2.1 on iPhone 16?
No. Laguna XS 2.1 needs ~22.2 GB even at Q4_K_M, but iPhone 16 only has ~4.5 GB usable.
Needs ~22.2 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.7 GB: Laguna XS 2.1 needs roughly 22.2 GB at Q4_K_M and iPhone 16 leaves only about 4.5 GB usable for a model. The lightest tracked hardware that runs Laguna XS 2.1 is the Nvidia GeForce RTX 4090 (24GB) at 24 GB. See Laguna XS 2.1 on Nvidia GeForce RTX 4090 (24GB).
- Q4_K_M needed
- ~22.2 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
- 33.4B (MoE, 3B active)
- Q4_K_M size
- 20 GB
- Q8_0 size
- 36 GB
- Context
- 256k
- Ollama tag
- laguna-xs-2.1
- 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 Laguna XS 2.1 on other hardware
FAQ
Can iPhone 16 run Laguna XS 2.1?
No. Laguna XS 2.1 needs ~22.2 GB even at Q4_K_M, but iPhone 16 only has ~4.5 GB usable.
How much memory does Laguna XS 2.1 need?
iPhone 16 does not have enough memory. At Q4_K_M the weights are ~20 GB; with KV cache and runtime overhead, budget ~22.2 GB at a 4k context. It is a Mixture-of-Experts model (33.4B total / 3B active), so all experts must stay in memory; memory tracks total params, not active params.
What is the best tool to run Laguna XS 2.1 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/laguna-xs-2.1/iphone-16) 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.