Llama 4 Scout 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
Radeon Instinct MI200
64 GB · Q3_K_M · 13.4 tok/s
Fastest card
B200
31.1 tok/s · 180 GB
Which GPUs can run Llama 4 Scout?
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.
43 cards match
Calculating| Needs | Quantisation | Fit | |||||
|---|---|---|---|---|---|---|---|
|
31.1
tok/s
19–50 · low confidence |
B200 NVIDIA | 180 GB | 8,000 GB/s | Jan 2024 | 117.4 GB | Q8_0 | Comfortable |
|
31.1
tok/s
19–50 · low confidence |
B300 NVIDIA | 288 GB | 8,000 GB/s | Sep 2025 | 117.4 GB | Q8_0 | Comfortable |
|
30.1
tok/s
18–48 · low confidence |
H100 SXM5 80 GB NVIDIA | 80 GB | 3,360 GB/s | Oct 2022 | 66.6 GB | Q4_K_M | Tight |
|
30.1
tok/s
18–48 · low confidence |
H800 SXM5 NVIDIA | 80 GB | 3,360 GB/s | Mar 2023 | 66.6 GB | Q4_K_M | Tight |
|
28.8
tok/s
17–46 · low confidence |
Radeon Instinct MI300 AMD | 128 GB | 6,550 GB/s | Jan 2023 | 92.0 GB | Q6_K | Comfortable |
|
27.3
tok/s
16–44 · low confidence |
H100 NVL 94 GB NVIDIA | 94 GB | 3,940 GB/s | Mar 2023 | 79.3 GB | Q5_K_M | Tight |
|
24.8
tok/s
15–40 · low confidence |
Radeon Instinct MI350X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 117.4 GB | Q8_0 | Comfortable |
|
24.8
tok/s
15–40 · low confidence |
Radeon Instinct MI355X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 117.4 GB | Q8_0 | Comfortable |
|
23.5
tok/s
14–38 · low confidence |
Radeon Instinct MI300A AMD | 128 GB | 5,325 GB/s | Dec 2023 | 92.0 GB | Q6_K | Comfortable |
|
23.3
tok/s
14–37 · low confidence |
H100 PCIe 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 79.3 GB | Q5_K_M | Tight |
|
23.3
tok/s
14–37 · low confidence |
H100 SXM5 94 GB NVIDIA | 94 GB | 3,360 GB/s | Mar 2023 | 79.3 GB | Q5_K_M | Tight |
|
23.3
tok/s
14–37 · low confidence |
H100 SXM5 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 79.3 GB | Q5_K_M | Tight |
|
21.2
tok/s
13–34 · low confidence |
H100 SXM5 64 GB NVIDIA | 64 GB | 2,020 GB/s | Mar 2023 | 54.0 GB | Q3_K_M | Tight |
|
19.0
tok/s
11–30 · low confidence |
H200 NVL NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 117.4 GB | Q8_0 | Tight |
|
19.0
tok/s
11–30 · low confidence |
H200 SXM 141 GB NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 117.4 GB | Q8_0 | Tight |
|
18.3
tok/s
11–29 · low confidence |
A100 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Nov 2020 | 66.6 GB | Q4_K_M | Tight |
|
18.3
tok/s
11–29 · low confidence |
A100X NVIDIA | 80 GB | 2,040 GB/s | Jun 2021 | 66.6 GB | Q4_K_M | Tight |
|
18.3
tok/s
11–29 · low confidence |
A800 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Aug 2022 | 66.6 GB | Q4_K_M | Tight |
|
18.3
tok/s
11–29 · low confidence |
H100 CNX NVIDIA | 80 GB | 2,040 GB/s | Mar 2023 | 66.6 GB | Q4_K_M | Tight |
|
18.3
tok/s
11–29 · low confidence |
H100 PCIe 80 GB NVIDIA | 80 GB | 2,040 GB/s | Oct 2022 | 66.6 GB | Q4_K_M | Tight |
|
18.3
tok/s
11–29 · low confidence |
H800 PCIe 80 GB NVIDIA | 80 GB | 2,040 GB/s | Mar 2023 | 66.6 GB | Q4_K_M | Tight |
|
18.2
tok/s
11–29 · low confidence |
Radeon Instinct MI325X AMD | 256 GB | 6,000 GB/s | Oct 2024 | 117.4 GB | Q8_0 | Comfortable |
|
17.4
tok/s
10–28 · low confidence |
A100 PCIe 80 GB NVIDIA | 80 GB | 1,940 GB/s | Jun 2021 | 66.6 GB | Q4_K_M | Tight |
|
17.4
tok/s
10–28 · low confidence |
A800 PCIe 80 GB NVIDIA | 80 GB | 1,940 GB/s | Nov 2022 | 66.6 GB | Q4_K_M | Tight |
|
16.1
tok/s
10–26 · low confidence |
Radeon Instinct MI300X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 117.4 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
- Meta AI
- Organisation type
- Industry
- Country
- United States of America
- Published
- 5 April 2025
What it does
The problem areas the model was built for. A model can carry several of each.
- Domain
- Multimodal, Language, Vision
- Task
- Chat, Code generation, Visual question answering, Language modeling/generation, Question answering
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
- 109B
- Training data
- 30,000,000,000,000 tokens
"Our smaller model, Llama 4 Scout, is a general purpose model with 17 billion active parameters, 16 experts, and 109 billion total parameters that delivers state-of-the-art performance for its class."
"The overall data mixture for training consisted of more than 30 trillion tokens, which is more than double the Llama 3 pre-training mixture and includes diverse text, image, and video datasets."
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
- 4.1 × 10²⁴ FLOP
40T training tokens per model card: https://github.com/meta-llama/llama-models/blob/main/models/llama4/MODEL_CARD.md Estimating training compute from parameters and tokens: 6 FLOP per token per parameter * 17B active parameters * 40T tokens = 4.08e24 FLOP (Implying mean throughput was 227 TFLOPS/GPU, or 11.5% MFU in FP8) The model card also states that Llama 4 Scout used 5.0M H100-hours. The blog post gives a figure of 390 TFLOPS/GPU, but this may have been the utilization rate for Behemot…
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 (restricted use)
- Training code
- Unreleased
- Hugging Face
- meta-llama
Llama 4 license (branding requirements, size cap 700M MAU) https://huggingface.co/meta-llama/Llama-4-Scout-17B-16E no training code here https://github.com/meta-llama/llama-models/tree/main/models/llama4
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
- Why it is tracked
- Discretionary
- Record confidence
- Likely
Sources
Where this record came from and when it was last checked.
- Reference
- The Llama 4 herd: The beginning of a new era of natively multimodal AI innovation
- Last updated
- 28 November 2025
The extremes
The ten fastest GPUs that run Llama 4 Scout
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 31.1 tok/s
- 02 B200 180 GB · 8,000 GB/s · Q8_0 31.1 tok/s
- 03 H800 SXM5 80 GB · 3,360 GB/s · Q4_K_M 30.1 tok/s
- 04 H100 SXM5 80 GB 80 GB · 3,360 GB/s · Q4_K_M 30.1 tok/s
- 05 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q6_K 28.8 tok/s
- 06 H100 NVL 94 GB 94 GB · 3,940 GB/s · Q5_K_M 27.3 tok/s
- 07 Radeon Instinct MI350X 288 GB · 8,190 GB/s · Q8_0 24.8 tok/s
- 08 Radeon Instinct MI355X 288 GB · 8,190 GB/s · Q8_0 24.8 tok/s
- 09 Radeon Instinct MI300A 128 GB · 5,325 GB/s · Q6_K 23.5 tok/s
- 10 H100 PCIe 96 GB 96 GB · 3,360 GB/s · Q5_K_M 23.3 tok/s
The smallest GPUs that still run Llama 4 Scout
The cheapest route in, by memory capacity. A tight fit runs the model but leaves nothing spare for a longer conversation.
- 01 Jetson T4000 64 GB · needs 54.0 GB · Q3_K_M · tight 2.9 tok/s
- 02 H100 SXM5 64 GB 64 GB · needs 54.0 GB · Q3_K_M · tight 21.2 tok/s
- 03 Jetson AGX Orin 64 GB 64 GB · needs 54.0 GB · Q3_K_M · tight 2.2 tok/s
- 04 Radeon Instinct MI200 64 GB · needs 54.0 GB · Q3_K_M · tight 13.4 tok/s
- 05 Radeon Instinct MI210 64 GB · needs 54.0 GB · Q3_K_M · tight 13.4 tok/s
- 06 RTX PRO 5000 72 GB Blackwell 72 GB · needs 60.3 GB · IQ4_XS · tight 12.8 tok/s
- 07 H100 CNX 80 GB · needs 66.6 GB · Q4_K_M · tight 18.3 tok/s
- 08 H800 PCIe 80 GB 80 GB · needs 66.6 GB · Q4_K_M · tight 18.3 tok/s
- 09 H800 SXM5 80 GB · needs 66.6 GB · Q4_K_M · tight 30.1 tok/s
- 10 A800 PCIe 80 GB 80 GB · needs 66.6 GB · Q4_K_M · tight 17.4 tok/s
What the numbers mean
What it takes to run this model
Minimum card
Radeon Instinct MI200
Memory needed
54.0 GB
Fastest
31.1 tok/s
Llama 4 Scout reaches a parameter count of 109B. That puts it above consumer hardware, into the range where a card is bought for this purpose rather than repurposed for it. The number of cards we track that can hold it: 43.
The smallest card that holds it is Radeon Instinct MI200, with a memory capacity of 64 GB, running it at a compression of Q3_K_M and producing around 13.4 tokens per second.
The fastest we calculate for it is B200, generating roughly 31.1 tokens per second on the strength of a memory bandwidth of 8,000 GB/s.
About this model
Llama 4 Scout was published by Meta AI, in the country recorded as United States of America, during April 2025. The category the publisher falls under is industry.
It works in the domain of Multimodal, Language, Vision, and is recorded as performing the task of chat, Code generation, Visual question answering, Language modeling/generation, Question answering.
Because its weights were released, nothing about running it depends on a provider staying available — it is yours once downloaded. On Hugging Face it is published under the organisation meta-llama.
How fast it runs, and why
Half the cards that hold it manage more than 18.2 tokens per second. Exceeding reading speed outright: 39 of them.
Every weight participates in every token here, so bandwidth is the whole story: the ranking below is effectively a ranking of memory throughput.
Without the attention layout on record, the memory column is an approximation. It is close enough to choose hardware by, and least reliable at long context.
How it was trained
The training run consumed about 4.1 × 10²⁴ FLOP. That figure measures what producing the model cost, and has no bearing on how fast it answers.
The training set ran to roughly 30,000,000,000,000 tokens of text.
The reason it appears in this catalogue at all: discretionary.
Step by step
How to choose a GPU for Llama 4 Scout
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
The table lists every card able to hold Llama 4 Scout, needing around 54.0 GB at a compression of Q3_K_M. No amount of processing power compensates for a card that cannot hold it.
-
02
Set the context length you will work at
Longer conversations cost memory on top of what the weights need. Move the slider to your real working length before trusting any row for Llama 4 Scout.
-
03
Decide how much compression you will accept
Compression is what makes a model fit smaller cards, at some cost in accuracy, reaching a compression of Q3_K_M on the smallest card that fits. Setting a minimum quality drops the cards that only manage it by squeezing further than you would want, and holds the comparison at one level.
-
04
Rank by throughput rather than spec sheet
The speed ordering is effectively an ordering by memory bandwidth, for Llama 4 Scout. It will not match a gaming ordering, because generation is bound by memory bandwidth. The card topping the list is B200, at 31.1 tok/s.
-
05
Check the fit verdict before buying
Tight means it loads and works with no room to raise the context later, in the case of Llama 4 Scout. Comfortable means you can grow the context later. That difference matters more than a few tokens per second, so buy for comfortable if you expect to.
-
06
See what else that card runs
Every card name links to its own page, which runs the same calculation across the whole model catalogue. A card is usually bought for more than one model, so it is worth a look before buying for Llama 4 Scout.
Answers
Llama 4 Scout — common questions
Llama 4 Scout— how much VRAM does it need?
It needs about 54.0 GB at a compression of Q3_K_M, 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.
Llama 4 Scout— is it open source?
Its weights are published, so it 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.
Llama 4 Scout— how many parameters does it have?
It has a parameter count of 109B. "Our smaller model, Llama 4 Scout, is a general purpose model with 17 billion active parameters, 16 experts, and 109 billion total parameters that delivers state-of-the-art performance for its class.". 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.
Llama 4 Scout— who created it?
It was published by Meta AI, based in United States of America, an organisation categorised as industry.
Llama 4 Scout— when was it released?
It was published in April 2025.
Llama 4 Scout— what is it used for?
It works in the domain of Multimodal, Language, Vision, and is recorded as handling the task of chat, Code generation, Visual question answering, Language modeling/generation, Question answering. Models frequently carry more than one of each, and the tags describe purpose rather than capability limits.
Llama 4 Scout— where can I download it?
Its weights are published on Hugging Face, under the organisation meta-llama. We do not host model files — this site calculates what hardware is needed to run them.
Llama 4 Scout— how much compute was used to train it?
Training consumed around 4.1 × 10²⁴ FLOP. 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.
Llama 4 Scout— can I run it if it does not fit in my GPU?
It can be split between the card and system memory, but it generates painfully slowly that way. The nearest miss we calculate falls short by 23.4 GB. Every figure here assumes the whole model is resident on the card.
Llama 4 Scout— would two GPUs run it faster?
Two cards buy memory rather than speed, which matters only if one card cannot hold it. The number that can: 43. So a second card is rarely the answer here.
Llama 4 Scout— why does the quantisation differ between cards?
A larger card holds a more accurate copy. The number of compression levels used across the cards that run it: 6. Bigger cards get the more accurate version, and the quality floor above pins the comparison to one level.
Llama 4 Scout— how accurate are these speed estimates?
They are calculated from specifications rather than measured, and each carries a range. One example: 19–50 tok/s on B200. The same model and card vary by thirty to fifty per cent depending on the inference software and its version.
Llama 4 Scout— what GPU do I need to run it?
The smallest card in our catalogue that holds it is Radeon Instinct MI200, with a memory capacity of 64 GB. It runs the model at a compression of Q3_K_M using about 54.0 GB, and produces roughly 13.4 tokens per second. The number of cards able to run it in total: 43.
Llama 4 Scout— how fast is it on a GPU?
It depends on the card. The quickest we calculate is B200, at about 31.1 tokens per second; the slowest that still runs it manages considerably less. Reading speed is around ten tokens per second, and the number of cards clearing that: 39.
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.