ViT-Base/32 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 · Q8_0 · 429 tok/s
Fastest card
B200
39,398 tok/s · 180 GB
Which GPUs can run ViT-Base/32?
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 | |||||
|---|---|---|---|---|---|---|---|
|
39,398
tok/s
23,639–63,037 · low confidence |
B200 NVIDIA | 180 GB | 8,000 GB/s | Jan 2024 | 0.8 GB | Q8_0 | Comfortable |
|
39,398
tok/s
23,639–63,037 · low confidence |
B300 NVIDIA | 288 GB | 8,000 GB/s | Sep 2025 | 0.8 GB | Q8_0 | Comfortable |
|
31,460
tok/s
18,876–50,337 · low confidence |
Radeon Instinct MI350X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 0.8 GB | Q8_0 | Comfortable |
|
31,460
tok/s
18,876–50,337 · low confidence |
Radeon Instinct MI355X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 0.8 GB | Q8_0 | Comfortable |
|
25,161
tok/s
15,096–40,257 · low confidence |
Radeon Instinct MI300 AMD | 128 GB | 6,550 GB/s | Jan 2023 | 0.8 GB | Q8_0 | Comfortable |
|
24,082
tok/s
14,449–38,531 · low confidence |
H200 NVL NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 0.8 GB | Q8_0 | Comfortable |
|
24,082
tok/s
14,449–38,531 · low confidence |
H200 SXM 141 GB NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 0.8 GB | Q8_0 | Comfortable |
|
23,048
tok/s
13,829–36,877 · low confidence |
Radeon Instinct MI325X AMD | 256 GB | 6,000 GB/s | Oct 2024 | 0.8 GB | Q8_0 | Comfortable |
|
20,455
tok/s
12,273–32,728 · low confidence |
Radeon Instinct MI300A AMD | 128 GB | 5,325 GB/s | Dec 2023 | 0.8 GB | Q8_0 | Comfortable |
|
20,455
tok/s
12,273–32,728 · low confidence |
Radeon Instinct MI300X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 0.8 GB | Q8_0 | Comfortable |
|
20,455
tok/s
12,273–32,728 · low confidence |
Radeon Instinct MI308X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 0.8 GB | Q8_0 | Comfortable |
|
19,404
tok/s
11,642–31,046 · low confidence |
H100 NVL 94 GB NVIDIA | 94 GB | 3,940 GB/s | Mar 2023 | 0.8 GB | Q8_0 | Comfortable |
|
16,547
tok/s
9,928–26,476 · low confidence |
H100 PCIe 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 0.8 GB | Q8_0 | Comfortable |
|
16,547
tok/s
9,928–26,476 · low confidence |
H100 SXM5 80 GB NVIDIA | 80 GB | 3,360 GB/s | Oct 2022 | 0.8 GB | Q8_0 | Comfortable |
|
16,547
tok/s
9,928–26,476 · low confidence |
H100 SXM5 94 GB NVIDIA | 94 GB | 3,360 GB/s | Mar 2023 | 0.8 GB | Q8_0 | Comfortable |
|
16,547
tok/s
9,928–26,476 · low confidence |
H100 SXM5 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 0.8 GB | Q8_0 | Comfortable |
|
16,547
tok/s
9,928–26,476 · low confidence |
H800 SXM5 NVIDIA | 80 GB | 3,360 GB/s | Mar 2023 | 0.8 GB | Q8_0 | Comfortable |
|
12,600
tok/s
7,560–20,159 · low confidence |
Radeon Instinct MI250 AMD | 128 GB | 3,280 GB/s | Nov 2021 | 0.8 GB | Q8_0 | Comfortable |
|
12,600
tok/s
7,560–20,159 · low confidence |
Radeon Instinct MI250X AMD | 128 GB | 3,280 GB/s | Nov 2021 | 0.8 GB | Q8_0 | Comfortable |
|
10,500
tok/s
6,300–16,799 · low confidence |
Data Center GPU Max 1550 Intel | 128 GB | 3,280 GB/s | Jan 2023 | 0.8 GB | Q8_0 | Comfortable |
|
10,276
tok/s
6,165–16,441 · low confidence |
Data Center GPU Max Subsystem Intel | 128 GB | 3,210 GB/s | Jan 2023 | 0.8 GB | Q8_0 | Comfortable |
|
10,047
tok/s
6,028–16,074 · low confidence |
A100 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Nov 2020 | 0.8 GB | Q8_0 | Comfortable |
|
10,047
tok/s
6,028–16,074 · low confidence |
A100X NVIDIA | 80 GB | 2,040 GB/s | Jun 2021 | 0.8 GB | Q8_0 | Comfortable |
|
10,047
tok/s
6,028–16,074 · low confidence |
A800 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Aug 2022 | 0.8 GB | Q8_0 | Comfortable |
|
10,047
tok/s
6,028–16,074 · low confidence |
H100 CNX NVIDIA | 80 GB | 2,040 GB/s | Mar 2023 | 0.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
- Google Brain
- Organisation type
- Industry
- Country
- United States of America
- Published
- 22 October 2020
- Authors
- Alexey Dosovitskiy, Lucas Beyer, Alexander Kolesnikov, Dirk Weissenborn, Xiaohua Zhai, Thomas Unterthiner, Mostafa Dehghani, Matthias Minderer, Georg Heigold, Sylvain Gelly, Jakob Uszkoreit, Neil Houlsby
What it does
The problem areas the model was built for. A model can carry several of each.
- Domain
- Vision
- Task
- Image representation
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
- 86M
- Training data
- 303,000,000 tokens
- Epochs
- 7
Table 1 https://arxiv.org/pdf/2010.11929.pdf
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
- Open source
- Hugging Face
Apache 2.0 https://huggingface.co/google/vit-base-patch16-224 https://github.com/google-research/vision_transformer https://github.com/google-research/big_vision
How it is classified
Labels the source dataset applies when tracking notable models, and how confident it is in the entry.
- Why it is tracked
- Highly cited
- Citations
- 62,651
Sources
Where this record came from and when it was last checked.
- Reference
- An Image is Worth 16x16 Words: Transformers for Image Recognition at Scale
- Last updated
- 25 May 2026
The extremes
The ten fastest GPUs that run ViT-Base/32
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 39,398 tok/s
- 02 B200 180 GB · 8,000 GB/s · Q8_0 39,398 tok/s
- 03 Radeon Instinct MI350X 288 GB · 8,190 GB/s · Q8_0 31,460 tok/s
- 04 Radeon Instinct MI355X 288 GB · 8,190 GB/s · Q8_0 31,460 tok/s
- 05 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q8_0 25,161 tok/s
- 06 H200 NVL 141 GB · 4,890 GB/s · Q8_0 24,082 tok/s
- 07 H200 SXM 141 GB 141 GB · 4,890 GB/s · Q8_0 24,082 tok/s
- 08 Radeon Instinct MI325X 256 GB · 6,000 GB/s · Q8_0 23,048 tok/s
- 09 Radeon Instinct MI300A 128 GB · 5,325 GB/s · Q8_0 20,455 tok/s
- 10 Radeon Instinct MI300X 192 GB · 5,325 GB/s · Q8_0 20,455 tok/s
The smallest GPUs that still run ViT-Base/32
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 0.8 GB · Q8_0 · comfortable 473 tok/s
- 02 RTX A400 4 GB · needs 0.8 GB · Q8_0 · comfortable 473 tok/s
- 03 RTX 500 Mobile Ada Generation 4 GB · needs 0.8 GB · Q8_0 · comfortable 630 tok/s
- 04 GeForce RTX 3050 A Mobile 4 GB · needs 0.8 GB · Q8_0 · comfortable 946 tok/s
- 05 Jetson Orin Nano 4 GB 4 GB · needs 0.8 GB · Q8_0 · comfortable 168 tok/s
- 06 Radeon RX 6450M 4 GB · needs 0.8 GB · Q8_0 · comfortable 492 tok/s
- 07 Radeon RX 6550M 4 GB · needs 0.8 GB · Q8_0 · comfortable 553 tok/s
- 08 Radeon RX 6550S 4 GB · needs 0.8 GB · Q8_0 · comfortable 492 tok/s
- 09 Arc A310 4 GB · needs 0.8 GB · Q8_0 · comfortable 397 tok/s
- 10 Arc Pro A30M 4 GB · needs 0.8 GB · Q8_0 · comfortable 410 tok/s
What the numbers mean
What you need to run it
Minimum card
Tesla C1080
Memory needed
0.8 GB
Fastest
39,398 tok/s
ViT-Base/32 is small enough at 86M 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 Q8_0 compression, giving roughly 429 tokens per second.
A B200 is the fastest we calculate for it: about 39,398 tokens per second, from 8,000 GB/s of memory bandwidth.
What this model is
ViT-Base/32 was published by Google Brain, in United States of America, in October 2020. The organisation is categorised as industry.
It works in Vision, and is recorded as doing image representation.
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 google organisation on Hugging Face.
What decides the speed
Across every card that can run it, the middle of the range is about 1,106.3 tokens per second, and 818 of them clear the ten tokens per second that roughly matches reading speed.
Every weight participates in every token here, so bandwidth is the whole story: the ranking below is effectively a ranking of memory throughput.
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
Around 303,000,000 tokens went into training it.
Its inclusion criterion is highly cited.
Step by step
How to choose a GPU for ViT-Base/32
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 that can hold ViT-Base/32 — around 0.8 GB at Q8_0. That figure, not the card's headline performance, is what decides whether it runs.
-
02
Match the context to your actual use
Set the context to what you will actually use. The cache grows with the conversation, and it is the usual reason ViT-Base/32 stops fitting a card that seemed fine.
-
03
Choose how far you will compress it
The quantisation column varies by card, because a bigger card holds a more accurate copy of ViT-Base/32 — Q8_0 on the smallest card that fits. Set a floor to hold the comparison at one level.
-
04
Rank by throughput rather than spec sheet
Sort by speed to see how cards rank for ViT-Base/32. It will not match a gaming ordering — generation is bound by memory bandwidth, which is why the B200 tops it at 39,398 tok/s.
-
05
Look at the headroom, not just the fit
Tight means ViT-Base/32 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
Following a card through to its own page shows every other model it can hold, which is the question that follows once ViT-Base/32 is settled.
Answers
ViT-Base/32 — common questions
Who created ViT-Base/32?
ViT-Base/32 was published by Google Brain, based in United States of America, categorised as industry.
When was ViT-Base/32 released?
ViT-Base/32 was published in October 2020. 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 ViT-Base/32 used for?
ViT-Base/32 works in Vision, and is recorded as handling image representation. 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 ViT-Base/32?
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.
Can I run ViT-Base/32 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 ViT-Base/32 is rarely worth using. Every figure here assumes the whole model is on the card.
Would two GPUs run ViT-Base/32 faster?
Capacity adds across cards; throughput does not. Since 818 of the cards we track already hold ViT-Base/32 on their own, a second card is rarely the answer here.
Why does the quantisation differ between cards for ViT-Base/32?
A larger card holds a more accurate copy. Across the cards that run ViT-Base/32, 1 compression levels are used; the floor control above pins it to one.
How accurate are these ViT-Base/32 speed estimates?
These are estimates with real error bars. The fastest result here, 23,639–63,037 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 ViT-Base/32?
The smallest card in our catalogue that holds ViT-Base/32 is the Tesla C1080, with 4 GB of memory. It runs the model at Q8_0 using about 0.8 GB, and produces roughly 429 tokens per second. 818 cards in total can run it.
How fast is ViT-Base/32 on a GPU?
It depends on the card. The quickest we calculate is a B200 at about 39,398 tokens per second; the slowest that still runs it manages considerably less. Reading speed is around ten tokens per second, and 818 of the cards that can run ViT-Base/32 clear that.
How much VRAM does ViT-Base/32 need?
About 0.8 GB at Q8_0 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 ViT-Base/32 on a 8 GB GPU?
Yes. A CMP 170HX 8 GB with 8 GB runs it at Q8_0, using about 0.8 GB and generating roughly 7,338 tokens per second — a comfortable fit.
Can I run ViT-Base/32 on a 12 GB GPU?
Yes. A GeForce RTX 3080 Ti with 12 GB runs it at Q8_0, using about 0.8 GB and generating roughly 4,493 tokens per second — a comfortable fit.
Can I run ViT-Base/32 on a 16 GB GPU?
Yes. A Tesla V100 SXM2 16 GB with 16 GB runs it at Q8_0, using about 0.8 GB and generating roughly 5,565 tokens per second — a comfortable fit.
Can I run ViT-Base/32 on a 24 GB GPU?
Yes. A GeForce RTX 5090 D V2 with 24 GB runs it at Q8_0, using about 0.8 GB and generating roughly 6,599 tokens per second — a comfortable fit.
Is ViT-Base/32 open source?
Its weights are published, so ViT-Base/32 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 ViT-Base/32 have?
ViT-Base/32 has 86M parameters. Table 1 https://arxiv.org/pdf/2010.11929.pdf. 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.
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.