SenseNova Loop 9B Preview on Apple iPhone 17 Pro / 17 Pro Max

Can the Apple iPhone 17 Pro / 17 Pro Max run SenseNova Loop 9B Preview?

Yes, it runs well (tight fit)

Runs well (tight fit). At Q4_K_M it needs about 7.0 GB of 7.2 GB usable, with an estimated speed of 10.0 tok/s.

Best quant: Q4_K_M
Generation speed: 10.0 tok/s
Prompt processing: 199 tok/s
First token (1K prompt): 5.1 s
Largest safe context: 12K

Download SenseNova Loop 9B Preview

On a phone, tablet or other mobile device you install a chat app and get the model file through it, so there are no commands to copy.

On iPhone or iPad

No mobile app in the App Store runs SenseNova Loop 9B Preview right now: mobile apps need a GGUF version, and none is published. Mobile apps · models that run on mobile devices.

Files and commands for a computer

Original weights · Hugging Face

Full-precision files from SenseTime, for fine-tuning, vLLM, Transformers.

huggingface.co/sensenova/SenseNova-Loop-9B-Preview (opens in a new tab)

No sign-in needed.

Official repo · GitHub

Reference code, inference scripts and docs from SenseTime. The weights themselves download from Hugging Face.

github.com/OpenSenseNova/SenseNova-Loop (opens in a new tab)

SenseNova's official repo for the Loop model. vLLM and SGLang support is still in open pull requests.

git clone https://github.com/OpenSenseNova/SenseNova-Loop

Links checked 5 days ago against Hugging Face, Ollama and GitHub.

How it’s rated

Quality 74Great quality (A) · 74 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 79/100 (quality, fit, speed and memory use) sets the ranking.: How capable the model itself is at Q4_K_M, from its editorial quality tier scaled by the quantization or precision. It’s the same on any hardware that runs this variant. Scale: A+ 85+ · A 70+ · B 55+ · C 40+ · D under 40.
Runs Runs welltight fit: How well it runs on the Apple iPhone 17 Pro / 17 Pro Max: speed, capped by how well it fits in memory. Runs great: 30+ tokens/s (or near the image, video or decision speed target) · Runs well: 10+ tokens/s · Slow: 3+ tokens/s · Very slow: under 3 · Won’t run: doesn’t fit even with offload. A tight fit or RAM offload caps it at Runs well; heavy offload caps it at Slow.

Match score

To order lists, each result also gets a match score out of 100 from four parts. It favors the most capable model that still runs well.

Model qualityEditorial quality tier of the model, scaled by the quantization or precision used.	33.3 / 45
Memory fitFull marks when the model fits in the share of unified memory the GPU can use; fewer when it goes past that limit.	24.0 / 25
SpeedGeneration speed against a 40 tokens/s target for LLMs, or render time against a target for image and video.	7.5 / 15
Memory useRewards using the memory you have, so a bigger, better variant beats a tiny one that leaves most memory idle.	15.0 / 15
Match score	79.9 / 100

The match score orders results; it is not shown as a grade. Quality and Runs are the two ratings in the tables.

Every quantization on the Apple iPhone 17 Pro / 17 Pro Max

Quant	Memory needed	Available	Speed	Runs	Quality	File to pick in the app
`Q2_K`	4.9 GB	7.2 GB	16.5 tok/s	Runs well	54Fair quality (C) · 54 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 74/100 (quality, fit, speed and memory use) sets the ranking.	—
`Q3_K_M`	5.8 GB	7.2 GB	13.0 tok/s	Runs well	65Good quality (B) · 65 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 78/100 (quality, fit, speed and memory use) sets the ranking.	—
`Q4_K_M`	7.0 GB	7.2 GB	10.0 tok/s	Runs welltight fit	74Great quality (A) · 74 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 79/100 (quality, fit, speed and memory use) sets the ranking.	—
`Q5_K_M`	7.9 GB	7.2 GB	—	Won't runover the app memory limit	75Great quality (A) · 75 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 10/100 (quality, fit, speed and memory use) sets the ranking.	—
`Q6_K`	9.0 GB	7.2 GB	—	Won't runover the app memory limit	77Great quality (A) · 77 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 10/100 (quality, fit, speed and memory use) sets the ranking.	—
`Q8_0`	11.3 GB	7.2 GB	—	Won't runover the app memory limit	78Great quality (A) · 78 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 10/100 (quality, fit, speed and memory use) sets the ranking.	—
`F16`	20.4 GB	7.2 GB	—	Won't runover the app memory limit	78Great quality (A) · 78 of 100: how capable the model is at F16, whatever it runs on. Match score 10/100 (quality, fit, speed and memory use) sets the ranking.	—

Memory figures assume 8K of context. Longer conversations or documents grow the KV cache.

Other hardware that runs it

78Great quality (A) · 78 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 90/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 4070 Ti SUPER Q8_0 · 43.5 tok/s · Runs great
78Great quality (A) · 78 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 90/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 4080 SUPER Q8_0 · 47.6 tok/s · Runs great
78Great quality (A) · 78 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 90/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 5070 Ti Q8_0 · 58.0 tok/s · Runs great
78Great quality (A) · 78 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 90/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 5080 Q8_0 · 62.1 tok/s · Runs great
78Great quality (A) · 78 of 100: how capable the model is at F16, whatever it runs on. Match score 90/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 5090 F16 · 53.4 tok/s · Runs great
77Great quality (A) · 77 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 89/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 4070 SUPER Q6_K · 44.4 tok/s · Runs great

Estimates come from published hardware specs and our open formulas, not from running the model on your machine. Real speed varies with runtime, drivers and settings. Numbers marked “Measured” come from a linked benchmark.