text model · Nemotron · iOS
Can I run Llama-3.3-Nemotron-Super-49B-v1 on iPhone 17 Pro?
No. Llama-3.3-Nemotron-Super-49B-v1 needs ~30.6 GB even at Q4_K_M, but iPhone 17 Pro only has ~8 GB usable.
Needs ~30.6 GB even at Q4_K_M, but only ~8 GB is usable.
That figure is at a 4k context and moves about ±15% as context length changes.
The gap is about 22.6 GB: Llama-3.3-Nemotron-Super-49B-v1 needs roughly 30.6 GB at Q4_K_M and iPhone 17 Pro leaves only about 8 GB usable for a model. The lightest tracked hardware that runs Llama-3.3-Nemotron-Super-49B-v1 is the Nvidia GeForce RTX 5090 (32GB) at 32 GB. See Llama-3.3-Nemotron-Super-49B-v1 on Nvidia GeForce RTX 5090 (32GB).
- Q4_K_M needed
- ~30.6 GB
- Usable on device
- ~8 GB
- Device memory
- 12 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
- 49B
- Q4_K_M size
- 28.14 GB
- Q8_0 size
- 49.36 GB
- Context
- 128k
- Memory
- 12 GB unified
- Usable for weights
- ~8 GB
- Power draw
- ~12 W
- Best runtime
- llama.cpp + Metal (via PocketPal or Off Grid app)
What you can run instead
Run Llama-3.3-Nemotron-Super-49B-v1 on other hardware
FAQ
Can iPhone 17 Pro run Llama-3.3-Nemotron-Super-49B-v1?
No. Llama-3.3-Nemotron-Super-49B-v1 needs ~30.6 GB even at Q4_K_M, but iPhone 17 Pro only has ~8 GB usable.
How much memory does Llama-3.3-Nemotron-Super-49B-v1 need?
iPhone 17 Pro does not have enough memory. At Q4_K_M the weights are ~28.14 GB; with KV cache and runtime overhead, budget ~30.6 GB at a 4k context.
What is the best tool to run Llama-3.3-Nemotron-Super-49B-v1 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/nemotron-super-49b/iphone-17-pro) 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.