Can I run Phi-4 Reasoning Vision 15B?
Phi-4 Reasoning Vision 15B by Microsoft needs around 16 GB of RAM at the recommended 4-bit quantization (9.1 GB download). Your hardware is checked below — instantly, nothing leaves your browser. Expect roughly ~34 tok/s on a NVIDIA RTX 3060 12GB.
Reading your hardware signals…
Real-world notes
Phi-4 Reasoning Vision 15B is Microsoft's open-weight (MIT-licensed, so freely usable commercially) model built for vision and reasoning rather than general chat. It is a dense 15B-parameter model, which means the whole thing loads and runs on every token. At a 4-bit quant it lands around 9.1 GB, so you want a 12 GB card like an RTX 3060 to keep it fully on the GPU, and you need at least 16 GB of system RAM. Drop to a 2-bit build (about 6.3 GB) if you are squeezing onto tighter hardware, though quality suffers at that level.
In daily use it feels brisk on a 12 GB RTX 3060 at roughly 34 tokens per second at 4-bit, comfortable for reading speed, and a 24 GB RTX 4090 pushes that to around 94 tokens per second. On an Apple M-series Max you can expect about 38 tokens per second. The context window is 16K, which is modest, so treat it as a working scratchpad rather than a place to dump whole documents. Even at 8K of context the full memory footprint climbs to roughly 10.5 GB, so leave headroom on a 12 GB card.
Positioned against its siblings, Phi-4 14B and Qwen 3 14B are the picks if you want a general chat-and-reasoning model, since this build trades some of that breadth for image understanding. Phi-4 Mini 3.8B is the lighter option when memory is tight. The standout trait here is that you get genuine multimodal reasoning at a footprint that still fits a single mid-range GPU, and the MIT license means no commercial restrictions to worry about.
Specifications
Size by quantization
| Quantization | Bits/weight | Download | Min RAM | Quality |
|---|---|---|---|---|
| Q2_K | 3.35 | 6.3 GB | 12 GB | Noticeable loss |
| Q4_K_MRecommended | 4.85 | 9.1 GB | 16 GB | Recommended |
| Q5_K_M | 5.65 | 10.6 GB | 16 GB | High |
| Q8_0 | 8.5 | 15.9 GB | 24 GB | Near-original |
| F16 | 16 | 30.0 GB | 48 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.7 GB | ~9.8 GB |
| 8K tokens | ~1.4 GB | ~10.5 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 | ~34 tok/s |
| NVIDIA RTX 4090 24GB | 1008 GB/s | ~94 tok/s |
| Apple M-series (base) | 100 GB/s | ~9 tok/s |
| Apple M-series Pro | 270 GB/s | ~25 tok/s |
| Apple M-series Max | 410 GB/s | ~38 tok/s |
| CPU only (dual-channel DDR5) | 60 GB/s | ~6 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.