Phi-4 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
P102-101
10 GB · IQ4_XS · 20.2 tok/s
Fastest card
B200
242 tok/s · 180 GB
Which GPUs can run Phi-4?
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.
306 cards match
Calculating| Needs | Quantisation | Fit | |||||
|---|---|---|---|---|---|---|---|
|
242
tok/s
145–387 · low confidence |
B200 NVIDIA | 180 GB | 8,000 GB/s | Jan 2024 | 15.7 GB | Q8_0 | Comfortable |
|
242
tok/s
145–387 · low confidence |
B300 NVIDIA | 288 GB | 8,000 GB/s | Sep 2025 | 15.7 GB | Q8_0 | Comfortable |
|
193
tok/s
116–309 · low confidence |
Radeon Instinct MI350X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 15.7 GB | Q8_0 | Comfortable |
|
193
tok/s
116–309 · low confidence |
Radeon Instinct MI355X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 15.7 GB | Q8_0 | Comfortable |
|
155
tok/s
93–247 · low confidence |
Radeon Instinct MI300 AMD | 128 GB | 6,550 GB/s | Jan 2023 | 15.7 GB | Q8_0 | Comfortable |
|
148
tok/s
89–237 · low confidence |
H200 NVL NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 15.7 GB | Q8_0 | Comfortable |
|
148
tok/s
89–237 · low confidence |
H200 SXM 141 GB NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 15.7 GB | Q8_0 | Comfortable |
|
142
tok/s
85–227 · low confidence |
Radeon Instinct MI325X AMD | 256 GB | 6,000 GB/s | Oct 2024 | 15.7 GB | Q8_0 | Comfortable |
|
126
tok/s
75–201 · low confidence |
Radeon Instinct MI300A AMD | 128 GB | 5,325 GB/s | Dec 2023 | 15.7 GB | Q8_0 | Comfortable |
|
126
tok/s
75–201 · low confidence |
Radeon Instinct MI300X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 15.7 GB | Q8_0 | Comfortable |
|
126
tok/s
75–201 · low confidence |
Radeon Instinct MI308X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 15.7 GB | Q8_0 | Comfortable |
|
119
tok/s
72–191 · low confidence |
H100 NVL 94 GB NVIDIA | 94 GB | 3,940 GB/s | Mar 2023 | 15.7 GB | Q8_0 | Comfortable |
|
116
tok/s
70–185 · low confidence |
CMP 170HX 10 GB NVIDIA | 10 GB | 1,560 GB/s | Sep 2021 | 8.4 GB | IQ4_XS | Tight |
|
102
tok/s
61–163 · low confidence |
H100 PCIe 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 15.7 GB | Q8_0 | Comfortable |
|
102
tok/s
61–163 · low confidence |
H100 SXM5 80 GB NVIDIA | 80 GB | 3,360 GB/s | Oct 2022 | 15.7 GB | Q8_0 | Comfortable |
|
102
tok/s
61–163 · low confidence |
H100 SXM5 94 GB NVIDIA | 94 GB | 3,360 GB/s | Mar 2023 | 15.7 GB | Q8_0 | Comfortable |
|
102
tok/s
61–163 · low confidence |
H100 SXM5 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 15.7 GB | Q8_0 | Comfortable |
|
102
tok/s
61–163 · low confidence |
H800 SXM5 NVIDIA | 80 GB | 3,360 GB/s | Mar 2023 | 15.7 GB | Q8_0 | Comfortable |
|
77.4
tok/s
46–124 · low confidence |
Radeon Instinct MI250 AMD | 128 GB | 3,280 GB/s | Nov 2021 | 15.7 GB | Q8_0 | Comfortable |
|
77.4
tok/s
46–124 · low confidence |
Radeon Instinct MI250X AMD | 128 GB | 3,280 GB/s | Nov 2021 | 15.7 GB | Q8_0 | Comfortable |
|
64.5
tok/s
39–103 · low confidence |
Data Center GPU Max 1550 Intel | 128 GB | 3,280 GB/s | Jan 2023 | 15.7 GB | Q8_0 | Comfortable |
|
63.1
tok/s
38–101 · low confidence |
Data Center GPU Max Subsystem Intel | 128 GB | 3,210 GB/s | Jan 2023 | 15.7 GB | Q8_0 | Comfortable |
|
61.7
tok/s
37–99 · low confidence |
A100 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Nov 2020 | 15.7 GB | Q8_0 | Comfortable |
|
61.7
tok/s
37–99 · low confidence |
A100X NVIDIA | 80 GB | 2,040 GB/s | Jun 2021 | 15.7 GB | Q8_0 | Comfortable |
|
61.7
tok/s
37–99 · low confidence |
A800 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Aug 2022 | 15.7 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 Research
- Organisation type
- Industry
- Country
- United States of America
- Published
- 12 December 2024
- Authors
- Marah Abdin, Jyoti Aneja, Harkirat Behl, Sébastien Bubeck, Ronen Eldan, Suriya Gunasekar, Michael Harrison, Russell J. Hewett, Mojan Javaheripi, Piero Kauffmann, James R. Lee, Yin Tat Lee, Yuanzhi Li, Weishung Liu, Caio C. T. Mendes, Anh Nguyen, Eric Price, Gustavo de Rosa, Olli Saarikivi, Adil Salim, Shital Shah, Xin Wang, Rachel Ward, Yue Wu, Dingli Yu, Cyril Zhang, Yi Zhang
What it does
The problem areas the model was built for. A model can carry several of each.
- Domain
- Language
- Task
- Language modeling/generation, Question answering, Code generation, Quantitative reasoning
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
- 14B
- Training data
- tokens
14B parameters, dense decoder-only Transformer model
"The model was pretrained for approximately 10T tokens using linear warm-up and decay schedules with peak learning rate of 0.0003, constant weight decay of 0.1, and global batch size of 5760. " Table 5: Web 15% 1.3T unique tokens 1.2 epochs Web rewrites 15% 290B unique tokens 5.2 epochs Synthetic 40% 290B unique tokens 13.8 epochs Code data 20% 820B unique tokens 2.4 epochs Acquired sources 10% 580B unique tokens 1.7 epochs
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
- 9.3 × 10²³ FLOP
- How it was established
- Operation counting,Hardware
6ND = 6* 14*10^9 parameters * 10*10^12 tokens = 8.4e+23 FLOP 989500000000000 FLOP / sec [assumed bf16 precision] * 1920 GPUs * 504 hours * 3600 sec / hour * 0.3 [assumed utilization] = 1.0341209e+24 FLOP geometric mean sqrt(8.4e+23 * 1.0341209e+24) = 9.3202015e+23
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 H100 SXM5 80GB
- Chips used
- 1,920
- Wall-clock time
- 504 hours (21 days)
- Power draw
- 2.6 MW
https://huggingface.co/microsoft/phi-4 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
"Phi-4 is currently available on Azure AI Foundry under a Microsoft Research License Agreement (MSRLA) and will be available on Hugging Face next week. " Hugging Face: MIT license https://huggingface.co/microsoft/phi-4
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 Technical Report
- Last updated
- 28 November 2025
The extremes
The ten fastest GPUs that run Phi-4
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 242 tok/s
- 02 B200 180 GB · 8,000 GB/s · Q8_0 242 tok/s
- 03 Radeon Instinct MI350X 288 GB · 8,190 GB/s · Q8_0 193 tok/s
- 04 Radeon Instinct MI355X 288 GB · 8,190 GB/s · Q8_0 193 tok/s
- 05 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q8_0 155 tok/s
- 06 H200 NVL 141 GB · 4,890 GB/s · Q8_0 148 tok/s
- 07 H200 SXM 141 GB 141 GB · 4,890 GB/s · Q8_0 148 tok/s
- 08 Radeon Instinct MI325X 256 GB · 6,000 GB/s · Q8_0 142 tok/s
- 09 Radeon Instinct MI300A 128 GB · 5,325 GB/s · Q8_0 126 tok/s
- 10 Radeon Instinct MI300X 192 GB · 5,325 GB/s · Q8_0 126 tok/s
The smallest GPUs that still run Phi-4
The cheapest route in, by memory capacity. A tight fit runs the model but leaves nothing spare for a longer conversation.
- 01 Arc B570 10 GB · needs 8.4 GB · IQ4_XS · tight 18.4 tok/s
- 02 Xbox Series X 6nm GPU 10 GB · needs 8.4 GB · IQ4_XS · tight 32.5 tok/s
- 03 Radeon RX 6750 GRE 10 GB 10 GB · needs 8.4 GB · IQ4_XS · tight 18.5 tok/s
- 04 CMP 170HX 10 GB 10 GB · needs 8.4 GB · IQ4_XS · tight 116 tok/s
- 05 CMP 90HX 10 GB · needs 8.4 GB · IQ4_XS · tight 56.5 tok/s
- 06 CMP 50HX 10 GB · needs 8.4 GB · IQ4_XS · tight 41.6 tok/s
- 07 Radeon RX 6700 10 GB · needs 8.4 GB · IQ4_XS · tight 18.5 tok/s
- 08 Radeon RX 6700M 10 GB · needs 8.4 GB · IQ4_XS · tight 18.5 tok/s
- 09 Xbox Series X GPU 10 GB · needs 8.4 GB · IQ4_XS · tight 32.5 tok/s
- 10 GeForce RTX 3080 10 GB · needs 8.4 GB · IQ4_XS · tight 56.5 tok/s
What the numbers mean
Hardware requirements in practice
Minimum card
P102-101
Memory needed
8.4 GB
Fastest
242 tok/s
Phi-4 is small enough at 14B parameters that hardware is rarely the obstacle — 306 of the cards we track can run it, including cards several years old.
The entry point is the P102-101: 10 GB of memory, IQ4_XS compression, roughly 20.2 tokens per second.
Top of the range is the B200, at roughly 242 tokens per second thanks to 8,000 GB/s of bandwidth.
Where it came from
Phi-4 was published by Microsoft Research, in United States of America, in December 2024. industry is the category the publisher falls under.
It works in Language, and is recorded as doing language modeling/generation, Question answering, Code generation, Quantitative reasoning.
The weights are published, so it can be downloaded and run on your own hardware indefinitely, offline, with no account attached. It is published under the microsoft organisation on Hugging Face.
Understanding the speeds
Across every card that can run it, the middle of the range is about 20.4 tokens per second, and 268 of them clear the ten tokens per second that roughly matches reading speed.
It is a dense model, so every parameter is read for every token produced. That makes speed track memory bandwidth almost exactly — a card with twice the bandwidth generates roughly twice as fast.
Its internal architecture is not on file, so memory is approximated from the parameter count and marked accordingly. Expect the real figure to differ, more so at long context.
How it was trained
Training it took roughly 9.3 × 10²³ FLOP of computation, on NVIDIA H100 SXM5 80GB — a measure of what producing the model cost, not of how fast it answers.
Step by step
How to choose a GPU for Phi-4
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 — around 8.4 GB at IQ4_XS. Capacity is the gate — a card either holds it or it does not.
-
02
Decide how long your conversations run
Set the context to what you will actually use. The cache grows with the conversation, and it is the usual reason Phi-4 stops fitting a card that seemed fine.
-
03
Decide how much compression you will accept
Compression is what makes Phi-4 fit smaller cards, at some cost in accuracy — IQ4_XS on the smallest card that fits. A minimum quality removes the ones that go too far.
-
04
Rank by throughput rather than spec sheet
Sort by speed to see how cards rank for Phi-4. It will not match a gaming ordering — generation is bound by memory bandwidth, which is why the B200 tops it at 242 tok/s.
-
05
Look at the headroom, not just the fit
Tight means Phi-4 loads and works, with no room to raise the context later. Comfortable means you can. The difference matters more than a few tokens per second.
-
06
Check the card from the other side
Every card name links to its own page, which runs the same calculation across the whole model catalogue. Worth a look before buying for Phi-4 alone — a card is usually bought for more than one model.
Answers
Phi-4 — common questions
How many parameters does Phi-4 have?
Phi-4 has 14B parameters. 14B parameters, 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?
Phi-4 was published by Microsoft Research, based in United States of America, categorised as industry.
When was Phi-4 released?
Phi-4 was published in December 2024. Capability per parameter has improved considerably since, so a newer model of the same size is often the better use of the same hardware.
What is Phi-4 used for?
Phi-4 works in Language, and is recorded as handling language modeling/generation, Question answering, Code generation, Quantitative reasoning. A model can carry several of each, so these are the areas it was built for rather than a limit on what it will attempt.
Where can I download Phi-4?
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?
Around 9.3 × 10²³ FLOP, on NVIDIA H100 SXM5 80GB. 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 if it does not fit in my GPU?
It can be split between the card and system memory, but Phi-4 generates painfully slowly that way — the nearest miss we calculate is short by 2.0 GB. Nothing on this page assumes offloading.
Would two GPUs run Phi-4 faster?
Capacity adds across cards; throughput does not. Since 306 of the cards we track already hold Phi-4 on their own, a second card is rarely the answer here.
Why does the quantisation differ between cards for Phi-4?
Because capacity varies, so does how hard Phi-4 has to be squeezed — 5 distinct levels appear in the table above. Set a minimum quality to compare at one.
How accurate are these Phi-4 speed estimates?
These are estimates with real error bars. The fastest result here, 145–387 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?
The smallest card in our catalogue that holds Phi-4 is the P102-101, with 10 GB of memory. It runs the model at IQ4_XS using about 8.4 GB, and produces roughly 20.2 tokens per second. 306 cards in total can run it.
How fast is Phi-4 on a GPU?
It depends on the card. The quickest we calculate is a B200 at about 242 tokens per second; the slowest that still runs it manages considerably less. Reading speed is around ten tokens per second, and 268 of the cards that can run Phi-4 clear that.
How much VRAM does Phi-4 need?
About 8.4 GB at IQ4_XS 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 on a 12 GB GPU?
Yes. A GeForce RTX 3080 Ti with 12 GB runs it at Q5_K_M, using about 10.8 GB and generating roughly 49.3 tokens per second — a tight fit.
Can I run Phi-4 on a 16 GB GPU?
Yes. A Tesla V100 SXM2 16 GB with 16 GB runs it at Q6_K, using about 12.4 GB and generating roughly 49.7 tokens per second — a tight fit.
Can I run Phi-4 on a 24 GB GPU?
Yes. A GeForce RTX 5090 D V2 with 24 GB runs it at Q8_0, using about 15.7 GB and generating roughly 40.5 tokens per second — a comfortable fit.
Is Phi-4 open source?
Its weights are published, so Phi-4 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.
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.