Command A Vision 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
Radeon Instinct MI200
64 GB · Q3_K_M · 13.1 tok/s
Fastest card
B200
30.3 tok/s · 180 GB
Which GPUs can run Command A Vision?
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.
43 cards match
Calculating| Needs | Quantisation | Fit | |||||
|---|---|---|---|---|---|---|---|
|
30.3
tok/s
18–48 · low confidence |
B200 NVIDIA | 180 GB | 8,000 GB/s | Jan 2024 | 120.6 GB | Q8_0 | Comfortable |
|
30.3
tok/s
18–48 · low confidence |
B300 NVIDIA | 288 GB | 8,000 GB/s | Sep 2025 | 120.6 GB | Q8_0 | Comfortable |
|
29.3
tok/s
18–47 · low confidence |
H100 SXM5 80 GB NVIDIA | 80 GB | 3,360 GB/s | Oct 2022 | 68.5 GB | Q4_K_M | Tight |
|
29.3
tok/s
18–47 · low confidence |
H800 SXM5 NVIDIA | 80 GB | 3,360 GB/s | Mar 2023 | 68.5 GB | Q4_K_M | Tight |
|
28.1
tok/s
17–45 · low confidence |
Radeon Instinct MI300 AMD | 128 GB | 6,550 GB/s | Jan 2023 | 94.5 GB | Q6_K | Comfortable |
|
26.6
tok/s
16–43 · low confidence |
H100 NVL 94 GB NVIDIA | 94 GB | 3,940 GB/s | Mar 2023 | 81.5 GB | Q5_K_M | Tight |
|
24.2
tok/s
14–39 · low confidence |
Radeon Instinct MI350X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 120.6 GB | Q8_0 | Comfortable |
|
24.2
tok/s
14–39 · low confidence |
Radeon Instinct MI355X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 120.6 GB | Q8_0 | Comfortable |
|
22.8
tok/s
14–37 · low confidence |
Radeon Instinct MI300A AMD | 128 GB | 5,325 GB/s | Dec 2023 | 94.5 GB | Q6_K | Comfortable |
|
22.7
tok/s
14–36 · low confidence |
H100 PCIe 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 81.5 GB | Q5_K_M | Tight |
|
22.7
tok/s
14–36 · low confidence |
H100 SXM5 94 GB NVIDIA | 94 GB | 3,360 GB/s | Mar 2023 | 81.5 GB | Q5_K_M | Tight |
|
22.7
tok/s
14–36 · low confidence |
H100 SXM5 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 81.5 GB | Q5_K_M | Tight |
|
20.6
tok/s
12–33 · low confidence |
H100 SXM5 64 GB NVIDIA | 64 GB | 2,020 GB/s | Mar 2023 | 55.4 GB | Q3_K_M | Tight |
|
18.5
tok/s
11–30 · low confidence |
H200 NVL NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 120.6 GB | Q8_0 | Tight |
|
18.5
tok/s
11–30 · low confidence |
H200 SXM 141 GB NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 120.6 GB | Q8_0 | Tight |
|
17.8
tok/s
11–29 · low confidence |
A100 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Nov 2020 | 68.5 GB | Q4_K_M | Tight |
|
17.8
tok/s
11–29 · low confidence |
A100X NVIDIA | 80 GB | 2,040 GB/s | Jun 2021 | 68.5 GB | Q4_K_M | Tight |
|
17.8
tok/s
11–29 · low confidence |
A800 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Aug 2022 | 68.5 GB | Q4_K_M | Tight |
|
17.8
tok/s
11–29 · low confidence |
H100 CNX NVIDIA | 80 GB | 2,040 GB/s | Mar 2023 | 68.5 GB | Q4_K_M | Tight |
|
17.8
tok/s
11–29 · low confidence |
H100 PCIe 80 GB NVIDIA | 80 GB | 2,040 GB/s | Oct 2022 | 68.5 GB | Q4_K_M | Tight |
|
17.8
tok/s
11–29 · low confidence |
H800 PCIe 80 GB NVIDIA | 80 GB | 2,040 GB/s | Mar 2023 | 68.5 GB | Q4_K_M | Tight |
|
17.7
tok/s
11–28 · low confidence |
Radeon Instinct MI325X AMD | 256 GB | 6,000 GB/s | Oct 2024 | 120.6 GB | Q8_0 | Comfortable |
|
16.9
tok/s
10–27 · low confidence |
A100 PCIe 80 GB NVIDIA | 80 GB | 1,940 GB/s | Jun 2021 | 68.5 GB | Q4_K_M | Tight |
|
16.9
tok/s
10–27 · low confidence |
A800 PCIe 80 GB NVIDIA | 80 GB | 1,940 GB/s | Nov 2022 | 68.5 GB | Q4_K_M | Tight |
|
15.7
tok/s
9–25 · low confidence |
Radeon Instinct MI300X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 120.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
- Cohere
- Organisation type
- Industry
- Country
- Canada
- Published
- 31 July 2025
What it does
The problem areas the model was built for. A model can carry several of each.
- Domain
- Vision, Multimodal, Language
- Task
- Visual question answering, Character recognition (OCR), Language modeling/generation, Question answering
- Base model
- Cohere Command A,SigLIP 2
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
- 112B
- Training data
- tokens
112B This is a vision-language model that uses a language model based on Command A paired with the SigLIP2-patch16-512 vision encoder through a multimodal adapter for vision-language understanding.
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 (non-commercial)
- Training code
- Unreleased
- Hugging Face
- CohereLabs
cc-by-nc-4.0 https://huggingface.co/CohereLabs/command-a-vision-07-2025
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
- Introducing Command A Vision: Multimodal AI built for business
- Last updated
- 28 November 2025
The extremes
The ten fastest GPUs that run Command A Vision
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 30.3 tok/s
- 02 B200 180 GB · 8,000 GB/s · Q8_0 30.3 tok/s
- 03 H800 SXM5 80 GB · 3,360 GB/s · Q4_K_M 29.3 tok/s
- 04 H100 SXM5 80 GB 80 GB · 3,360 GB/s · Q4_K_M 29.3 tok/s
- 05 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q6_K 28.1 tok/s
- 06 H100 NVL 94 GB 94 GB · 3,940 GB/s · Q5_K_M 26.6 tok/s
- 07 Radeon Instinct MI350X 288 GB · 8,190 GB/s · Q8_0 24.2 tok/s
- 08 Radeon Instinct MI355X 288 GB · 8,190 GB/s · Q8_0 24.2 tok/s
- 09 Radeon Instinct MI300A 128 GB · 5,325 GB/s · Q6_K 22.8 tok/s
- 10 H100 PCIe 96 GB 96 GB · 3,360 GB/s · Q5_K_M 22.7 tok/s
The smallest GPUs that still run Command A Vision
The cheapest route in, by memory capacity. A tight fit runs the model but leaves nothing spare for a longer conversation.
- 01 Jetson T4000 64 GB · needs 55.4 GB · Q3_K_M · tight 2.8 tok/s
- 02 H100 SXM5 64 GB 64 GB · needs 55.4 GB · Q3_K_M · tight 20.6 tok/s
- 03 Jetson AGX Orin 64 GB 64 GB · needs 55.4 GB · Q3_K_M · tight 2.1 tok/s
- 04 Radeon Instinct MI200 64 GB · needs 55.4 GB · Q3_K_M · tight 13.1 tok/s
- 05 Radeon Instinct MI210 64 GB · needs 55.4 GB · Q3_K_M · tight 13.1 tok/s
- 06 RTX PRO 5000 72 GB Blackwell 72 GB · needs 61.9 GB · IQ4_XS · tight 12.4 tok/s
- 07 H100 CNX 80 GB · needs 68.5 GB · Q4_K_M · tight 17.8 tok/s
- 08 H800 PCIe 80 GB 80 GB · needs 68.5 GB · Q4_K_M · tight 17.8 tok/s
- 09 H800 SXM5 80 GB · needs 68.5 GB · Q4_K_M · tight 29.3 tok/s
- 10 A800 PCIe 80 GB 80 GB · needs 68.5 GB · Q4_K_M · tight 16.9 tok/s
What the numbers mean
What it takes to run this model
Minimum card
Radeon Instinct MI200
Memory needed
55.4 GB
Fastest
30.3 tok/s
Command A Vision reaches a parameter count of 112B. That puts it above consumer hardware, into the range where a card is bought for this purpose rather than repurposed for it. The number of cards we track that can hold it: 43.
The smallest card that holds it is Radeon Instinct MI200, with a memory capacity of 64 GB, running it at a compression of Q3_K_M and producing around 13.1 tokens per second.
Top of the range is B200, generating roughly 30.3 tokens per second on the strength of a memory bandwidth of 8,000 GB/s.
Where it came from
Command A Vision was published by Cohere, in the country recorded as Canada, during July 2025. It comes out of an organisation categorised as industry.
It works in the domain of Vision, Multimodal, Language, and is recorded as performing the task of visual question answering, Character recognition (OCR), Language modeling/generation, Question answering.
Rather than being trained from scratch, it is derived from Cohere Command A,SigLIP 2. That is why it shares the base 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. On Hugging Face it is published under the organisation CohereLabs.
Understanding the speeds
Half the cards that hold it manage more than 17.7 tokens per second. Producing text faster than most people read it: 39 of them.
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.
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.
Step by step
How to choose a GPU for Command A Vision
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
Every card here has been checked against Command A Vision, needing around 55.4 GB at a compression of Q3_K_M. That figure, not the headline performance of a card, 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 a card that seemed fine stops fitting Command A Vision.
-
03
Choose how far you will compress it
The quantisation column varies by card, because a bigger card holds a more accurate copy, reaching a compression of Q3_K_M 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
Compare tokens per second, not specifications
Sort by speed to see how cards rank for Command A Vision. It will not match a gaming ordering, because generation is bound by memory bandwidth. The card topping the list is B200, at 30.3 tok/s.
-
05
Read the fit column last
A tight fit runs, but leaves nothing spare for a longer conversation, in the case of Command A Vision. 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
See what else that card runs
Each card page repeats this sweep for every model we hold, answering what else the hardware is good for beyond Command A Vision.
Answers
Command A Vision — common questions
Command A Vision— when was it released?
It was published in July 2025.
Command A Vision— what is it used for?
It works in the domain of Vision, Multimodal, Language, and is recorded as handling the task of visual question answering, Character recognition (OCR), Language modeling/generation, Question answering. Models frequently carry more than one of each, and the tags describe purpose rather than capability limits.
Command A Vision— where can I download it?
Its weights are published on Hugging Face, under the organisation CohereLabs. We do not host model files — this site calculates what hardware is needed to run them.
Command A Vision— 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. The nearest miss we calculate falls short by 25.3 GB. Every figure here assumes the whole model is resident on the card.
Command A Vision— 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: 43. So a second card is rarely the answer here.
Command A Vision— why does the quantisation differ between cards?
Because capacity varies, so does how hard it has to be squeezed. The number of distinct levels in the table above: 6. Bigger cards get the more accurate version, and the quality floor above pins the comparison to one level.
Command A Vision— how accurate are these speed estimates?
These are estimates with real error bars, and any of them could reasonably land anywhere in its published range depending on which runtime you use. The fastest result here: 18–48 tok/s on B200. The same model and card vary by thirty to fifty per cent depending on the inference software and its version.
Command A Vision— what GPU do I need to run it?
The smallest card in our catalogue that holds it is Radeon Instinct MI200, with a memory capacity of 64 GB. It runs the model at a compression of Q3_K_M using about 55.4 GB, and produces roughly 13.1 tokens per second. The number of cards able to run it in total: 43.
Command A Vision— how fast is it on a GPU?
It depends on the card. The quickest we calculate is B200, at about 30.3 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: 39.
Command A Vision— how much VRAM does it need?
It needs about 55.4 GB at a compression of Q3_K_M, 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.
Command A Vision— 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.
Command A Vision— how many parameters does it have?
It has a parameter count of 112B. 112B This is a vision-language model that uses a language model based on Command A paired with the SigLIP2-patch16-512 vision encoder through a multimodal adapter for vision-language understanding. 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.
Command A Vision— who created it?
It was published by Cohere, based in Canada, 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.