stabilityai · image

stable-diffusion-3.5-large

stabilityai/stable-diffusion-3.5-large

stable-diffusion-3.5-large at Q4_0 is exactly 4,772,054,752 bytes (4.44 GiB / 4.77 GB) — an effective 4.686 bits per weight, not the nominal 4.

From the file· summed from 1 file(s)
Parameters
8.1B
Architecture
Context
native (config.json)
License
other

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
Q4_04.44 GiB4,772,054,7524.686calcuis
Q4_04.44 GiB4,772,054,7524.686923city96
Q4_14.91 GiB5,272,949,4725.178city96
Q4_14.91 GiB5,272,949,4725.178calcuis
Q5_05.38 GiB5,773,844,1925.670calcuis
Q5_05.38 GiB5,773,844,1925.670city96
Q5_15.84 GiB6,274,738,9126.162calcuis
Q5_15.84 GiB6,274,738,9126.162city96
Q4_02 shards7.32 GiB7,860,139,1367.719second-state
Q4_12 shards8.07 GiB8,666,904,0328.511second-state
Q8_08.18 GiB8,779,212,5128.622calcuis
Q8_08.18 GiB8,779,212,5128.622923city96
Q5_02 shards8.82 GiB9,473,669,2489.304second-state
Q5_12 shards9.57 GiB10,280,434,14410.096second-state
Q8_03 shards14.02 GiB15,052,808,51214.783second-state
F1615.17 GiB16,292,633,31216.000city96
F1615.17 GiB16,292,633,31216.000923calcuis

Pipeline components

a diffusion model is a graph of parts, not one file
ComponentSizeShareCan live on the CPU?
text encoder0.46 GiB1%yes — the usual first VRAM saving
text encoder 22.59 GiB7%yes — the usual first VRAM saving
text encoder 317.74 GiB49%yes — the usual first VRAM saving
vae0.16 GiB0%no, must be resident
denoiser15.33 GiB42%no, must be resident
Full pipeline36.28 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. This repository also ships a single-file copy of the denoiser at its root; we count it once, not twice.

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_0 at roughly 4.27 GiB. The real file is 4.44 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 stable-diffusion-3.5-large need?
Q4_0 is exactly 4,772,054,752 bytes (4.44 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
Which quantization of stable-diffusion-3.5-large 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.