TMax 4B on Apple iPhone 17 Pro / 17 Pro Max
Can the Apple iPhone 17 Pro / 17 Pro Max run TMax 4B?
Yes, it runs well
Runs well. At Q4_K_M it needs about 3.4 GB of 7.2 GB usable, with an estimated speed of 23.0 tok/s.
- Best quant
Q4_K_M- Generation speed
- 23.0 tok/s
- Prompt processing
- 457 tok/s
- First token (1K prompt)
- 2.2 s
- Largest safe context
- 120K
Download TMax 4B
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 TMax 4B 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 Ai2, for fine-tuning, vLLM, Transformers.
How it’s rated
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 quality | 26.1 / 45 | |
|---|---|---|
| Memory fit | 25.0 / 25 | |
| Speed | 11.4 / 15 | |
| Memory use | 11.0 / 15 | |
| Match score | 73.5 / 100 |
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 | 2.6 GB | 7.2 GB | 37.8 tok/s | Runs great | 42Fair quality (C) · 42 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 66/100 (quality, fit, speed and memory use) sets the ranking. | |
Q3_K_M | 2.9 GB | 7.2 GB | 29.8 tok/s | Runs well | 51Fair quality (C) · 51 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 70/100 (quality, fit, speed and memory use) sets the ranking. | |
Q4_K_M | 3.4 GB | 7.2 GB | 23.0 tok/s | Runs well | 57Good quality (B) · 57 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 73/100 (quality, fit, speed and memory use) sets the ranking. | |
Q5_K_M | 3.9 GB | 7.2 GB | 19.0 tok/s | Runs well | 59Good quality (B) · 59 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 74/100 (quality, fit, speed and memory use) sets the ranking. | |
Q6_K | 4.3 GB | 7.2 GB | 16.0 tok/s | Runs well | 60Good quality (B) · 60 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 75/100 (quality, fit, speed and memory use) sets the ranking. | |
Q8_0 | 5.3 GB | 7.2 GB | 11.7 tok/s | Runs well | 61Good quality (B) · 61 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 75/100 (quality, fit, speed and memory use) sets the ranking. | |
F16 | 9.3 GB | 7.2 GB | — | Won't runover the app memory limit | 61Good quality (B) · 61 of 100: how capable the model is at F16, whatever it runs on. Match score 8/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
-
61Good quality (B) · 61 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 82/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA GeForce RTX 4060
-
61Good quality (B) · 61 of 100: how capable the model is at F16, whatever it runs on. Match score 82/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA GeForce RTX 4070 Ti SUPER
-
61Good quality (B) · 61 of 100: how capable the model is at F16, whatever it runs on. Match score 82/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA GeForce RTX 4080 SUPER
-
61Good quality (B) · 61 of 100: how capable the model is at F16, whatever it runs on. Match score 82/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA GeForce RTX 5070 Ti
-
61Good quality (B) · 61 of 100: how capable the model is at F16, whatever it runs on. Match score 82/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA GeForce RTX 5080
-
61Good quality (B) · 61 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 78/100 (quality, fit, speed and memory use) sets the ranking.
Intel Arc B580
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.