Pix2Struct-Large 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 · 28.4 tok/s
Fastest card
B200
2,606 tok/s · 180 GB
Which GPUs can run Pix2Struct-Large?
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 | |||||
|---|---|---|---|---|---|---|---|
|
2,606
tok/s
1,564–4,170 · low confidence |
B200 NVIDIA | 180 GB | 8,000 GB/s | Jan 2024 | 2.1 GB | Q8_0 | Comfortable |
|
2,606
tok/s
1,564–4,170 · low confidence |
B300 NVIDIA | 288 GB | 8,000 GB/s | Sep 2025 | 2.1 GB | Q8_0 | Comfortable |
|
2,081
tok/s
1,249–3,330 · low confidence |
Radeon Instinct MI350X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 2.1 GB | Q8_0 | Comfortable |
|
2,081
tok/s
1,249–3,330 · low confidence |
Radeon Instinct MI355X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 2.1 GB | Q8_0 | Comfortable |
|
1,664
tok/s
999–2,663 · low confidence |
Radeon Instinct MI300 AMD | 128 GB | 6,550 GB/s | Jan 2023 | 2.1 GB | Q8_0 | Comfortable |
|
1,593
tok/s
956–2,549 · low confidence |
H200 NVL NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 2.1 GB | Q8_0 | Comfortable |
|
1,593
tok/s
956–2,549 · low confidence |
H200 SXM 141 GB NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 2.1 GB | Q8_0 | Comfortable |
|
1,525
tok/s
915–2,440 · low confidence |
Radeon Instinct MI325X AMD | 256 GB | 6,000 GB/s | Oct 2024 | 2.1 GB | Q8_0 | Comfortable |
|
1,353
tok/s
812–2,165 · low confidence |
Radeon Instinct MI300A AMD | 128 GB | 5,325 GB/s | Dec 2023 | 2.1 GB | Q8_0 | Comfortable |
|
1,353
tok/s
812–2,165 · low confidence |
Radeon Instinct MI300X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 2.1 GB | Q8_0 | Comfortable |
|
1,353
tok/s
812–2,165 · low confidence |
Radeon Instinct MI308X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 2.1 GB | Q8_0 | Comfortable |
|
1,284
tok/s
770–2,054 · low confidence |
H100 NVL 94 GB NVIDIA | 94 GB | 3,940 GB/s | Mar 2023 | 2.1 GB | Q8_0 | Comfortable |
|
1,095
tok/s
657–1,751 · low confidence |
H100 PCIe 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 2.1 GB | Q8_0 | Comfortable |
|
1,095
tok/s
657–1,751 · low confidence |
H100 SXM5 80 GB NVIDIA | 80 GB | 3,360 GB/s | Oct 2022 | 2.1 GB | Q8_0 | Comfortable |
|
1,095
tok/s
657–1,751 · low confidence |
H100 SXM5 94 GB NVIDIA | 94 GB | 3,360 GB/s | Mar 2023 | 2.1 GB | Q8_0 | Comfortable |
|
1,095
tok/s
657–1,751 · low confidence |
H100 SXM5 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 2.1 GB | Q8_0 | Comfortable |
|
1,095
tok/s
657–1,751 · low confidence |
H800 SXM5 NVIDIA | 80 GB | 3,360 GB/s | Mar 2023 | 2.1 GB | Q8_0 | Comfortable |
|
834
tok/s
500–1,334 · low confidence |
Radeon Instinct MI250 AMD | 128 GB | 3,280 GB/s | Nov 2021 | 2.1 GB | Q8_0 | Comfortable |
|
834
tok/s
500–1,334 · low confidence |
Radeon Instinct MI250X AMD | 128 GB | 3,280 GB/s | Nov 2021 | 2.1 GB | Q8_0 | Comfortable |
|
695
tok/s
417–1,111 · low confidence |
Data Center GPU Max 1550 Intel | 128 GB | 3,280 GB/s | Jan 2023 | 2.1 GB | Q8_0 | Comfortable |
|
680
tok/s
408–1,088 · low confidence |
Data Center GPU Max Subsystem Intel | 128 GB | 3,210 GB/s | Jan 2023 | 2.1 GB | Q8_0 | Comfortable |
|
665
tok/s
399–1,063 · low confidence |
A100 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Nov 2020 | 2.1 GB | Q8_0 | Comfortable |
|
665
tok/s
399–1,063 · low confidence |
A100X NVIDIA | 80 GB | 2,040 GB/s | Jun 2021 | 2.1 GB | Q8_0 | Comfortable |
|
665
tok/s
399–1,063 · low confidence |
A800 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Aug 2022 | 2.1 GB | Q8_0 | Comfortable |
|
665
tok/s
399–1,063 · low confidence |
H100 CNX NVIDIA | 80 GB | 2,040 GB/s | Mar 2023 | 2.1 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 Research,University of Cambridge
- Organisation type
- Industry,Academia
- Country
- United States of America, United Kingdom of Great Britain and Northern Ireland
- Published
- 15 June 2023
- Authors
- Kenton Lee, Mandar Joshi, Iulia Turc, Hexiang Hu, Fangyu Liu, Julian Eisenschlos, Urvashi Khandelwal, Peter Shaw, Ming-Wei Chang, Kristina Toutanova
What it does
The problem areas the model was built for. A model can carry several of each.
- Domain
- Vision
- Task
- Image captioning, Visual 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
- 1.3B
- Training data
- tokens
1.3B
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
- 1.7 × 10²⁰ FLOP
- How it was established
- Operation counting
"The large model is pretrained for 170K steps with a batch size of 1024" "The decoder sequence length is 128 tokens" 6 FLOP / token / parameter * 1.3 * 10^9 parameters * 128 tokens / sample* 1024 samples / step * 170000 steps = 1.7380147e+20 FLOP
The training run
What it physically took to train: which chips, how many, for how long, and what that drew from the wall.
- Chips used
- 128
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
Apache 2.0 https://github.com/google-research/pix2struct
How it is classified
Labels the source dataset applies when tracking notable models, and how confident it is in the entry.
- Record confidence
- Likely
Sources
Where this record came from and when it was last checked.
- Reference
- Pix2Struct: Screenshot Parsing as Pretraining for Visual Language Understanding
- Last updated
- 28 November 2025
The extremes
The ten fastest GPUs that run Pix2Struct-Large
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 2,606 tok/s
- 02 B200 180 GB · 8,000 GB/s · Q8_0 2,606 tok/s
- 03 Radeon Instinct MI350X 288 GB · 8,190 GB/s · Q8_0 2,081 tok/s
- 04 Radeon Instinct MI355X 288 GB · 8,190 GB/s · Q8_0 2,081 tok/s
- 05 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q8_0 1,664 tok/s
- 06 H200 NVL 141 GB · 4,890 GB/s · Q8_0 1,593 tok/s
- 07 H200 SXM 141 GB 141 GB · 4,890 GB/s · Q8_0 1,593 tok/s
- 08 Radeon Instinct MI325X 256 GB · 6,000 GB/s · Q8_0 1,525 tok/s
- 09 Radeon Instinct MI300A 128 GB · 5,325 GB/s · Q8_0 1,353 tok/s
- 10 Radeon Instinct MI300X 192 GB · 5,325 GB/s · Q8_0 1,353 tok/s
The smallest GPUs that still run Pix2Struct-Large
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 2.1 GB · Q8_0 · comfortable 31.3 tok/s
- 02 RTX A400 4 GB · needs 2.1 GB · Q8_0 · comfortable 31.3 tok/s
- 03 RTX 500 Mobile Ada Generation 4 GB · needs 2.1 GB · Q8_0 · comfortable 41.7 tok/s
- 04 GeForce RTX 3050 A Mobile 4 GB · needs 2.1 GB · Q8_0 · comfortable 62.6 tok/s
- 05 Jetson Orin Nano 4 GB 4 GB · needs 2.1 GB · Q8_0 · comfortable 11.1 tok/s
- 06 Radeon RX 6450M 4 GB · needs 2.1 GB · Q8_0 · comfortable 32.5 tok/s
- 07 Radeon RX 6550M 4 GB · needs 2.1 GB · Q8_0 · comfortable 36.6 tok/s
- 08 Radeon RX 6550S 4 GB · needs 2.1 GB · Q8_0 · comfortable 32.5 tok/s
- 09 Arc A310 4 GB · needs 2.1 GB · Q8_0 · comfortable 26.3 tok/s
- 10 Arc Pro A30M 4 GB · needs 2.1 GB · Q8_0 · comfortable 27.1 tok/s
What the numbers mean
Hardware requirements in practice
Minimum card
Tesla C1080
Memory needed
2.1 GB
Fastest
2,606 tok/s
Pix2Struct-Large is small enough at 1.3B parameters that hardware is rarely the obstacle — 818 of the cards we track can run it, including cards several years old.
The entry point is the Tesla C1080: 4 GB of memory, Q8_0 compression, roughly 28.4 tokens per second.
The quickest result comes from a B200 at around 2,606 tokens per second — its 8,000 GB/s of bandwidth is what buys that.
What this model is
Pix2Struct-Large was published by Google Research,University of Cambridge, in United States of America, in June 2023. The organisation is categorised as industry,Academia.
It works in Vision, and is recorded as doing image captioning, Visual question answering.
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.
What decides the speed
Across every card that can run it, the middle of the range is about 73.2 tokens per second, and 797 of them clear the ten tokens per second that roughly matches reading speed.
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.
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
Producing it required around 1.7 × 10²⁰ FLOP of arithmetic, which is a statement about the training budget rather than about inference.
Step by step
How to choose a GPU for Pix2Struct-Large
The table above has already assessed every card we hold specifications for against this model. Getting to your answer takes six steps.
-
01
Start from the memory column
The table lists every card that can hold Pix2Struct-Large — around 2.1 GB at Q8_0. That figure, not the card's headline performance, is what decides whether it runs.
-
02
Set the context length you will work at
The conversation occupies memory too, and grows as it goes. Set the slider to the length you expect: at long context Pix2Struct-Large can slip off a card that handles short questions easily.
-
03
Choose how far you will compress it
Compression is what makes Pix2Struct-Large fit smaller cards, at some cost in accuracy — Q8_0 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 Pix2Struct-Large. It will not match a gaming ordering — generation is bound by memory bandwidth, which is why the B200 tops it at 2,606 tok/s.
-
05
Read the fit column last
Tight means Pix2Struct-Large 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
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 Pix2Struct-Large.
Answers
Pix2Struct-Large — common questions
Where can I download Pix2Struct-Large?
The weights for Pix2Struct-Large are published, though we do not hold a repository link for it. This site calculates hardware requirements rather than hosting model files.
How much compute was used to train Pix2Struct-Large?
Around 1.7 × 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.
Can I run Pix2Struct-Large if it does not fit in my GPU?
Only by offloading, which is usually a false economy: the part in system memory drags the whole thing down. Our figures for Pix2Struct-Large assume it is fully resident.
Would two GPUs run Pix2Struct-Large faster?
A second card roughly doubles the memory available but not the generation rate. With 818 cards already able to run Pix2Struct-Large alone, the case for pairing is weak.
Why does the quantisation differ between cards for Pix2Struct-Large?
Because capacity varies, so does how hard Pix2Struct-Large has to be squeezed — 1 distinct levels appear in the table above. Set a minimum quality to compare at one.
How accurate are these Pix2Struct-Large speed estimates?
Every figure is derived from memory bandwidth and model size, not benchmarked. That is why each is published as a range such as 1,564–4,170 tok/s on the B200 rather than a single number.
What GPU do I need to run Pix2Struct-Large?
The smallest card in our catalogue that holds Pix2Struct-Large is the Tesla C1080, with 4 GB of memory. It runs the model at Q8_0 using about 2.1 GB, and produces roughly 28.4 tokens per second. 818 cards in total can run it.
How fast is Pix2Struct-Large on a GPU?
It depends on the card. The quickest we calculate is a B200 at about 2,606 tokens per second; the slowest that still runs it manages considerably less. Reading speed is around ten tokens per second, and 797 of the cards that can run Pix2Struct-Large clear that.
How much VRAM does Pix2Struct-Large need?
About 2.1 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 Pix2Struct-Large on a 8 GB GPU?
Yes. A CMP 170HX 8 GB with 8 GB runs it at Q8_0, using about 2.1 GB and generating roughly 485 tokens per second — a comfortable fit.
Can I run Pix2Struct-Large on a 12 GB GPU?
Yes. A GeForce RTX 3080 Ti with 12 GB runs it at Q8_0, using about 2.1 GB and generating roughly 297 tokens per second — a comfortable fit.
Can I run Pix2Struct-Large on a 16 GB GPU?
Yes. A Tesla V100 SXM2 16 GB with 16 GB runs it at Q8_0, using about 2.1 GB and generating roughly 368 tokens per second — a comfortable fit.
Can I run Pix2Struct-Large on a 24 GB GPU?
Yes. A GeForce RTX 5090 D V2 with 24 GB runs it at Q8_0, using about 2.1 GB and generating roughly 437 tokens per second — a comfortable fit.
Is Pix2Struct-Large open source?
Its weights are published, so Pix2Struct-Large 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 Pix2Struct-Large have?
Pix2Struct-Large has 1.3B parameters. 1.3B. 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 Pix2Struct-Large?
Pix2Struct-Large was published by Google Research,University of Cambridge, based in United States of America, categorised as industry,Academia.
When was Pix2Struct-Large released?
Pix2Struct-Large was published in June 2023. 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 Pix2Struct-Large used for?
Pix2Struct-Large works in Vision, and is recorded as handling image captioning, Visual question answering. Models frequently carry more than one of each, and the tags describe purpose rather than capability limits.
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.