on

Can the Apple iPhone 17 Pro / 17 Pro Max run d1 2B?

20Basic quality (D) · 20 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 55/100 (quality, fit, speed and memory use) sets the ranking.

Yes, it runs great

Runs great. At Q5_K_M it needs about 2.1 GB of 7.2 GB usable, with an estimated speed of 41.7 tok/s.

Best quant
Q5_K_M
Generation speed
41.7 tok/s
Prompt processing
1,002 tok/s
First token (1K prompt)
1.0 s
Largest safe context
125K

Best app to run it on the Apple iPhone 17 Pro / 17 Pro Max

On iOS

PocketPal AI

Mobile app · runs on llama.cpp

  • Runs the model on the device itself, offline: download it once in the app.

Get it on the App Store Then download d1 2B in the app

How we choose: the files published for this model, your operating system and GPU, whether it fits fully in memory, and published speed tests (MLX vs llama.cpp on Apple silicon, vLLM vs llama.cpp vs Ollama on NVIDIA). Details.

Download d1 2B

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. Use d1-2B-Q4_K_M.gguf, the largest single file that fits (mobile apps can’t open a model split into parts).

On iPhone or iPad

PocketPal AI

Free mobile app · runs the model on the device with llama.cpp

Get it on the App Store

  1. Install PocketPal AI (free) and open it.
  2. Tap the menu (☰), then Models, then + and Add from Hugging Face.
  3. Search for LiquidAI/d1-2B-GGUF, open it and download d1-2B-Q4_K_M.gguf.
  4. Tap Load next to the model and start a chat. It runs on the device, with no connection needed from then on.
Files and commands for a computer

Quantized files · GGUF

Works in LM Studio, llama.cpp, Jan and Ollama. No sign-in needed.

huggingface.co/LiquidAI/d1-2B-GGUF (opens in a new tab)

ollama run hf.co/LiquidAI/d1-2B-GGUF

Original weights · Hugging Face

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

huggingface.co/LiquidAI/d1-2B (opens in a new tab)

No sign-in needed.

Links checked 1 day ago against Hugging Face, Ollama and GitHub.

How it’s rated

Quality 20Basic quality (D) · 20 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 55/100 (quality, fit, speed and memory use) sets the ranking.
How capable the model itself is at Q5_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 great
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.9.2 / 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.25.0 / 25
SpeedGeneration speed against a 40 tokens/s target for LLMs, or render time against a target for image and video.15.0 / 15
Memory useRewards using the memory you have, so a bigger, better variant beats a tiny one that leaves most memory idle.6.6 / 15
Match score55.8 / 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 1.5 GB 7.2 GB 82.9 tok/s Runs great 14Basic quality (D) · 14 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 51/100 (quality, fit, speed and memory use) sets the ranking. —
Q3_K_M 1.6 GB 7.2 GB 65.2 tok/s Runs great 17Basic quality (D) · 17 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 53/100 (quality, fit, speed and memory use) sets the ranking. —
Q4_K_M 1.9 GB 7.2 GB 50.5 tok/s Runs great 19Basic quality (D) · 19 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 54/100 (quality, fit, speed and memory use) sets the ranking. Q4_K_M
Q5_K_M 2.1 GB 7.2 GB 41.7 tok/s Runs great 20Basic quality (D) · 20 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 55/100 (quality, fit, speed and memory use) sets the ranking. —
Q6_K 2.3 GB 7.2 GB 35.0 tok/s Runs great 20Basic quality (D) · 20 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 55/100 (quality, fit, speed and memory use) sets the ranking. —
Q8_0 2.7 GB 7.2 GB 25.7 tok/s Runs well 21Basic quality (D) · 21 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 55/100 (quality, fit, speed and memory use) sets the ranking. Q8_0
F16 4.5 GB 7.2 GB 11.8 tok/s Runs well 21Basic quality (D) · 21 of 100: how capable the model is at F16, whatever it runs on. Match score 57/100 (quality, fit, speed and memory use) sets the ranking. BF16

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

Other hardware that runs it

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.

Was this page helpful?