Phi-4 Mini 3.8B
By Microsoft · United States
Updated 2026-07-13
Overview
Microsoft's 3.8B Phi-4 Mini under MIT with native function calling, 128k context via LongRoPE, and a 200k vocab. MMLU 67.3 and HumanEval 74.4.
When to pick this model
- Tool-using agents on minimal hardware
- On-device assistants requiring function calls
- MIT-licensed embedded deployments
- Long-context document tasks in a small model
VRAM requirements by quantization
| Quantization | VRAM required |
|---|---|
| Q4_K_M (recommended) | 10 GB |
| Q5_K_M | 12 GB |
| Q8_0 | 18 GB |
| FP16 (no quantization) | 33 GB |
VRAM figures include model weights plus a typical 8k KV cache and ~600 MB runtime overhead (Ollama / llama.cpp baseline). Add headroom for higher context lengths.
In practice, Phi-4 Mini 3.8B needs a 12 GB card at Q4_K_M (10 GB). Stepping up to Q8_0 nearly doubles the footprint to 18 GB, and unquantized FP16 weights take 33 GB — plan your GPU around the Q4 or Q5 figure unless you specifically need the higher fidelity.
Without a GPU, Phi-4 Mini 3.8B needs roughly 12 GB of system RAM to run on CPU via llama.cpp or Ollama — workable for background jobs, but far slower than GPU inference. Throughput estimates from our compatibility engine: around 14 tokens/sec on entry-level GPUs, on the order of 40 tokens/sec on a mid-range card, and up to 100 tokens/sec on high-end hardware — assuming the chosen quantization fully fits in VRAM.
What hardware do you need
The table below matches Phi-4 Mini 3.8B to common GPU memory tiers, using the highest-fidelity quantization that fully fits each card class. Spilling layers to system RAM works but costs most of the speed, so size your card to the quantization you actually want to run.
| GPU memory | Example cards | Best fit for Phi-4 Mini 3.8B |
|---|---|---|
| 8 GB | RTX 5070 Laptop, RTX 5060, RTX 5060 Ti 8GB | Does not fit — needs 10 GB at Q4_K_M |
| 12 GB | RTX 5070, RTX 5070 Ti Laptop, RTX 4080 Laptop | Q5_K_M (12 GB used) |
| 16 GB | RTX 5080, RTX 4080 Super, Radeon RX 9070 XT | Q5_K_M (12 GB used) |
| 24 GB | RTX 4090, Radeon RX 7900 XTX, RTX 5090 Laptop | Q8_0 (18 GB used) |
| 32 GB | RTX 5090 | Q8_0 (18 GB used) |
Which GPU should you buy to run Phi-4 Mini 3.8B?
To run Phi-4 Mini 3.8B locally at Q4, you need ~10 GB of VRAM. The best value for this is a RTX 5070 (12 GB VRAM).
As an Amazon Associate, BestLLMfor earns from qualifying purchases, at no extra cost to you. It does not influence our independent rankings.
Published benchmark scores
| Benchmark | Score |
|---|---|
| MMLU | 67.3 |
| HumanEval | 74.4 |
| MATH | 71.5 |
Scores published by the model author or aggregated from public leaderboards. Re-measured monthly by our editorial team.
To put Phi-4 Mini 3.8B in context: its MMLU score of 67.3 ranks #25 of the 34 catalog models with a published MMLU result (catalog median 73.4); its HumanEval score of 74.4 ranks #17 of the 26 catalog models with a published HumanEval result (catalog median 81.1). Scores are author-published and measured under different harnesses, so treat gaps of a few points as noise rather than a verdict.
Strengths
- Native function calling at 3.8B
- 128k context via LongRoPE
- MIT license
- 200k vocabulary improves tokenization efficiency
Limitations
- English-first — multilingual coverage is thin
- Outscored on raw quality by Qwen 2.5 3B
- Tool-calling reliability still trails larger models
Typical workloads
In our catalog grid, Phi-4 Mini 3.8B is filed under Laptop Assistant, Tool calling — the use cases where its size/quality trade-off makes the most sense. Its tags translate to concrete workloads: everyday chat, drafting and summarization.
The 125k-token context window covers long chats and mid-sized documents, though very large retrieval workloads will need chunking. The MIT license is permissive, so shipping it inside a commercial product raises no special legal questions.
Architecture & training
Architecture: Dense 3.8B · GQA · LongRoPE · shared embeddings · 200k vocab
Training: High-quality Phi corpus.
The MIT-licensed pick for small tool-using agents — strong function calling and 128k context in a 3.8B footprint.
Quick start
ollama run phi4-mini:3.8bOr use the open-source MCP server to query this model from Claude Desktop, Cursor, or any MCP-compatible client.
Similar models worth comparing
Frequently asked questions
How much VRAM does Phi-4 Mini 3.8B need?
At the recommended Q4_K_M quantization, Phi-4 Mini 3.8B needs about 10 GB of VRAM. Q8_0 takes 18 GB, and unquantized FP16 weights take 33 GB.
Can Phi-4 Mini 3.8B run without a GPU?
Yes — with roughly 12 GB of system RAM it runs CPU-only through llama.cpp or Ollama. Expect a fraction of GPU speed, which is fine for background or batch jobs but slow for interactive chat.
What context window does Phi-4 Mini 3.8B support?
Phi-4 Mini 3.8B supports a 125k-token context window (128,000 tokens).
Can I use Phi-4 Mini 3.8B commercially?
Yes. Phi-4 Mini 3.8B is released under MIT, a permissive open-source license that allows commercial use, modification and redistribution.
How fast is Phi-4 Mini 3.8B on consumer hardware?
Our compatibility engine estimates on the order of 40 tokens/sec on a mid-range GPU and up to 100 tokens/sec on high-end cards, assuming the quantization fully fits in VRAM.
Which quantization of Phi-4 Mini 3.8B should I download first?
Start with Q4_K_M (10 GB) — the standard size/quality sweet spot. Step up to Q5_K_M or Q8_0 only if you have VRAM headroom. On a 24 GB card you can run up to Q8_0.