SigLIP 400M 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 · 92.2 tok/s
Fastest card
B200
8,471 tok/s · 180 GB
Which GPUs can run SigLIP 400M?
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 | |||||
|---|---|---|---|---|---|---|---|
|
8,471
tok/s
5,082–13,553 · low confidence |
B200 NVIDIA | 180 GB | 8,000 GB/s | Jan 2024 | 1.1 GB | Q8_0 | Comfortable |
|
8,471
tok/s
5,082–13,553 · low confidence |
B300 NVIDIA | 288 GB | 8,000 GB/s | Sep 2025 | 1.1 GB | Q8_0 | Comfortable |
|
6,764
tok/s
4,058–10,822 · low confidence |
Radeon Instinct MI350X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 1.1 GB | Q8_0 | Comfortable |
|
6,764
tok/s
4,058–10,822 · low confidence |
Radeon Instinct MI355X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 1.1 GB | Q8_0 | Comfortable |
|
5,410
tok/s
3,246–8,655 · low confidence |
Radeon Instinct MI300 AMD | 128 GB | 6,550 GB/s | Jan 2023 | 1.1 GB | Q8_0 | Comfortable |
|
5,178
tok/s
3,107–8,284 · low confidence |
H200 NVL NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 1.1 GB | Q8_0 | Comfortable |
|
5,178
tok/s
3,107–8,284 · low confidence |
H200 SXM 141 GB NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 1.1 GB | Q8_0 | Comfortable |
|
4,955
tok/s
2,973–7,928 · low confidence |
Radeon Instinct MI325X AMD | 256 GB | 6,000 GB/s | Oct 2024 | 1.1 GB | Q8_0 | Comfortable |
|
4,398
tok/s
2,639–7,037 · low confidence |
Radeon Instinct MI300A AMD | 128 GB | 5,325 GB/s | Dec 2023 | 1.1 GB | Q8_0 | Comfortable |
|
4,398
tok/s
2,639–7,037 · low confidence |
Radeon Instinct MI300X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 1.1 GB | Q8_0 | Comfortable |
|
4,398
tok/s
2,639–7,037 · low confidence |
Radeon Instinct MI308X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 1.1 GB | Q8_0 | Comfortable |
|
4,172
tok/s
2,503–6,675 · low confidence |
H100 NVL 94 GB NVIDIA | 94 GB | 3,940 GB/s | Mar 2023 | 1.1 GB | Q8_0 | Comfortable |
|
3,558
tok/s
2,135–5,692 · low confidence |
H100 PCIe 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 1.1 GB | Q8_0 | Comfortable |
|
3,558
tok/s
2,135–5,692 · low confidence |
H100 SXM5 80 GB NVIDIA | 80 GB | 3,360 GB/s | Oct 2022 | 1.1 GB | Q8_0 | Comfortable |
|
3,558
tok/s
2,135–5,692 · low confidence |
H100 SXM5 94 GB NVIDIA | 94 GB | 3,360 GB/s | Mar 2023 | 1.1 GB | Q8_0 | Comfortable |
|
3,558
tok/s
2,135–5,692 · low confidence |
H100 SXM5 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 1.1 GB | Q8_0 | Comfortable |
|
3,558
tok/s
2,135–5,692 · low confidence |
H800 SXM5 NVIDIA | 80 GB | 3,360 GB/s | Mar 2023 | 1.1 GB | Q8_0 | Comfortable |
|
2,709
tok/s
1,625–4,334 · low confidence |
Radeon Instinct MI250 AMD | 128 GB | 3,280 GB/s | Nov 2021 | 1.1 GB | Q8_0 | Comfortable |
|
2,709
tok/s
1,625–4,334 · low confidence |
Radeon Instinct MI250X AMD | 128 GB | 3,280 GB/s | Nov 2021 | 1.1 GB | Q8_0 | Comfortable |
|
2,257
tok/s
1,354–3,612 · low confidence |
Data Center GPU Max 1550 Intel | 128 GB | 3,280 GB/s | Jan 2023 | 1.1 GB | Q8_0 | Comfortable |
|
2,209
tok/s
1,326–3,535 · low confidence |
Data Center GPU Max Subsystem Intel | 128 GB | 3,210 GB/s | Jan 2023 | 1.1 GB | Q8_0 | Comfortable |
|
2,160
tok/s
1,296–3,456 · low confidence |
A100 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Nov 2020 | 1.1 GB | Q8_0 | Comfortable |
|
2,160
tok/s
1,296–3,456 · low confidence |
A100X NVIDIA | 80 GB | 2,040 GB/s | Jun 2021 | 1.1 GB | Q8_0 | Comfortable |
|
2,160
tok/s
1,296–3,456 · low confidence |
A800 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Aug 2022 | 1.1 GB | Q8_0 | Comfortable |
|
2,160
tok/s
1,296–3,456 · low confidence |
H100 CNX NVIDIA | 80 GB | 2,040 GB/s | Mar 2023 | 1.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 DeepMind
- Organisation type
- Industry
- Country
- United States of America
- Published
- 27 March 2023
- Authors
- Xiaohua Zhai, Basil Mustafa, Alexander Kolesnikov, Lucas Beyer
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
- 400M
- Training data
- 6,705,000,000,000 tokens
- Batch size
- 32,000
Table 3
"B/16 ViT for image embeddings and B-sized transformer for text embeddings. The input images are resized to 224×224 resolution." "SigLIP performs best at batch size 32 k [image-text pairs]" 729 patches (table 3) "a maximum of 16 text tokens are kept" 9B examples * (16 text tokens + 729 image tokens) = 6.705e+12 total training tokens
From Table 1: SigLit and SigLIP results
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.9 × 10²¹ FLOP
- How it was established
- Hardware,Operation counting
Operation Counting: 6ND = 6 FLOP / token / parameter*400*10^6 parameters * 6705000000000 tokens [see Dataset size notes] = 1.6092e+22 FLOP Hardware: 275000000000000 FLOP/s/GPU * 32 GPUs * 120 hours * 3600 sec / hour * 0.4 = 1.52064e+21 FLOPs geometric mean (1.6092e+22, 1.52064e+21) = 4.9467301e+21
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
- 32
- Chip-hours
- 3,840
- Wall-clock time
- 120 hours
- Power draw
- 21.7 kW
5 days = 120 hours
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
Apache2 license https://github.com/google-research/big_vision https://colab.research.google.com/github/google-research/big_vision/blob/main/big_vision/configs/proj/image_text/SigLIP_demo.ipynb code release is still pending as "TODO"
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
- Significant use
- Record confidence
- Confident
Sources
Where this record came from and when it was last checked.
- Reference
- Sigmoid Loss for Language Image Pre-Training
- Last updated
- 28 November 2025
The extremes
The ten fastest GPUs that run SigLIP 400M
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 8,471 tok/s
- 02 B200 180 GB · 8,000 GB/s · Q8_0 8,471 tok/s
- 03 Radeon Instinct MI350X 288 GB · 8,190 GB/s · Q8_0 6,764 tok/s
- 04 Radeon Instinct MI355X 288 GB · 8,190 GB/s · Q8_0 6,764 tok/s
- 05 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q8_0 5,410 tok/s
- 06 H200 NVL 141 GB · 4,890 GB/s · Q8_0 5,178 tok/s
- 07 H200 SXM 141 GB 141 GB · 4,890 GB/s · Q8_0 5,178 tok/s
- 08 Radeon Instinct MI325X 256 GB · 6,000 GB/s · Q8_0 4,955 tok/s
- 09 Radeon Instinct MI300A 128 GB · 5,325 GB/s · Q8_0 4,398 tok/s
- 10 Radeon Instinct MI300X 192 GB · 5,325 GB/s · Q8_0 4,398 tok/s
The smallest GPUs that still run SigLIP 400M
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.1 GB · Q8_0 · comfortable 102 tok/s
- 02 RTX A400 4 GB · needs 1.1 GB · Q8_0 · comfortable 102 tok/s
- 03 RTX 500 Mobile Ada Generation 4 GB · needs 1.1 GB · Q8_0 · comfortable 136 tok/s
- 04 GeForce RTX 3050 A Mobile 4 GB · needs 1.1 GB · Q8_0 · comfortable 203 tok/s
- 05 Jetson Orin Nano 4 GB 4 GB · needs 1.1 GB · Q8_0 · comfortable 36.1 tok/s
- 06 Radeon RX 6450M 4 GB · needs 1.1 GB · Q8_0 · comfortable 106 tok/s
- 07 Radeon RX 6550M 4 GB · needs 1.1 GB · Q8_0 · comfortable 119 tok/s
- 08 Radeon RX 6550S 4 GB · needs 1.1 GB · Q8_0 · comfortable 106 tok/s
- 09 Arc A310 4 GB · needs 1.1 GB · Q8_0 · comfortable 85.3 tok/s
- 10 Arc Pro A30M 4 GB · needs 1.1 GB · Q8_0 · comfortable 88.1 tok/s
What the numbers mean
What you need to run it
Minimum card
Tesla C1080
Memory needed
1.1 GB
Fastest
8,471 tok/s
SigLIP 400M is small enough at 400M 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 92.2 tokens per second.
A B200 is the fastest we calculate for it: about 8,471 tokens per second, from 8,000 GB/s of memory bandwidth.
Background
SigLIP 400M was published by Google DeepMind, in United States of America, in March 2023. industry is the category the publisher falls under.
It works in Vision, and is recorded as doing image classification, Image embedding.
The weights are published, so it can be downloaded and run on your own hardware indefinitely, offline, with no account attached.
Reading the throughput figures
Half the cards that hold it manage more than 237.9 tokens per second, and 817 exceed reading speed outright.
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
The training run consumed about 4.9 × 10²¹ FLOP, on Google TPU v4. That figure describes the cost of creating it and has no bearing on how quickly it generates text.
The training set ran to roughly 6,705,000,000,000 tokens.
It is tracked in the underlying dataset for one reason in particular: significant use.
Step by step
How to choose a GPU for SigLIP 400M
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 SigLIP 400M — around 1.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
Set the context to what you will actually use. The cache grows with the conversation, and it is the usual reason SigLIP 400M stops fitting a card that seemed fine.
-
03
Decide how much compression you will accept
Each card runs the least-compressed copy it can hold — Q8_0 on the smallest card that fits. Setting a floor drops the cards that only manage SigLIP 400M by squeezing it further than you would want.
-
04
Sort by speed
The speed ordering for SigLIP 400M is effectively an ordering by memory bandwidth, which is why the B200 tops it at 8,471 tok/s.
-
05
Check the fit verdict before buying
The fit column separates cards that just manage SigLIP 400M from those with room to spare. Buy for the second if the context might grow.
-
06
Check the card from the other side
Each card page repeats this sweep for every model we hold. It answers what else the hardware is good for, beyond SigLIP 400M.
Answers
SigLIP 400M — common questions
How many parameters does SigLIP 400M have?
SigLIP 400M has 400M parameters. Table 3. 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 SigLIP 400M?
SigLIP 400M was published by Google DeepMind, based in United States of America, categorised as industry.
When was SigLIP 400M released?
SigLIP 400M was published in March 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 SigLIP 400M used for?
SigLIP 400M works in Vision, and is recorded as handling image classification, Image embedding. Models frequently carry more than one of each, and the tags describe purpose rather than capability limits.
Where can I download SigLIP 400M?
The weights for SigLIP 400M 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 SigLIP 400M?
Around 4.9 × 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.
Can I run SigLIP 400M 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 SigLIP 400M is rarely worth using. Every figure here assumes the whole model is on the card.
Would two GPUs run SigLIP 400M faster?
A second card roughly doubles the memory available but not the generation rate. With 818 cards already able to run SigLIP 400M alone, the case for pairing is weak.
Why does the quantisation differ between cards for SigLIP 400M?
A larger card holds a more accurate copy. Across the cards that run SigLIP 400M, 1 compression levels are used; the floor control above pins it to one.
How accurate are these SigLIP 400M 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 5,082–13,553 tok/s on the B200 rather than a single number.
What GPU do I need to run SigLIP 400M?
The smallest card in our catalogue that holds SigLIP 400M is the Tesla C1080, with 4 GB of memory. It runs the model at Q8_0 using about 1.1 GB, and produces roughly 92.2 tokens per second. 818 cards in total can run it.
How fast is SigLIP 400M on a GPU?
It depends on the card. The quickest we calculate is a B200 at about 8,471 tokens per second; the slowest that still runs it manages considerably less. Reading speed is around ten tokens per second, and 817 of the cards that can run SigLIP 400M clear that.
How much VRAM does SigLIP 400M need?
About 1.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 SigLIP 400M on a 8 GB GPU?
Yes. A CMP 170HX 8 GB with 8 GB runs it at Q8_0, using about 1.1 GB and generating roughly 1,578 tokens per second — a comfortable fit.
Can I run SigLIP 400M on a 12 GB GPU?
Yes. A GeForce RTX 3080 Ti with 12 GB runs it at Q8_0, using about 1.1 GB and generating roughly 966 tokens per second — a comfortable fit.
Can I run SigLIP 400M on a 16 GB GPU?
Yes. A Tesla V100 SXM2 16 GB with 16 GB runs it at Q8_0, using about 1.1 GB and generating roughly 1,196 tokens per second — a comfortable fit.
Can I run SigLIP 400M on a 24 GB GPU?
Yes. A GeForce RTX 5090 D V2 with 24 GB runs it at Q8_0, using about 1.1 GB and generating roughly 1,419 tokens per second — a comfortable fit.
Is SigLIP 400M open source?
Its weights are published, so SigLIP 400M 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.
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.