Phi-4 Mini TPS calculator
Each card below is assessed against this model at the context length and minimum quality you choose. Speed is an estimate for a single request, calculated from the card's memory bandwidth and the size of the model once compressed.
Calculated for this model
818 cards we hold specifications for
Smallest card that fits
Tesla C1080
4 GB · Q5_K_M · 17.3 tok/s
Fastest card
B200
892 tok/s · 180 GB
Which GPUs can run Phi-4 Mini?
Set the inputs, read the answer
A longer conversation needs more memory, which can push this model off smaller cards.
Hides cards that would only fit the model by compressing it below this point.
818 cards match
Calculating| Needs | Quantisation | Fit | |||||
|---|---|---|---|---|---|---|---|
|
892
tok/s
535–1,427 · low confidence |
B200 NVIDIA | 180 GB | 8,000 GB/s | Jan 2024 | 4.8 GB | Q8_0 | Comfortable |
|
892
tok/s
535–1,427 · low confidence |
B300 NVIDIA | 288 GB | 8,000 GB/s | Sep 2025 | 4.8 GB | Q8_0 | Comfortable |
|
712
tok/s
427–1,139 · low confidence |
Radeon Instinct MI350X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 4.8 GB | Q8_0 | Comfortable |
|
712
tok/s
427–1,139 · low confidence |
Radeon Instinct MI355X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 4.8 GB | Q8_0 | Comfortable |
|
569
tok/s
342–911 · low confidence |
Radeon Instinct MI300 AMD | 128 GB | 6,550 GB/s | Jan 2023 | 4.8 GB | Q8_0 | Comfortable |
|
545
tok/s
327–872 · low confidence |
H200 NVL NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 4.8 GB | Q8_0 | Comfortable |
|
545
tok/s
327–872 · low confidence |
H200 SXM 141 GB NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 4.8 GB | Q8_0 | Comfortable |
|
522
tok/s
313–835 · low confidence |
Radeon Instinct MI325X AMD | 256 GB | 6,000 GB/s | Oct 2024 | 4.8 GB | Q8_0 | Comfortable |
|
463
tok/s
278–741 · low confidence |
Radeon Instinct MI300A AMD | 128 GB | 5,325 GB/s | Dec 2023 | 4.8 GB | Q8_0 | Comfortable |
|
463
tok/s
278–741 · low confidence |
Radeon Instinct MI300X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 4.8 GB | Q8_0 | Comfortable |
|
463
tok/s
278–741 · low confidence |
Radeon Instinct MI308X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 4.8 GB | Q8_0 | Comfortable |
|
439
tok/s
263–703 · low confidence |
H100 NVL 94 GB NVIDIA | 94 GB | 3,940 GB/s | Mar 2023 | 4.8 GB | Q8_0 | Comfortable |
|
374
tok/s
225–599 · low confidence |
H100 PCIe 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 4.8 GB | Q8_0 | Comfortable |
|
374
tok/s
225–599 · low confidence |
H100 SXM5 80 GB NVIDIA | 80 GB | 3,360 GB/s | Oct 2022 | 4.8 GB | Q8_0 | Comfortable |
|
374
tok/s
225–599 · low confidence |
H100 SXM5 94 GB NVIDIA | 94 GB | 3,360 GB/s | Mar 2023 | 4.8 GB | Q8_0 | Comfortable |
|
374
tok/s
225–599 · low confidence |
H100 SXM5 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 4.8 GB | Q8_0 | Comfortable |
|
374
tok/s
225–599 · low confidence |
H800 SXM5 NVIDIA | 80 GB | 3,360 GB/s | Mar 2023 | 4.8 GB | Q8_0 | Comfortable |
|
285
tok/s
171–456 · low confidence |
Radeon Instinct MI250 AMD | 128 GB | 3,280 GB/s | Nov 2021 | 4.8 GB | Q8_0 | Comfortable |
|
285
tok/s
171–456 · low confidence |
Radeon Instinct MI250X AMD | 128 GB | 3,280 GB/s | Nov 2021 | 4.8 GB | Q8_0 | Comfortable |
|
238
tok/s
143–380 · low confidence |
Data Center GPU Max 1550 Intel | 128 GB | 3,280 GB/s | Jan 2023 | 4.8 GB | Q8_0 | Comfortable |
|
233
tok/s
140–372 · low confidence |
Data Center GPU Max Subsystem Intel | 128 GB | 3,210 GB/s | Jan 2023 | 4.8 GB | Q8_0 | Comfortable |
|
227
tok/s
136–364 · low confidence |
A100 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Nov 2020 | 4.8 GB | Q8_0 | Comfortable |
|
227
tok/s
136–364 · low confidence |
A100X NVIDIA | 80 GB | 2,040 GB/s | Jun 2021 | 4.8 GB | Q8_0 | Comfortable |
|
227
tok/s
136–364 · low confidence |
A800 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Aug 2022 | 4.8 GB | Q8_0 | Comfortable |
|
227
tok/s
136–364 · low confidence |
H100 CNX NVIDIA | 80 GB | 2,040 GB/s | Mar 2023 | 4.8 GB | Q8_0 | Comfortable |
Speeds are estimates for a single request — one conversation at a time — calculated from memory bandwidth, model size and quantisation. Real throughput varies with the inference runtime and its version. Figures published by hardware vendors measure many simultaneous requests and are much higher.
On record
Full specification
Everything on record for this model. Most of it describes how it was trained rather than how it runs — useful context for judging how much work went into it, and how it compares with models built at a different scale.
Origin
Who built this model, where, and when it was published.
- Organisation
- Microsoft
- Organisation type
- Industry
- Country
- United States of America
- Published
- 3 March 2025
- Authors
- Abdelrahman Abouelenin, Atabak Ashfaq, Adam Atkinson, Hany Awadalla, Nguyen Bach, Jianmin Bao, Alon Benhaim, Martin Cai, Vishrav Chaudhary, Congcong Chen, Dong Chen, Dongdong Chen, Junkun Chen, Weizhu Chen, Yen-Chun Chen, Yi-ling Chen, Qi Dai, Xiyang Dai, Ruchao Fan, Mei Gao, Min Gao, Amit Garg, Abhishek Goswami, Junheng Hao, Amr Hendy, Yuxuan Hu, Xin Jin, Mahmoud Khademi, Dongwoo Kim, Young Jin K…
What it does
The problem areas the model was built for. A model can carry several of each.
- Domain
- Language
- Task
- Language modeling/generation, Visual question answering, Code generation, Quantitative reasoning, Translation
Size
How large the model is and how much data it was trained on. Parameters are the figure that decides whether it fits on a given graphics card.
- Parameters
- 3.8B
- Training data
- 5,000,000,000,000 tokens
3.8-billion dense decoder-only Transformer model
"With these techniques, we built the 5 trillion pre-training data corpus"
Training compute
The arithmetic performed to train the model, measured in floating-point operations. It is a measure of what the training run cost, not of how fast the finished model answers you.
- Training compute
- 10 × 10²² FLOP
- How it was established
- Operation counting,Hardware
6ND = 6 FLOP / token / parameter * 3800000000 parameters * 5000000000000 tokens = 1.14e+23 FLOP 512 GPUs * 312000000000000 FLOP / sec * 504 hours * 3600 sec / hour * 0.3 [assumed utilization] = 8.6951854e+22 FLOP geometric mean: sqrt(1.14e+23*8.6951854e+22) = 9.9561596e+22
The training run
What it physically took to train: which chips, how many, for how long, and what that drew from the wall.
- Training hardware
- NVIDIA A100 SXM4 80 GB
- Chips used
- 512
- Wall-clock time
- 504 hours (21 days)
- Power draw
- 402.0 kW
21 days * 24 hours / day = 504 hours
Availability
Whether you can obtain the model and run it on your own hardware, which is what decides if any of the graphics-card figures on this page apply.
- Weights
- Open — downloadable
- Model access
- Open weights (unrestricted)
- Training code
- Unreleased
- Hugging Face
- microsoft
the instruct model is under MIT license on hugging face https://huggingface.co/microsoft/Phi-4-mini-instruct
How it is classified
Labels the source dataset applies when tracking notable models, and how confident it is in the entry.
- Likely above 10²³ FLOP
- Yes
- Record confidence
- Confident
Sources
Where this record came from and when it was last checked.
- Reference
- Phi-4-Mini Technical Report: Compact yet Powerful Multimodal Language Models via Mixture-of-LoRAs
- Last updated
- 28 November 2025
The extremes
The ten fastest GPUs that run Phi-4 Mini
Ranked by estimated tokens per second, newest card first where speeds tie. Because generation is bound by memory bandwidth, this ordering follows bandwidth rather than any gaming benchmark.
- 01 B300 288 GB · 8,000 GB/s · Q8_0 892 tok/s
- 02 B200 180 GB · 8,000 GB/s · Q8_0 892 tok/s
- 03 Radeon Instinct MI350X 288 GB · 8,190 GB/s · Q8_0 712 tok/s
- 04 Radeon Instinct MI355X 288 GB · 8,190 GB/s · Q8_0 712 tok/s
- 05 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q8_0 569 tok/s
- 06 H200 NVL 141 GB · 4,890 GB/s · Q8_0 545 tok/s
- 07 H200 SXM 141 GB 141 GB · 4,890 GB/s · Q8_0 545 tok/s
- 08 Radeon Instinct MI325X 256 GB · 6,000 GB/s · Q8_0 522 tok/s
- 09 Radeon Instinct MI300A 128 GB · 5,325 GB/s · Q8_0 463 tok/s
- 10 Radeon Instinct MI300X 192 GB · 5,325 GB/s · Q8_0 463 tok/s
The smallest GPUs that still run Phi-4 Mini
The cheapest route in, by memory capacity. A tight fit runs the model but leaves nothing spare for a longer conversation.
- 01 GeForce RTX 4010 4 GB · needs 3.4 GB · Q5_K_M · tight 19.1 tok/s
- 02 RTX A400 4 GB · needs 3.4 GB · Q5_K_M · tight 19.1 tok/s
- 03 RTX 500 Mobile Ada Generation 4 GB · needs 3.4 GB · Q5_K_M · tight 25.5 tok/s
- 04 GeForce RTX 3050 A Mobile 4 GB · needs 3.4 GB · Q5_K_M · tight 38.2 tok/s
- 05 Jetson Orin Nano 4 GB 4 GB · needs 3.4 GB · Q5_K_M · tight 6.8 tok/s
- 06 Radeon RX 6450M 4 GB · needs 3.4 GB · Q5_K_M · tight 19.9 tok/s
- 07 Radeon RX 6550M 4 GB · needs 3.4 GB · Q5_K_M · tight 22.4 tok/s
- 08 Radeon RX 6550S 4 GB · needs 3.4 GB · Q5_K_M · tight 19.9 tok/s
- 09 Arc A310 4 GB · needs 3.4 GB · Q5_K_M · tight 16.0 tok/s
- 10 Arc Pro A30M 4 GB · needs 3.4 GB · Q5_K_M · tight 16.6 tok/s
What the numbers mean
What you need to run it
Minimum card
Tesla C1080
Memory needed
3.4 GB
Fastest
892 tok/s
Phi-4 Mini is small enough at 3.8B parameters that hardware is rarely the obstacle — 818 of the cards we track can run it, including cards several years old.
The least hardware that works is a Tesla C1080. Its 4 GB is enough at Q5_K_M compression, giving roughly 17.3 tokens per second.
At the other end, a B200 generates roughly 892 tokens per second on it, on the strength of 8,000 GB/s of memory bandwidth.
Background
Phi-4 Mini was published by Microsoft, in United States of America, in March 2025. It comes out of industry.
It works in Language, and is recorded as doing language modeling/generation, Visual question answering, Code generation, Quantitative reasoning, Translation.
Published weights mean the model runs on your machine rather than someone else's, which is what makes the hardware question below answerable at all. It is published under the microsoft organisation on Hugging Face.
Reading the throughput figures
Half the cards that hold it manage more than 29.9 tokens per second, and 777 exceed reading speed outright.
Being dense, it reads all of itself per token, which is why the ordering by speed below follows the ordering by memory bandwidth so closely.
Memory here is estimated from size rather than computed from the architecture, which is not recorded for this model — the numbers are indicative rather than exact.
How it was trained
Producing it required around 10 × 10²² FLOP of arithmetic, on NVIDIA A100 SXM4 80 GB, which is a statement about the training budget rather than about inference.
It was trained on about 5,000,000,000,000 tokens of text.
Step by step
How to choose a GPU for Phi-4 Mini
The table above has already assessed every card we hold specifications for against this model. Getting to your answer takes six steps.
-
01
Read the memory figure first
Every card here has been checked against Phi-4 Mini — around 3.4 GB at Q5_K_M. Capacity is the gate — a card either holds it or it does not.
-
02
Decide how long your conversations run
Longer conversations cost memory on top of what the weights need. Move the slider to your real working length before trusting any row for Phi-4 Mini.
-
03
Choose how far you will compress it
Compression is what makes Phi-4 Mini fit smaller cards, at some cost in accuracy — Q5_K_M on the smallest card that fits. A minimum quality removes the ones that go too far.
-
04
Compare tokens per second, not specifications
Sort by speed to see how cards rank for Phi-4 Mini. It will not match a gaming ordering — generation is bound by memory bandwidth, which is why the B200 tops it at 892 tok/s.
-
05
Check the fit verdict before buying
The fit column separates cards that just manage Phi-4 Mini from those with room to spare. Buy for the second if the context might grow.
-
06
See what else that card runs
Following a card through to its own page shows every other model it can hold, which is the question that follows once Phi-4 Mini is settled.
Answers
Phi-4 Mini — common questions
How much VRAM does Phi-4 Mini need?
About 3.4 GB at Q5_K_M compression, which is what the smallest card that runs it uses. Less compression needs more: the figures in the memory column above are recalculated for each card, because each one holds the least-compressed version it can.
Can I run Phi-4 Mini on a 8 GB GPU?
Yes. A CMP 170HX 8 GB with 8 GB runs it at Q8_0, using about 4.8 GB and generating roughly 166 tokens per second — a comfortable fit.
Can I run Phi-4 Mini on a 12 GB GPU?
Yes. A GeForce RTX 3080 Ti with 12 GB runs it at Q8_0, using about 4.8 GB and generating roughly 102 tokens per second — a comfortable fit.
Can I run Phi-4 Mini on a 16 GB GPU?
Yes. A Tesla V100 SXM2 16 GB with 16 GB runs it at Q8_0, using about 4.8 GB and generating roughly 126 tokens per second — a comfortable fit.
Can I run Phi-4 Mini on a 24 GB GPU?
Yes. A GeForce RTX 5090 D V2 with 24 GB runs it at Q8_0, using about 4.8 GB and generating roughly 149 tokens per second — a comfortable fit.
Is Phi-4 Mini open source?
Its weights are published, so Phi-4 Mini can be downloaded and run on your own hardware. Note that open weights is not the same as open source in the full sense — it says nothing about the training data, the training code, or the commercial terms attached.
How many parameters does Phi-4 Mini have?
Phi-4 Mini has 3.8B parameters. 3.8-billion dense decoder-only Transformer model. That figure is the total, and it is what decides how much memory the model needs — roughly half a gigabyte per billion at the compression most people use.
Who created Phi-4 Mini?
Phi-4 Mini was published by Microsoft, based in United States of America, categorised as industry.
When was Phi-4 Mini released?
Phi-4 Mini was published in March 2025.
What is Phi-4 Mini used for?
Phi-4 Mini works in Language, and is recorded as handling language modeling/generation, Visual question answering, Code generation, Quantitative reasoning, Translation. Models frequently carry more than one of each, and the tags describe purpose rather than capability limits.
Where can I download Phi-4 Mini?
Its weights are published under the microsoft organisation on Hugging Face. We do not host model files — this site calculates what hardware is needed to run them.
How much compute was used to train Phi-4 Mini?
Around 10 × 10²² FLOP, on NVIDIA A100 SXM4 80 GB. That measures what producing the model cost and says nothing about how quickly it answers once trained — inference speed comes from memory bandwidth, not from the training budget.
Can I run Phi-4 Mini if it does not fit in my GPU?
Partly. Layers that do not fit sit in system memory and run at a fraction of the speed, so a mostly-offloaded Phi-4 Mini is rarely worth using. Every figure here assumes the whole model is on the card.
Would two GPUs run Phi-4 Mini faster?
Capacity adds across cards; throughput does not. Since 818 of the cards we track already hold Phi-4 Mini on their own, a second card is rarely the answer here.
Why does the quantisation differ between cards for Phi-4 Mini?
Because capacity varies, so does how hard Phi-4 Mini has to be squeezed — 3 distinct levels appear in the table above. Set a minimum quality to compare at one.
How accurate are these Phi-4 Mini speed estimates?
These are estimates with real error bars. The fastest result here, 535–1,427 tok/s on the B200, could reasonably land anywhere in its published range depending on which runtime you use.
What GPU do I need to run Phi-4 Mini?
The smallest card in our catalogue that holds Phi-4 Mini is the Tesla C1080, with 4 GB of memory. It runs the model at Q5_K_M using about 3.4 GB, and produces roughly 17.3 tokens per second. 818 cards in total can run it.
How fast is Phi-4 Mini on a GPU?
It depends on the card. The quickest we calculate is a B200 at about 892 tokens per second; the slowest that still runs it manages considerably less. Reading speed is around ten tokens per second, and 777 of the cards that can run Phi-4 Mini clear that.
The other direction
Looking at it from the other side?
This page starts from the model. If you already own a card and want to know everything it will run, start from the hardware instead.