Gemma 3 12B 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
Xeon Phi 5110P
8 GB · Q3_K_M · 19.8 tok/s
Fastest card
B200
282 tok/s · 180 GB
Which GPUs can run Gemma 3 12B?
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.
509 cards match
Calculating| Needs | Quantisation | Fit | |||||
|---|---|---|---|---|---|---|---|
|
282
tok/s
240–339 |
B200 NVIDIA | 180 GB | 8,000 GB/s | Jan 2024 | 13.6 GB | Q8_0 | Comfortable |
|
282
tok/s
240–339 |
B300 NVIDIA | 288 GB | 8,000 GB/s | Sep 2025 | 13.6 GB | Q8_0 | Comfortable |
|
225
tok/s
135–361 · low confidence |
Radeon Instinct MI350X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 13.6 GB | Q8_0 | Comfortable |
|
225
tok/s
135–361 · low confidence |
Radeon Instinct MI355X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 13.6 GB | Q8_0 | Comfortable |
|
180
tok/s
108–289 · low confidence |
Radeon Instinct MI300 AMD | 128 GB | 6,550 GB/s | Jan 2023 | 13.6 GB | Q8_0 | Comfortable |
|
173
tok/s
147–207 |
H200 NVL NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 13.6 GB | Q8_0 | Comfortable |
|
173
tok/s
147–207 |
H200 SXM 141 GB NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 13.6 GB | Q8_0 | Comfortable |
|
165
tok/s
99–264 · low confidence |
Radeon Instinct MI325X AMD | 256 GB | 6,000 GB/s | Oct 2024 | 13.6 GB | Q8_0 | Comfortable |
|
147
tok/s
88–235 · low confidence |
Radeon Instinct MI300A AMD | 128 GB | 5,325 GB/s | Dec 2023 | 13.6 GB | Q8_0 | Comfortable |
|
147
tok/s
88–235 · low confidence |
Radeon Instinct MI300X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 13.6 GB | Q8_0 | Comfortable |
|
147
tok/s
88–235 · low confidence |
Radeon Instinct MI308X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 13.6 GB | Q8_0 | Comfortable |
|
142
tok/s
121–170 |
CMP 170HX 8 GB NVIDIA | 8 GB | 1,490 GB/s | Sep 2021 | 6.6 GB | Q3_K_M | Tight |
|
139
tok/s
118–167 |
H100 NVL 94 GB NVIDIA | 94 GB | 3,940 GB/s | Mar 2023 | 13.6 GB | Q8_0 | Comfortable |
|
127
tok/s
108–153 |
CMP 170HX 10 GB NVIDIA | 10 GB | 1,560 GB/s | Sep 2021 | 8.0 GB | Q4_K_M | Tight |
|
119
tok/s
101–142 |
H100 PCIe 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 13.6 GB | Q8_0 | Comfortable |
|
119
tok/s
101–142 |
H100 SXM5 80 GB NVIDIA | 80 GB | 3,360 GB/s | Oct 2022 | 13.6 GB | Q8_0 | Comfortable |
|
119
tok/s
101–142 |
H100 SXM5 94 GB NVIDIA | 94 GB | 3,360 GB/s | Mar 2023 | 13.6 GB | Q8_0 | Comfortable |
|
119
tok/s
101–142 |
H100 SXM5 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 13.6 GB | Q8_0 | Comfortable |
|
119
tok/s
101–142 |
H800 SXM5 NVIDIA | 80 GB | 3,360 GB/s | Mar 2023 | 13.6 GB | Q8_0 | Comfortable |
|
90.3
tok/s
54–144 · low confidence |
Radeon Instinct MI250 AMD | 128 GB | 3,280 GB/s | Nov 2021 | 13.6 GB | Q8_0 | Comfortable |
|
90.3
tok/s
54–144 · low confidence |
Radeon Instinct MI250X AMD | 128 GB | 3,280 GB/s | Nov 2021 | 13.6 GB | Q8_0 | Comfortable |
|
75.3
tok/s
45–120 · low confidence |
Data Center GPU Max 1550 Intel | 128 GB | 3,280 GB/s | Jan 2023 | 13.6 GB | Q8_0 | Comfortable |
|
73.6
tok/s
44–118 · low confidence |
Data Center GPU Max Subsystem Intel | 128 GB | 3,210 GB/s | Jan 2023 | 13.6 GB | Q8_0 | Comfortable |
|
73.1
tok/s
62–88 |
RTX A5000-8Q NVIDIA | 8 GB | 768 GB/s | Apr 2021 | 6.6 GB | Q3_K_M | Tight |
|
72.0
tok/s
61–86 |
A100 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Nov 2020 | 13.6 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
- Google DeepMind
- Organisation type
- Industry
- Country
- United States of America
- Published
- 12 March 2025
- Authors
- Core contributors: Aishwarya Kamath, Johan Ferret, Shreya Pathak, Nino Vieillard, Ramona Merhej, Sarah Perrin, Tatiana Matejovicova, Alexandre Ramé, Morgane Rivière, Louis Rouillard, Thomas Mesnard, Geoffrey Cideron, Jean-bastien Grill, Sabela Ramos, Edouard Yvinec, Michelle Casbon, Etienne Pot, Ivo Penchev, Gaël Liu, Francesco Visin, Kathleen Kenealy, Lucas Beyer, Xiaohai Zhai, Anton Tsitsulin, R…
What it does
The problem areas the model was built for. A model can carry several of each.
- Domain
- Language, Vision, Multimodal
- Task
- Language modeling/generation, Question answering, Translation, Chat, Quantitative reasoning, Visual question answering, Code generation
- Base model
- SigLIP 400M
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
- 12B
- Training data
- 12,000,000,000,000 tokens
Vision Encoder: 417M Embedding Parameters: 1,012M Non-embedding Parameters: 10,759M
12T
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
- 8.6 × 10²³ FLOP
- How it was established
- Operation counting
6ND = 6 * 12B parameters * 12T training tokens = 8.64 × 10^23 FLOP
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
- Google TPU v4
- Chips used
- 6,144
- Power draw
- 4.1 MW
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
https://huggingface.co/google/gemma-3-12b-it Gemma License
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
- Gemma 3 Technical Report
- Last updated
- 28 November 2025
The extremes
The ten fastest GPUs that run Gemma 3 12B
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 282 tok/s
- 02 B200 180 GB · 8,000 GB/s · Q8_0 282 tok/s
- 03 Radeon Instinct MI350X 288 GB · 8,190 GB/s · Q8_0 225 tok/s
- 04 Radeon Instinct MI355X 288 GB · 8,190 GB/s · Q8_0 225 tok/s
- 05 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q8_0 180 tok/s
- 06 H200 NVL 141 GB · 4,890 GB/s · Q8_0 173 tok/s
- 07 H200 SXM 141 GB 141 GB · 4,890 GB/s · Q8_0 173 tok/s
- 08 Radeon Instinct MI325X 256 GB · 6,000 GB/s · Q8_0 165 tok/s
- 09 Radeon Instinct MI300A 128 GB · 5,325 GB/s · Q8_0 147 tok/s
- 10 Radeon Instinct MI300X 192 GB · 5,325 GB/s · Q8_0 147 tok/s
The smallest GPUs that still run Gemma 3 12B
The cheapest route in, by memory capacity. A tight fit runs the model but leaves nothing spare for a longer conversation.
- 01 Radeon RX 7400 8 GB · needs 6.6 GB · Q3_K_M · tight 21.4 tok/s
- 02 Radeon RX 9060 8 GB · needs 6.6 GB · Q3_K_M · tight 23.9 tok/s
- 03 GeForce RTX 5050 8 GB · needs 6.6 GB · Q3_K_M · tight 30.5 tok/s
- 04 GeForce RTX 5050 Mobile 8 GB · needs 6.6 GB · Q3_K_M · tight 36.6 tok/s
- 05 Radeon RX 9060 XT 8 GB 8 GB · needs 6.6 GB · Q3_K_M · tight 23.9 tok/s
- 06 GeForce RTX 5060 Mobile 8 GB · needs 6.6 GB · Q3_K_M · tight 36.6 tok/s
- 07 GeForce RTX 5060 8 GB · needs 6.6 GB · Q3_K_M · tight 42.7 tok/s
- 08 GeForce RTX 5060 Ti 8 GB 8 GB · needs 6.6 GB · Q3_K_M · tight 42.7 tok/s
- 09 GeForce RTX 5070 Mobile 8 GB · needs 6.6 GB · Q3_K_M · tight 36.6 tok/s
- 10 Radeon RX 7650 GRE 8 GB · needs 6.6 GB · Q3_K_M · tight 21.4 tok/s
What the numbers mean
The hardware side
Minimum card
Xeon Phi 5110P
Memory needed
6.6 GB
Fastest
282 tok/s
Gemma 3 12B is small enough at 12B parameters that hardware is rarely the obstacle — 509 of the cards we track can run it, including cards several years old.
At the low end, a Xeon Phi 5110P handles it — 8 GB, at Q3_K_M, for about 19.8 tokens per second.
At the other end, a B200 generates roughly 282 tokens per second on it, on the strength of 8,000 GB/s of memory bandwidth.
What this model is
Gemma 3 12B was published by Google DeepMind, in United States of America, in March 2025. It comes out of industry.
It works in Language, Vision, Multimodal, and is recorded as doing language modeling/generation, Question answering, Translation, Chat, Quantitative reasoning, Visual question answering, Code generation.
It builds on SigLIP 400M, which is why it shares that model's general shape and size.
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 google organisation on Hugging Face.
What decides the speed
The median result is around 21.2 tokens per second; 455 cards produce text faster than most people read it.
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.
Because the architecture is recorded, the memory column is derived rather than estimated.
How it was trained
Producing it required around 8.6 × 10²³ FLOP of arithmetic, on Google TPU v4, which is a statement about the training budget rather than about inference.
The training set ran to roughly 12,000,000,000,000 tokens.
Step by step
How to choose a GPU for Gemma 3 12B
The table above has already assessed every card we hold specifications for against this model. Getting to your answer takes six steps.
-
01
Check what it needs before anything else
The table lists every card that can hold Gemma 3 12B — around 6.6 GB at Q3_K_M. That figure, not the card's headline performance, is what decides whether it runs.
-
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 Gemma 3 12B.
-
03
Decide how much compression you will accept
The quantisation column varies by card, because a bigger card holds a more accurate copy of Gemma 3 12B — Q3_K_M on the smallest card that fits. Set a floor to hold the comparison at one level.
-
04
Sort by speed
Ranking by tokens per second for Gemma 3 12B follows memory bandwidth, not core counts, which is why the B200 tops it at 282 tok/s.
-
05
Look at the headroom, not just the fit
The fit column separates cards that just manage Gemma 3 12B from those with room to spare. Buy for the second if the context might grow.
-
06
Open the card you have settled on
Each card page repeats this sweep for every model we hold. It answers what else the hardware is good for, beyond Gemma 3 12B.
Answers
Gemma 3 12B — common questions
Can I run Gemma 3 12B if it does not fit in my GPU?
It can be split between the card and system memory, but Gemma 3 12B generates painfully slowly that way — the nearest miss we calculate is short by 2.6 GB. Nothing on this page assumes offloading.
Would two GPUs run Gemma 3 12B faster?
Capacity adds across cards; throughput does not. Since 509 of the cards we track already hold Gemma 3 12B on their own, a second card is rarely the answer here.
Why does the quantisation differ between cards for Gemma 3 12B?
A larger card holds a more accurate copy. Across the cards that run Gemma 3 12B, 4 compression levels are used; the floor control above pins it to one.
How accurate are these Gemma 3 12B speed estimates?
They are calculated from specifications rather than measured, and each carries a range — 240–339 tok/s on the B200, for instance. The same model and card vary by thirty to fifty per cent depending on the inference software and its version.
What GPU do I need to run Gemma 3 12B?
The smallest card in our catalogue that holds Gemma 3 12B is the Xeon Phi 5110P, with 8 GB of memory. It runs the model at Q3_K_M using about 6.6 GB, and produces roughly 19.8 tokens per second. 509 cards in total can run it.
How fast is Gemma 3 12B on a GPU?
It depends on the card. The quickest we calculate is a B200 at about 282 tokens per second; the slowest that still runs it manages considerably less. Reading speed is around ten tokens per second, and 455 of the cards that can run Gemma 3 12B clear that.
How much VRAM does Gemma 3 12B need?
About 6.6 GB at Q3_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 Gemma 3 12B on a 8 GB GPU?
Yes. A CMP 170HX 8 GB with 8 GB runs it at Q3_K_M, using about 6.6 GB and generating roughly 142 tokens per second — a tight fit.
Can I run Gemma 3 12B on a 12 GB GPU?
Yes. A GeForce RTX 3080 Ti with 12 GB runs it at Q5_K_M, using about 9.4 GB and generating roughly 57.5 tokens per second — a tight fit.
Can I run Gemma 3 12B on a 16 GB GPU?
Yes. A Tesla V100 SXM2 16 GB with 16 GB runs it at Q8_0, using about 13.6 GB and generating roughly 39.9 tokens per second — a tight fit.
Can I run Gemma 3 12B on a 24 GB GPU?
Yes. A GeForce RTX 5090 D V2 with 24 GB runs it at Q8_0, using about 13.6 GB and generating roughly 47.3 tokens per second — a comfortable fit.
Is Gemma 3 12B open source?
Its weights are published, so Gemma 3 12B 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 Gemma 3 12B have?
Gemma 3 12B has 12B parameters. Vision Encoder: 417M Embedding Parameters: 1,012M Non-embedding Parameters: 10,759M. 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 Gemma 3 12B?
Gemma 3 12B was published by Google DeepMind, based in United States of America, categorised as industry.
When was Gemma 3 12B released?
Gemma 3 12B was published in March 2025.
What is Gemma 3 12B used for?
Gemma 3 12B works in Language, Vision, Multimodal, and is recorded as handling language modeling/generation, Question answering, Translation, Chat, Quantitative reasoning, Visual question answering, Code generation. 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 Gemma 3 12B?
Its weights are published under the google 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 Gemma 3 12B?
Around 8.6 × 10²³ FLOP, on Google TPU v4. 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.
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.