text model · Mistral · Android
Can I run Magistral Small on Google Pixel 10 Pro?
No. Magistral Small needs ~16 GB even at Q4_K_M, but Google Pixel 10 Pro only has ~10.5 GB usable.
Needs ~16 GB even at Q4_K_M, but only ~10.5 GB is usable.
That figure is at a 4k context and moves about ±15% as context length changes.
The gap is about 5.5 GB: Magistral Small needs roughly 16 GB at Q4_K_M and Google Pixel 10 Pro leaves only about 10.5 GB usable for a model. The lightest tracked hardware that runs Magistral Small is the Apple M4 (24GB) at 24 GB. See Magistral Small on Apple M4 (24GB).
- Q4_K_M needed
- ~16 GB
- Usable on device
- ~10.5 GB
- Device memory
- 16 GB
Which quant fits
How to run it
On Android use PocketPal AI (Polished app, download GGUF and run offline.).
- Parameters
- 24B
- Q4_K_M size
- 14 GB
- Q8_0 size
- 25 GB
- Context
- 40k
- Ollama tag
- magistral:24b
- Memory
- 16 GB ram
- Usable for weights
- ~10.5 GB
- Power draw
- ~7 W
- Best runtime
- llama.cpp (PocketPal) or MLC-LLM (Adreno GPU path)
What you can run instead
Run Magistral Small on other hardware
FAQ
Can Google Pixel 10 Pro run Magistral Small?
No. Magistral Small needs ~16 GB even at Q4_K_M, but Google Pixel 10 Pro only has ~10.5 GB usable.
How much memory does Magistral Small need?
Google Pixel 10 Pro does not have enough memory. At Q4_K_M the weights are ~14 GB; with KV cache and runtime overhead, budget ~16 GB at a 4k context.
What is the best tool to run Magistral Small 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.
Embed this
A live badge for your model card or README, updated as the data is. [](https://localmodel.run/can-i-run/magistral-small/pixel-10-pro) Sources
Weights are measured from GGUF files; KV cache and overhead are computed, so totals can vary ~15% with context and runtime. Any tok/s is a bandwidth estimate. See methodology.