text model · DeepSeek-R1-Distill · Android
Can I run DeepSeek-R1-Distill-Qwen 14B on Samsung Galaxy S26 Ultra (16GB, 1TB config)?
Yes. DeepSeek-R1-Distill-Qwen 14B runs on Samsung Galaxy S26 Ultra (16GB, 1TB config) at Q4_K_M (~10.7 GB of ~12 GB usable).
Runs at Q4_K_M using ~10.7 GB of ~12 GB usable.
- Q4_K_M needed
- ~10.7 GB
- Usable on device
- ~12 GB
- Device memory
- 16 GB
- Best quant
- Q4_K_M
How to run it
On Android use PocketPal AI (Polished app, download GGUF and run offline.). NPU acceleration is limited and chip-specific; most apps run on CPU. Expect 1B-4B class.
- Parameters
- 14B
- Q4_K_M size
- 8.99 GB
- Q8_0 size
- 15.7 GB
- Context
- 128k
- Ollama tag
- deepseek-r1:14b
- Memory
- 16 GB ram
- Usable for weights
- ~12 GB
- Best runtime
- llama.cpp (PocketPal) or MLC-LLM (Adreno GPU path)
You could also run
Run DeepSeek-R1-Distill-Qwen 14B on other hardware
FAQ
Can Samsung Galaxy S26 Ultra (16GB, 1TB config) run DeepSeek-R1-Distill-Qwen 14B?
Yes. DeepSeek-R1-Distill-Qwen 14B runs on Samsung Galaxy S26 Ultra (16GB, 1TB config) at Q4_K_M (~10.7 GB of ~12 GB usable).
How much memory does DeepSeek-R1-Distill-Qwen 14B need?
Samsung Galaxy S26 Ultra (16GB, 1TB config) has room to spare. At Q4_K_M the weights are ~8.99 GB; with KV cache and runtime overhead, budget ~10.7 GB at a 4k context.
What is the best tool to run DeepSeek-R1-Distill-Qwen 14B on Android?
On Android, PocketPal AI (Polished app, download GGUF and run offline.) is the go-to option. NPU acceleration is limited and chip-specific; most apps run on CPU. Expect 1B-4B class.
Sources
Memory figures are estimates. See methodology.