runwayml · image

stable-diffusion-v1-5

runwayml/stable-diffusion-v1-5

stable-diffusion-v1-5 at Q4_0 is exactly 1,566,768,416 bytes (1.46 GiB / 1.57 GB) — an effective 14.583 bits per weight, not the nominal 4.

From the file· summed from 1 file(s)
Parameters
860M
Architecture
Context
native (config.json)
License
creativeml-openrail-m

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
Q4_01.46 GiB1,566,768,41614.583second-state
Q4_11.48 GiB1,591,364,89614.812second-state
Q5_01.50 GiB1,615,967,90415.041second-state
Q5_11.53 GiB1,640,564,25615.270second-state
Q8_01.64 GiB1,763,578,17616.415second-state
F161.99 GiB2,132,586,94419.849second-state
F323.97 GiB4,265,059,488second-state

Pipeline components

a diffusion model is a graph of parts, not one file
ComponentSizeShareCan live on the CPU?
denoiser22.29 GiB91%no, must be resident
text encoder1.38 GiB6%yes — the usual first VRAM saving
vae0.94 GiB4%no, must be resident
Full pipeline24.60 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.

Measured

published by a third party, attributed below
MetricValueWhat it means
it/s7.7
it/s9.0
it/s8.5
it/s4.8
it/s5.1
it/s5.2
it/s6.0
it/s6.6
it/s6.8
it/s12.9
it/s12.1
it/s11.3
it/s2.6
it/s4.7
it/s4.1
it/s5.3
it/s2.8
it/s3.0
it/s27.2
it/s27.4
it/s34.9
Benchmarked· by vladmandic-sd-data-benchmark

Measured by a third party on their own hardware. We reproduce these figures with attribution; they are not ours and we have not verified the runs. Source: vladmandic-sd-data-benchmark.

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 0.45 GiB. The real file is 1.46 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-v1-5 need?
Q4_0 is exactly 1,566,768,416 bytes (1.46 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-v1-5 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.