baidu · image

ERNIE-Image

baidu/ERNIE-Image

ERNIE-Image at Q4_K_M is exactly 2,146,489,664 bytes (2.00 GiB / 2.15 GB) — an effective 2.138 bits per weight, not the nominal 4.

From the file· summed from 1 file(s)
Parameters
8.0B
Architecture
wan
Context
native (config.json)
License
apache-2.0

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
Q4_K_M2.00 GiB2,146,489,6642.138ponpoke
Q4_K_M2.00 GiB2,146,490,2082.138ponpoke
Q4_K_M2.21 GiB2,372,982,6882.363Green-Sky
Q5_K_M2.56 GiB2,750,470,0482.739Green-Sky
Q6_K2.63 GiB2,821,248,3202.809ponpoke
Q6_K2.63 GiB2,821,248,8642.809ponpoke
Q2_K2.96 GiB3,178,545,8563.165unsloth
Q8_03.40 GiB3,651,671,3603.636ponpoke
Q8_03.40 GiB3,651,671,9043.636ponpoke
Q3_K_S3.57 GiB3,834,135,2323.818unsloth
Q3_K_M3.64 GiB3,909,632,7043.893unsloth
UD-Q2_K3.69 GiB3,967,337,1523.951unsloth
Q8_03.80 GiB4,079,490,9764.063Green-Sky
Q4_04.44 GiB4,762,747,5844.743unsloth
UD-Q3_K_M4.45 GiB4,780,606,1444.761unsloth
Q4_K_S4.54 GiB4,875,993,7924.856unsloth
Q4_K_M4.67 GiB5,019,124,4164.998unsloth
Q4_14.89 GiB5,254,267,5845.232unsloth
Q5_05.35 GiB5,745,787,5845.722unsloth
UD-Q4_K_M5.38 GiB5,774,754,4965.751unsloth
Q5_K_S5.46 GiB5,861,655,2325.837unsloth
Q5_K_M5.53 GiB5,932,958,4005.908unsloth
Q5_15.81 GiB6,237,307,5846.211unsloth
UD-Q5_K_M6.27 GiB6,732,235,4566.704unsloth
Q6_K6.32 GiB6,790,267,5846.762unsloth
BF167.14 GiB7,671,519,1367.639Green-Sky
Q8_08.10 GiB8,694,907,5848.659unsloth
BF1614.96 GiB16,067,707,58416.001unsloth
F1614.96 GiB16,067,707,58416.001unsloth

Pipeline components

a diffusion model is a graph of parts, not one file
ComponentSizeShareCan live on the CPU?
text encoder7.17 GiB32%yes — the usual first VRAM saving
vae0.16 GiB1%no, must be resident
denoiser14.96 GiB67%no, must be resident
Full pipeline22.29 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 4.21 GiB. The real file is 2.00 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 ERNIE-Image need?
Q4_K_M is exactly 2,146,489,664 bytes (2.00 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
Which quantization of ERNIE-Image 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.