Can Your Phone Run Bonsai 27B? RAM Requirements & Speed Estimates (July 2026)
Quick answers:
- Yes, flagship phones can run Bonsai 27B — at 4K context, the 1-bit variant needs about 4.8GB of usable RAM (3.8GB file + overhead), while the ternary variant needs about 8.4GB.
- 1-bit (3.8GB file): runs comfortably on 12GB+ phones and fits tightly on many 8GB phones at 4K context.
- Ternary (7.2GB file): fits a 16GB Android comfortably; a 12GB Android is tight, while a 12GB iPhone is over its estimated per-app memory budget. (PrismML's "5.9GB" figure is the theoretical weight size — the actual GGUF on Hugging Face is 7.17GB.)
- App support is separate: PocketPal supports the 1-bit Q1_0 path. Its current phone releases do not load the tracked ternary Q2_0 file, even on a phone with enough RAM.
- Expect roughly 8-14 tokens/s on 2024-25 flagships — PrismML reports ~11 tokens/s on iPhone 17 Pro Max.
- It's multimodal (4-bit vision tower adds ~0.5GB if enabled).
If you search for bonsai 27b requirements, bonsai 27b on android, or can my phone run bonsai 27b — this is the reference table.
What is Bonsai 27B?
Released July 14, 2026 by PrismML, Bonsai 27B is a 27.3B-parameter model distilled from Qwen3.6-27B, quantized end-to-end to 1-bit (1.125 effective bits/weight) or ternary (1.71 bits/weight). PrismML reports the 1-bit build retains ~90% of full-precision performance across 15 benchmarks. Context window: 262K (hybrid attention keeps the KV cache small). It is the first 27B-class model that genuinely fits phone memory budgets.
RAM math
| Variant | File size (HF actual) | + runtime & KV overhead* | Free RAM needed | Verdict |
|---|---|---|---|---|
| 1-bit (Q1_0, 1.125bpw) | 3.8 GB | ~1.0 GB | ~4.8 GB | 12GB Android / iPhone 17 Pro: ✅ · 8GB phones: ⚠️ tight |
| Ternary (Q2_0, 1.71bpw) | 7.2 GB | ~1.2 GB | ~8.4 GB | 16GB Android: ✅ · 12GB Android: ⚠️ tight · 12GB iPhone / 8GB: ❌ |
*4K context. Bonsai's hybrid linear attention keeps the KV cache small: every additional 4K of context adds about 0.25GB.
Which phones run it? (by device)
| Phone | RAM | 1-bit (3.8GB) | Ternary (7.2GB) | Est. speed† |
|---|---|---|---|---|
| ROG Phone 9 Pro / OnePlus 13 (24GB) | 24GB | ✅ Easy | ✅ Easy | ~9-12 tokens/s |
| Galaxy S26 Ultra / OnePlus 15 (16GB) | 16GB | ✅ | ✅ | ~10-13 tokens/s |
| Galaxy S25 Ultra / Xiaomi 15 Pro | 16GB | ✅ | ✅ | ~9-12 tokens/s |
| Galaxy S24 Ultra | 12GB | ✅ | ⚠️ tight | ~8-11 tokens/s |
| Pixel 9 Pro | 16GB | ✅ | ✅ | ~8-11 tokens/s |
| iPhone 17 Pro / Pro Max | 12GB | ✅ | ❌ (iOS per-app limit) | ~11 tokens/s (PrismML) |
| iPhone 16 Pro | 8GB | ⚠️ tight at 4K | ❌ | ~7-9 tokens/s |
| Galaxy S24 / most 8GB Androids | 8GB | ⚠️ limited headroom | ❌ | ~7-9 tokens/s |
| 6GB phones (iPhone 15, budget Android) | 6GB | ❌ | ❌ | — |
†Formula estimates from memory bandwidth; will be replaced with measured numbers as we test devices. PrismML's own figure for iPhone 17 Pro Max is ~11 tokens/s (1-bit).
How to run it
- Install or update PocketPal from the App Store or Google Play.
- In its model hub, open
prism-ml/Bonsai-27B-ggufand chooseBonsai-27B-Q1_0.gguf(3.8GB). - Start with 4K context, send a short prompt, then turn on airplane mode and ask again to confirm the reply is local.
The ternary Q2_0 figures on this page answer the hardware question only. Do not use that file in the PocketPal walkthrough; current phone releases do not support its tracked runtime format.
FAQ
Does Bonsai 27B beat a 7-8B model on a phone? PrismML's benchmarks say yes at ~90% of the full 27B — but 1-bit quantization quality is workload-dependent. For coding, compare against Qwen3 8B Q4 before committing to the 4GB download.
Can it see images? The family includes a vision tower, but image input needs an app-compatible projector path. The beginner Q1_0 walkthrough above covers text chat.
Why does it fit when Qwen3 32B doesn't? Bits per weight: a Q4 32B needs ~18GB; 1-bit 27B needs 3.8GB. Same class, 4-5× smaller footprint.
Estimates use our standard fit methodology; measured entries will be labeled separately as evidence arrives. Data sources: PrismML announcement and documentation, plus public repository file sizes (accessed 2026-07-17). Try the phone checker for a specific device.