Can I run Phi-4 Mini 3.8B?
Phi-4 Mini 3.8B by Microsoft needs around 6 GB of RAM at the recommended 4-bit quantization (2.3 GB download). Your hardware is checked below — instantly, nothing leaves your browser. Expect roughly ~133 tok/s on a NVIDIA RTX 3060 12GB.
Reading your hardware signals…
Real-world notes
Phi-4 Mini 3.8B is Microsoft's small chat model, the one to reach for when you want something genuinely lightweight that still holds a conversation. At a 4-bit quant it lands around 2.3 GB, dropping to roughly 1.6 GB at 2-bit, so it fits almost anywhere: a 6 GB GPU has room to spare, an entry M1 Mac runs it without thinking, and an old laptop on CPU can handle it. The MIT license is the easy part, no terms to read and no commercial restrictions, so you can ship it in a product freely.
In daily use it is quick. On an RTX 3060 you'll see about 133 tok/s, an M-series Max sits near 151 tok/s, and a 4090 pushes it past 370 tok/s, which is faster than you can read by a wide margin. The 128K context is the headline number but treat it with caution: fill it and total memory climbs to about 14.3 GB, far past the 6 GB this model needs at rest. On a small GPU keep working context to a few thousand tokens and you will stay comfortable. Even CPU on DDR5 manages around 22 tok/s for short prompts.
Where it shows its size is depth. For reasoning and multi-step instructions, Qwen 3 4B generally has the edge despite being roughly the same parameter count, and if you need real reasoning headroom Phi-4 14B is the obvious step up. Phi-4 Mini's standout trait is efficiency: it punches above its 3.8B for plain chat and summarisation while staying small enough to run almost anywhere, MIT-licensed and unrestricted. If you want a tiny local assistant that loads fast and gets out of your way, this is a strong default.
Specifications
Size by quantization
| Quantization | Bits/weight | Download | Min RAM | Quality |
|---|---|---|---|---|
| Q2_K | 3.35 | 1.6 GB | 4 GB | Noticeable loss |
| Q4_K_MRecommended | 4.85 | 2.3 GB | 6 GB | Recommended |
| Q5_K_M | 5.65 | 2.7 GB | 6 GB | High |
| Q8_0 | 8.5 | 4.0 GB | 8 GB | Near-original |
| F16 | 16 | 7.6 GB | 12 GB | Original |
Sizes are estimates from parameter count × bits per weight; real GGUF builds vary slightly. · Data updated: 2026-06-11 · How we calculate these numbers →
Memory needed by context length
| Context | KV cache (est.) | Total memory (Q4) |
|---|---|---|
| 4K tokens | ~0.4 GB | ~2.7 GB |
| 8K tokens | ~0.8 GB | ~3.1 GB |
| 32K tokens | ~3.0 GB | ~5.3 GB |
| 128K tokens | ~12.0 GB | ~14.3 GB |
The KV cache grows with context length — a model that fits at 4K can run out of memory at 32K. Estimates assume an FP16 cache with grouped-query attention; actual usage varies by runtime.
Estimated speed by hardware
| Hardware | Bandwidth | ~Speed |
|---|---|---|
| NVIDIA RTX 3060 12GB | 360 GB/s | ~133 tok/s |
| NVIDIA RTX 4090 24GB | 1008 GB/s | ~372 tok/s |
| Apple M-series (base) | 100 GB/s | ~37 tok/s |
| Apple M-series Pro | 270 GB/s | ~100 tok/s |
| Apple M-series Max | 410 GB/s | ~151 tok/s |
| CPU only (dual-channel DDR5) | 60 GB/s | ~22 tok/s |
Token generation is memory-bandwidth bound: tok/s ≈ bandwidth × 0.85 ÷ model size at Q4. Real-world numbers vary by runtime and context length.
Run it locally
The easiest path is Ollama — one command and you're chatting:
ollama run phi4-miniSources & downloads
Ollama Library
Pull and run the model with a single command.
ollama.comHugging Face
Model weights, files and license details.
huggingface.coOfficial GitHub repo
Source code, releases and issues from Microsoft.
github.comMicrosoft — official page
Official page and documentation from Microsoft.
azure.microsoft.com