nvidia · image

Cosmos-Predict2-2B-Text2Image

nvidia/Cosmos-Predict2-2B-Text2Image

Cosmos-Predict2-2B-Text2Image at Q4_K_M is exactly 16,049,921,632 bytes (14.95 GiB / 16.05 GB) — an effective 9.001 bits per weight, not the nominal 4.

From the file· summed from 8 file(s)
Parameters
14.3B
Architecture
pig
Context
native (config.json)
License
other

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
Q3_K_M8 shards11.52 GiB12,366,188,6406.935calcuis
Q4_K_M8 shards14.95 GiB16,049,921,6329.001calcuis
Q5_K_M8 shards18.18 GiB19,516,964,44810.945calcuis
Q2_K12 shards32.34 GiB34,729,181,53619.476calcuis
Q4_110 shards47.99 GiB51,533,681,44028.900calcuis
Q5_110 shards57.37 GiB61,595,874,080calcuis
Q4_017 shards65.28 GiB70,090,148,192calcuis
Q6_K12 shards65.66 GiB70,505,718,624calcuis
Q5_016 shards76.30 GiB81,925,395,520calcuis
Q8_018 shards120.91 GiB129,830,502,016calcuis

Pipeline components

a diffusion model is a graph of parts, not one file
ComponentSizeShareCan live on the CPU?
text encoder9.06 GiB69%yes — the usual first VRAM saving
vae0.47 GiB4%no, must be resident
denoiser3.64 GiB28%no, must be resident
Full pipeline13.18 GiBresident if nothing is offloaded

The parameter count published for a diffusion model describes the denoiser alone. Running it also requires its text encoder and VAE, and the text encoder is often nearly as large as the denoiser — which is why offloading it is the standard first move when you run out of memory.

We publish component sizes here, not throughput. Community-submitted image-generation rates do exist for many GPUs and we show them on the hardware pages, but they aggregate runs at different resolutions, step counts and settings, so they cannot be attributed to one model. Peak memory during sampling is unmeasured by any public source, and we do not estimate it.

Compare with

same modality, comparable size

Will it run on your card?

full quant x context sweep

Why other calculators give a different number

A parameters × bits ÷ 8 estimate puts Q4_K_M at roughly 7.47 GiB. The real file is 14.95 GiB, because a quantization is a mixture and some tensors are always kept at higher precision.

Architecture

Architecture unavailable — this repository is gated and no ungated mirror was found. Exact file sizes above are still authoritative; only the KV math needs the config.

Questions people ask

How much VRAM does Cosmos-Predict2-2B-Text2Image need?
Q4_K_M is exactly 16,049,921,632 bytes (14.95 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
Which quantization of Cosmos-Predict2-2B-Text2Image should I use?
Q4_K_M is the usual default. Pick the largest quantization that fits your card at the context you actually need — the table above gives exact sizes for every one published.