What GPU do I need to run microsoft/phi-4?
14.7B parameters, published in BF16. View on Hugging Face
phi-4 is published by microsoft on Hugging Face, with 632,240 downloads and 2,293 likes to date. It's a Phi3ForCausalLM model built for text-generation, published natively in BF16.
VRAM required & cheapest live GPU fit
Required VRAM = weight size at each precision, plus a fixed overhead for KV-cache, activations, and fragmentation. Full formula and assumptions: methodology.
A GPU is only matched to a row if its hardware supports that precision, and the primary recommendation is always a single-GPU fit when one exists.
INT4 requires a quantized checkpoint actually published for this model, check its Hugging Face page before relying on this row.
Cheapest way to run phi-4 at its published (BF16) precision: 1× RTX A6000 on runpod, at $0.330/hr per GPU ($0.330/hr total). Quantizing to FP8 or INT4 (rows above) can cost less, but requires a compatible quantized checkpoint to exist for this model.
phi-4: common questions
Can phi-4 run on a single GPU?
Yes, but not on a desktop card. At BF16 it needs 32.8 GB of VRAM, more than a single 32 GB desktop card holds. The cheapest live single-card fit is a 48.0 GB RTX A6000 on runpod at $0.330/hr.
What is the least VRAM phi-4 can run in?
8.2 GB, at INT4 (quantized), which fits a 12 GB card, against 32.8 GB at BF16. That row assumes an INT4 checkpoint has actually been published for this model, so check its Hugging Face page before planning around it.
Does quantizing phi-4 lower the GPU bill?
Yes. At BF16 the cheapest live fit is one RTX A6000 on runpod at $0.330/hr. At INT4 (quantized) it drops to one RTX 3080 on simplepod at $0.070/hr, provided a quantized checkpoint exists for it.
Weight-to-VRAM math, the fit rules, and how live prices are normalized: full methodology.
More microsoft models
- Florence-2-base (232M, F16)
- phi-2 (2.8B, F16)
- VibeVoice-ASR (8.7B, BF16)
- Phi-3.5-vision-instruct (4.1B, BF16)
- Florence-2-large (777M, F16)
- Phi-3-mini-4k-instruct (3.8B, BF16)