Cosmos-Transfer1-7B TPS calculator

Open weights NVIDIA 7B parameters March 2025

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

589 cards that can run it

818 cards we hold specifications for

Smallest card that fits

Tesla K20c

5 GB · Q3_K_M · 28.9 tok/s

Fastest card

B200

484 tok/s · 180 GB

Which GPUs can run Cosmos-Transfer1-7B?

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.

589 cards match

Calculating
Needs Quantisation Fit
484 tok/s

290–774 · low confidence

B200 NVIDIA 180 GB 8,000 GB/s Jan 2024 8.2 GB Q8_0 Comfortable
484 tok/s

290–774 · low confidence

B300 NVIDIA 288 GB 8,000 GB/s Sep 2025 8.2 GB Q8_0 Comfortable
387 tok/s

232–618 · low confidence

Radeon Instinct MI350X AMD 288 GB 8,190 GB/s Jan 2025 8.2 GB Q8_0 Comfortable
387 tok/s

232–618 · low confidence

Radeon Instinct MI355X AMD 288 GB 8,190 GB/s Jan 2025 8.2 GB Q8_0 Comfortable
309 tok/s

185–495 · low confidence

Radeon Instinct MI300 AMD 128 GB 6,550 GB/s Jan 2023 8.2 GB Q8_0 Comfortable
296 tok/s

178–473 · low confidence

H200 NVL NVIDIA 141 GB 4,890 GB/s Nov 2024 8.2 GB Q8_0 Comfortable
296 tok/s

178–473 · low confidence

H200 SXM 141 GB NVIDIA 141 GB 4,890 GB/s Nov 2024 8.2 GB Q8_0 Comfortable
283 tok/s

170–453 · low confidence

Radeon Instinct MI325X AMD 256 GB 6,000 GB/s Oct 2024 8.2 GB Q8_0 Comfortable
251 tok/s

151–402 · low confidence

Radeon Instinct MI300A AMD 128 GB 5,325 GB/s Dec 2023 8.2 GB Q8_0 Comfortable
251 tok/s

151–402 · low confidence

Radeon Instinct MI300X AMD 192 GB 5,325 GB/s Dec 2023 8.2 GB Q8_0 Comfortable
251 tok/s

151–402 · low confidence

Radeon Instinct MI308X AMD 192 GB 5,325 GB/s Dec 2023 8.2 GB Q8_0 Comfortable
238 tok/s

143–381 · low confidence

H100 NVL 94 GB NVIDIA 94 GB 3,940 GB/s Mar 2023 8.2 GB Q8_0 Comfortable
203 tok/s

122–325 · low confidence

H100 PCIe 96 GB NVIDIA 96 GB 3,360 GB/s Mar 2023 8.2 GB Q8_0 Comfortable
203 tok/s

122–325 · low confidence

H100 SXM5 80 GB NVIDIA 80 GB 3,360 GB/s Oct 2022 8.2 GB Q8_0 Comfortable
203 tok/s

122–325 · low confidence

H100 SXM5 94 GB NVIDIA 94 GB 3,360 GB/s Mar 2023 8.2 GB Q8_0 Comfortable
203 tok/s

122–325 · low confidence

H100 SXM5 96 GB NVIDIA 96 GB 3,360 GB/s Mar 2023 8.2 GB Q8_0 Comfortable
203 tok/s

122–325 · low confidence

H800 SXM5 NVIDIA 80 GB 3,360 GB/s Mar 2023 8.2 GB Q8_0 Comfortable
155 tok/s

93–248 · low confidence

Radeon Instinct MI250 AMD 128 GB 3,280 GB/s Nov 2021 8.2 GB Q8_0 Comfortable
155 tok/s

93–248 · low confidence

Radeon Instinct MI250X AMD 128 GB 3,280 GB/s Nov 2021 8.2 GB Q8_0 Comfortable
131 tok/s

79–210 · low confidence

CMP 170HX 8 GB NVIDIA 8 GB 1,490 GB/s Sep 2021 6.6 GB Q6_K Tight
129 tok/s

77–206 · low confidence

Data Center GPU Max 1550 Intel 128 GB 3,280 GB/s Jan 2023 8.2 GB Q8_0 Comfortable
126 tok/s

76–202 · low confidence

Data Center GPU Max Subsystem Intel 128 GB 3,210 GB/s Jan 2023 8.2 GB Q8_0 Comfortable
123 tok/s

74–197 · low confidence

A100 SXM4 80 GB NVIDIA 80 GB 2,040 GB/s Nov 2020 8.2 GB Q8_0 Comfortable
123 tok/s

74–197 · low confidence

A100X NVIDIA 80 GB 2,040 GB/s Jun 2021 8.2 GB Q8_0 Comfortable
123 tok/s

74–197 · low confidence

A800 SXM4 80 GB NVIDIA 80 GB 2,040 GB/s Aug 2022 8.2 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
NVIDIA
Organisation type
Industry
Country
United States of America
Published
18 March 2025
Authors
NVIDIA: Hassan Abu Alhaija, Jose Alvarez, Maciej Bala, Tiffany Cai, Tianshi Cao, Liz Cha, Joshua Chen, Mike Chen, Francesco Ferroni, Sanja Fidler, Dieter Fox, Yunhao Ge, Jinwei Gu, Ali Hassani, Michael Isaev, Pooya Jannaty, Shiyi Lan, Tobias Lasser, Huan Ling, Ming-Yu Liu, Xian Liu, Yifan Lu, Alice Luo, Qianli Ma, Hanzi Mao, Fabio Ramos, Xuanchi Ren, Tianchang Shen, Xinglong Sun, Shitao Tang, Ting…

What it does

The problem areas the model was built for. A model can carry several of each.

Domain
Video, Vision, Robotics
Task
Robotic manipulation, System control, Video generation
Base model
Cosmos-Predict1-7b-Video2World

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
7B

7B

Training data
tokens

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
3.6 × 10²⁴ FLOP

1.4e+24 FLOP [base model compute] + 2.205901651968e+24 FLOP = 3.6059017e+24 FLOP

How it was established
Hardware
Fine-tuning compute
2.2 × 10²⁴ FLOP

989400000000000 FLOP/GPU/sec * 2016 hours ["Likely" confidence, see training time notes] * 3600 sec / hour * 1024 GPUs * 0.3 [assumed utilization] = 2.205901651968e+24 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
NVIDIA H100 SXM5 80GB
Chips used
1,024
Wall-clock time
2,016 hours (84 days)

"We train each control branch with 1024 NVIDIA H100 GPUs for a period of 2 to 4 weeks depending on the modality" 4 modalities -> ~12 weeks of total training = 2016 hours

Power draw
1.4 MW

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 (restricted use)
Training code
Unreleased

NVIDIA license (termination clause + attribution requirements) https://huggingface.co/nvidia/Cosmos-Transfer1-7B

Hugging Face
nvidia

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
Cosmos-Transfer1: Conditional World Generation with Adaptive Multimodal Control
Last updated
28 November 2025

The extremes

What the numbers mean

Hardware requirements in practice

Minimum card

Tesla K20c

Memory needed

4.1 GB

Fastest

484 tok/s

Cosmos-Transfer1-7B reaches a parameter count of 7B. 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: 589.

The entry point is Tesla K20c, with a memory capacity of 5 GB, running it at a compression of Q3_K_M and producing around 28.9 tokens per second.

At the other end sits B200, generating roughly 484 tokens per second on the strength of a memory bandwidth of 8,000 GB/s.

What this model is

Cosmos-Transfer1-7B was published by NVIDIA, in the country recorded as United States of America, during March 2025. The category the publisher falls under is industry.

It works in the domain of Video, Vision, Robotics, and is recorded as performing the task of robotic manipulation, System control, Video generation.

It builds on Cosmos-Predict1-7b-Video2World. Most models at this scale are adapted from an existing base rather than built from nothing.

Because its weights were released, nothing about running it depends on a provider staying available — it is yours once downloaded. On Hugging Face it is published under the organisation nvidia.

What decides the speed

Half the cards that hold it manage more than 26.1 tokens per second. Producing text faster than most people read it: 559 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 3.6 × 10²⁴ FLOP, on hardware recorded as NVIDIA H100 SXM5 80GB. 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 Cosmos-Transfer1-7B

The table above has already assessed every card we hold specifications for against this model. Getting to your answer takes six steps.

  1. 01

    Check what it needs before anything else

    The table lists every card able to hold Cosmos-Transfer1-7B, needing around 4.1 GB at a compression of Q3_K_M. Capacity is the gate — a card either holds it or it does not.

  2. 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 a card that seemed fine stops fitting Cosmos-Transfer1-7B.

  3. 03

    Set a quality floor

    Compression is what makes a model fit smaller cards, at some cost in accuracy, 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.

  4. 04

    Rank by throughput rather than spec sheet

    The speed ordering is effectively an ordering by memory bandwidth, for Cosmos-Transfer1-7B. It will not match a gaming ordering, because generation is bound by memory bandwidth. The card topping the list is B200, at 484 tok/s.

  5. 05

    Check the fit verdict before buying

    A tight fit runs, but leaves nothing spare for a longer conversation, in the case of Cosmos-Transfer1-7B. 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.

  6. 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 Cosmos-Transfer1-7B.

Answers

Cosmos-Transfer1-7B — common questions

01

Cosmos-Transfer1-7B— how accurate are these speed estimates?

Every figure is derived from memory bandwidth and model size, not benchmarked, which is why each is published as a range rather than a single number. One example: 290–774 tok/s on B200. The same model and card vary by thirty to fifty per cent depending on the inference software and its version.

02

Cosmos-Transfer1-7B— what GPU do I need to run it?

The smallest card in our catalogue that holds it is Tesla K20c, with a memory capacity of 5 GB. It runs the model at a compression of Q3_K_M using about 4.1 GB, and produces roughly 28.9 tokens per second. The number of cards able to run it in total: 589.

03

Cosmos-Transfer1-7B— how fast is it on a GPU?

It depends on the card. The quickest we calculate is B200, at about 484 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: 559.

04

Cosmos-Transfer1-7B— how much VRAM does it need?

It needs about 4.1 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.

05

Cosmos-Transfer1-7B— 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 Q6_K, using about 6.6 GB and generating roughly 131 tokens per second. The fit is tight.

06

Cosmos-Transfer1-7B— 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 8.2 GB and generating roughly 55.2 tokens per second. The fit is comfortable.

07

Cosmos-Transfer1-7B— 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 8.2 GB and generating roughly 68.4 tokens per second. The fit is comfortable.

08

Cosmos-Transfer1-7B— 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 8.2 GB and generating roughly 81.1 tokens per second. The fit is comfortable.

09

Cosmos-Transfer1-7B— 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.

10

Cosmos-Transfer1-7B— how many parameters does it have?

It has a parameter count of 7B. 7B. 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.

11

Cosmos-Transfer1-7B— who created it?

It was published by NVIDIA, based in United States of America, an organisation categorised as industry.

12

Cosmos-Transfer1-7B— when was it released?

It was published in March 2025.

13

Cosmos-Transfer1-7B— what is it used for?

It works in the domain of Video, Vision, Robotics, and is recorded as handling the task of robotic manipulation, System control, Video generation. Models frequently carry more than one of each, and the tags describe purpose rather than capability limits.

14

Cosmos-Transfer1-7B— where can I download it?

Its weights are published on Hugging Face, under the organisation nvidia. We do not host model files — this site calculates what hardware is needed to run them.

15

Cosmos-Transfer1-7B— how much compute was used to train it?

Training consumed around 3.6 × 10²⁴ FLOP, on hardware recorded as NVIDIA H100 SXM5 80GB. 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.

16

Cosmos-Transfer1-7B— 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 1.3 GB. Every figure here assumes the whole model is resident on the card.

17

Cosmos-Transfer1-7B— 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: 589. So a second card is rarely the answer here.

18

Cosmos-Transfer1-7B— 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: 4. Bigger cards get the more accurate version, and the quality floor above pins the comparison to one level.

Source

Original publication

Record last updated 28 November 2025

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.