SigLIP 2 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 · 32.3 tok/s
Fastest card
B200
2,972 tok/s · 180 GB
Which GPUs can run SigLIP 2?
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,972
tok/s
1,783–4,755 · low confidence |
B200 NVIDIA | 180 GB | 8,000 GB/s | Jan 2024 | 1.9 GB | Q8_0 | Comfortable |
|
2,972
tok/s
1,783–4,755 · low confidence |
B300 NVIDIA | 288 GB | 8,000 GB/s | Sep 2025 | 1.9 GB | Q8_0 | Comfortable |
|
2,373
tok/s
1,424–3,797 · low confidence |
Radeon Instinct MI350X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 1.9 GB | Q8_0 | Comfortable |
|
2,373
tok/s
1,424–3,797 · low confidence |
Radeon Instinct MI355X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 1.9 GB | Q8_0 | Comfortable |
|
1,898
tok/s
1,139–3,037 · low confidence |
Radeon Instinct MI300 AMD | 128 GB | 6,550 GB/s | Jan 2023 | 1.9 GB | Q8_0 | Comfortable |
|
1,817
tok/s
1,090–2,907 · low confidence |
H200 NVL NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 1.9 GB | Q8_0 | Comfortable |
|
1,817
tok/s
1,090–2,907 · low confidence |
H200 SXM 141 GB NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 1.9 GB | Q8_0 | Comfortable |
|
1,739
tok/s
1,043–2,782 · low confidence |
Radeon Instinct MI325X AMD | 256 GB | 6,000 GB/s | Oct 2024 | 1.9 GB | Q8_0 | Comfortable |
|
1,543
tok/s
926–2,469 · low confidence |
Radeon Instinct MI300A AMD | 128 GB | 5,325 GB/s | Dec 2023 | 1.9 GB | Q8_0 | Comfortable |
|
1,543
tok/s
926–2,469 · low confidence |
Radeon Instinct MI300X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 1.9 GB | Q8_0 | Comfortable |
|
1,543
tok/s
926–2,469 · low confidence |
Radeon Instinct MI308X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 1.9 GB | Q8_0 | Comfortable |
|
1,464
tok/s
878–2,342 · low confidence |
H100 NVL 94 GB NVIDIA | 94 GB | 3,940 GB/s | Mar 2023 | 1.9 GB | Q8_0 | Comfortable |
|
1,248
tok/s
749–1,997 · low confidence |
H100 PCIe 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 1.9 GB | Q8_0 | Comfortable |
|
1,248
tok/s
749–1,997 · low confidence |
H100 SXM5 80 GB NVIDIA | 80 GB | 3,360 GB/s | Oct 2022 | 1.9 GB | Q8_0 | Comfortable |
|
1,248
tok/s
749–1,997 · low confidence |
H100 SXM5 94 GB NVIDIA | 94 GB | 3,360 GB/s | Mar 2023 | 1.9 GB | Q8_0 | Comfortable |
|
1,248
tok/s
749–1,997 · low confidence |
H100 SXM5 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 1.9 GB | Q8_0 | Comfortable |
|
1,248
tok/s
749–1,997 · low confidence |
H800 SXM5 NVIDIA | 80 GB | 3,360 GB/s | Mar 2023 | 1.9 GB | Q8_0 | Comfortable |
|
950
tok/s
570–1,521 · low confidence |
Radeon Instinct MI250 AMD | 128 GB | 3,280 GB/s | Nov 2021 | 1.9 GB | Q8_0 | Comfortable |
|
950
tok/s
570–1,521 · low confidence |
Radeon Instinct MI250X AMD | 128 GB | 3,280 GB/s | Nov 2021 | 1.9 GB | Q8_0 | Comfortable |
|
792
tok/s
475–1,267 · low confidence |
Data Center GPU Max 1550 Intel | 128 GB | 3,280 GB/s | Jan 2023 | 1.9 GB | Q8_0 | Comfortable |
|
775
tok/s
465–1,240 · low confidence |
Data Center GPU Max Subsystem Intel | 128 GB | 3,210 GB/s | Jan 2023 | 1.9 GB | Q8_0 | Comfortable |
|
758
tok/s
455–1,213 · low confidence |
A100 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Nov 2020 | 1.9 GB | Q8_0 | Comfortable |
|
758
tok/s
455–1,213 · low confidence |
A100X NVIDIA | 80 GB | 2,040 GB/s | Jun 2021 | 1.9 GB | Q8_0 | Comfortable |
|
758
tok/s
455–1,213 · low confidence |
A800 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Aug 2022 | 1.9 GB | Q8_0 | Comfortable |
|
758
tok/s
455–1,213 · low confidence |
H100 CNX NVIDIA | 80 GB | 2,040 GB/s | Mar 2023 | 1.9 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
- 20 February 2025
- Authors
- Michael Tschannen, Alexey Gritsenko, Xiao Wang, Muhammad Ferjad Naeem, Ibrahim Alabdulmohsin, Nikhil Parthasarathy, Talfan Evans, Lucas Beyer, Ye Xia, Basil Mustafa, Olivier Hénaff, Jeremiah Harmsen, Andreas Steiner, Xiaohua Zhai
What it does
The problem areas the model was built for. A model can carry several of each.
- Domain
- Vision
- Task
- Image classification, Image embedding
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.1B
- Training data
- tokens
1B
"We use the WebLI dataset [10] containing 10 billion images and 12 billion alt-texts covering 109 languages." "We set the batch size to 32k and use a cosine schedule with 20k warmup steps, training for a total of 40B examples." "For all model sizes, we set the vision encoder patch size to 16 and the image resolution to 256 (resulting in an image representation sequence length of 256)." 40 * 10^9 examples * 256 image tokens per example = 1.024e+13 image tokens (10T) "We set the text length to…
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.2 × 10²² FLOP
- How it was established
- Operation counting
6 FLOP/parameter/token * 1140000000 parameters * 12000000000000 tokens [see dataset size notes] = 8.208e+22 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 v5e
- Chips used
- 2,048
- Power draw
- 904.7 kW
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
Apache 2.0 https://huggingface.co/google/siglip2-so400m-patch16-512
How it is classified
Labels the source dataset applies when tracking notable models, and how confident it is in the entry.
- Record confidence
- Confident
Sources
Where this record came from and when it was last checked.
- Reference
- SigLIP 2: Multilingual Vision-Language Encoders with Improved Semantic Understanding, Localization, and Dense Features
- Last updated
- 28 November 2025
The extremes
The ten fastest GPUs that run SigLIP 2
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,972 tok/s
- 02 B200 180 GB · 8,000 GB/s · Q8_0 2,972 tok/s
- 03 Radeon Instinct MI350X 288 GB · 8,190 GB/s · Q8_0 2,373 tok/s
- 04 Radeon Instinct MI355X 288 GB · 8,190 GB/s · Q8_0 2,373 tok/s
- 05 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q8_0 1,898 tok/s
- 06 H200 NVL 141 GB · 4,890 GB/s · Q8_0 1,817 tok/s
- 07 H200 SXM 141 GB 141 GB · 4,890 GB/s · Q8_0 1,817 tok/s
- 08 Radeon Instinct MI325X 256 GB · 6,000 GB/s · Q8_0 1,739 tok/s
- 09 Radeon Instinct MI300A 128 GB · 5,325 GB/s · Q8_0 1,543 tok/s
- 10 Radeon Instinct MI300X 192 GB · 5,325 GB/s · Q8_0 1,543 tok/s
The smallest GPUs that still run SigLIP 2
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 1.9 GB · Q8_0 · comfortable 35.7 tok/s
- 02 RTX A400 4 GB · needs 1.9 GB · Q8_0 · comfortable 35.7 tok/s
- 03 RTX 500 Mobile Ada Generation 4 GB · needs 1.9 GB · Q8_0 · comfortable 47.6 tok/s
- 04 GeForce RTX 3050 A Mobile 4 GB · needs 1.9 GB · Q8_0 · comfortable 71.3 tok/s
- 05 Jetson Orin Nano 4 GB 4 GB · needs 1.9 GB · Q8_0 · comfortable 12.7 tok/s
- 06 Radeon RX 6450M 4 GB · needs 1.9 GB · Q8_0 · comfortable 37.1 tok/s
- 07 Radeon RX 6550M 4 GB · needs 1.9 GB · Q8_0 · comfortable 41.7 tok/s
- 08 Radeon RX 6550S 4 GB · needs 1.9 GB · Q8_0 · comfortable 37.1 tok/s
- 09 Arc A310 4 GB · needs 1.9 GB · Q8_0 · comfortable 29.9 tok/s
- 10 Arc Pro A30M 4 GB · needs 1.9 GB · Q8_0 · comfortable 30.9 tok/s
What the numbers mean
What you need to run it
Minimum card
Tesla C1080
Memory needed
1.9 GB
Fastest
2,972 tok/s
SigLIP 2 reaches a parameter count of 1.1B. That is small enough that hardware is rarely the obstacle, including on cards several years old. The number of cards we track that can run it: 818.
The least hardware that works is Tesla C1080, with a memory capacity of 4 GB, running it at a compression of Q8_0 and producing around 32.3 tokens per second.
Top of the range is B200, generating roughly 2,972 tokens per second on the strength of a memory bandwidth of 8,000 GB/s.
About this model
SigLIP 2 was published by Google DeepMind, in the country recorded as United States of America, during February 2025. The publishing organisation is categorised as industry.
It works in the domain of Vision, and is recorded as performing the task of image classification, Image embedding.
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. On Hugging Face it is published under the organisation google.
How fast it runs, and why
The median result is around 83.5 tokens per second. Producing text faster than most people read it: 799 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.
Training and provenance
Producing it required arithmetic totalling around 8.2 × 10²² FLOP, on hardware recorded as Google TPU v5e. That figure measures what producing the model cost, and has no bearing on how fast it answers.
Step by step
How to choose a GPU for SigLIP 2
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
Start from what it actually needs, which is the requirement of SigLIP 2, needing around 1.9 GB at a compression of Q8_0. That figure, not the headline performance of a card, 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 SigLIP 2.
-
03
Choose how far you will compress it
Compression is what makes a model fit smaller cards, at some cost in accuracy, reaching a compression of Q8_0 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
Sort by speed to see how cards rank for SigLIP 2. It will not match a gaming ordering, because generation is bound by memory bandwidth. The card topping the list is B200, at 2,972 tok/s.
-
05
Check the fit verdict before buying
The fit column separates cards that just manage it from those with room to spare, in the case of SigLIP 2. 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
Open the card you have settled on
Following a card through to its own page shows every other model it can hold, which is the question that follows once you have settled on SigLIP 2.
Answers
SigLIP 2 — common questions
SigLIP 2— when was it released?
It was published in February 2025.
SigLIP 2— what is it used for?
It works in the domain of Vision, and is recorded as handling the task of image classification, Image embedding. 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.
SigLIP 2— where can I download it?
Its weights are published on Hugging Face, under the organisation google. We do not host model files — this site calculates what hardware is needed to run them.
SigLIP 2— how much compute was used to train it?
Training consumed around 8.2 × 10²² FLOP, on hardware recorded as Google TPU v5e. 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.
SigLIP 2— can I run it 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 model is rarely worth using. Every figure here assumes the whole model is resident on the card.
SigLIP 2— would two GPUs run it faster?
A second card roughly doubles the memory available but not the generation rate. The number already able to run it alone: 818. So a second card is rarely the answer here.
SigLIP 2— 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: 1. Bigger cards get the more accurate version, and the quality floor above pins the comparison to one level.
SigLIP 2— how accurate are these speed estimates?
They are calculated from specifications rather than measured, and each carries a range. One example: 1,783–4,755 tok/s on B200. The same model and card vary by thirty to fifty per cent depending on the inference software and its version.
SigLIP 2— what GPU do I need to run it?
The smallest card in our catalogue that holds it is Tesla C1080, with a memory capacity of 4 GB. It runs the model at a compression of Q8_0 using about 1.9 GB, and produces roughly 32.3 tokens per second. The number of cards able to run it in total: 818.
SigLIP 2— how fast is it on a GPU?
It depends on the card. The quickest we calculate is B200, at about 2,972 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: 799.
SigLIP 2— how much VRAM does it need?
It needs about 1.9 GB at a compression of Q8_0, 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.
SigLIP 2— can I run it on a GPU holding 8 GB?
Yes. The card CMP 170HX 8 GB, holding 8 GB, runs it at a compression of Q8_0, using about 1.9 GB and generating roughly 554 tokens per second. The fit is comfortable.
SigLIP 2— can I run it on a GPU holding 12 GB?
Yes. The card GeForce RTX 3080 Ti, holding 12 GB, runs it at a compression of Q8_0, using about 1.9 GB and generating roughly 339 tokens per second. The fit is comfortable.
SigLIP 2— can I run it on a GPU holding 16 GB?
Yes. The card Tesla V100 SXM2 16 GB, holding 16 GB, runs it at a compression of Q8_0, using about 1.9 GB and generating roughly 420 tokens per second. The fit is comfortable.
SigLIP 2— can I run it on a GPU holding 24 GB?
Yes. The card GeForce RTX 5090 D V2, holding 24 GB, runs it at a compression of Q8_0, using about 1.9 GB and generating roughly 498 tokens per second. The fit is comfortable.
SigLIP 2— 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.
SigLIP 2— how many parameters does it have?
It has a parameter count of 1.1B. 1B. 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.
SigLIP 2— who created it?
It was published by Google DeepMind, based in United States of America, an organisation categorised as industry.
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.