Does Qwen-Image-Bench fit in 8GB of VRAM?
Not at these settings. No indexed quantization of Qwen-Image-Bench fits 8GB card at any context we compute, with f16 KV. The smallest shipped quantization is 9.98 GiB in weights alone, against 7.44 GiB usable. CPU offload can still run it, slowly.
Every quantization at every context
| Quant | Weights● | 4K◐ | 8K◐ | 16K◐ | 32K◐ | 64K◐ | 128K◐ |
|---|---|---|---|---|---|---|---|
| BF16 | 50.11 GiB | 51.2 | 51.5 | 52.0 | 53.0 | 55.0 | 59.0 |
| Q8_0 | 26.63 GiB | 27.7 | 28.0 | 28.5 | 29.5 | 31.5 | 35.5 |
| Q6_K | 20.57 GiB | 21.7 | 21.9 | 22.4 | 23.4 | 25.4 | 29.4 |
| Q5_K_M | 17.91 GiB | 19.0 | 19.3 | 19.8 | 20.8 | 22.8 | 26.8 |
| Q4_K_M | 15.41 GiB | 16.5 | 16.8 | 17.3 | 18.3 | 20.3 | 24.3 |
| Q3_K_M | 12.39 GiB | 13.5 | 13.8 | 14.3 | 15.3 | 17.3 | 21.3 |
| Q2_K | 9.98 GiB | 11.1 | 11.3 | 11.8 | 12.8 | 14.8 | 18.8 |
Figures are GiB of total memory: weights plus KV cache plus compute buffer and backend overhead. Weights and KV are near-exact; the overhead term is modeled. Hover any cell for the breakdown.
Why there are no speeds on this page
A capacity is not a card. Whether a model fits depends only on memory, so every figure above holds for any 8GB accelerator. How fast it runs depends on memory bandwidth, which varies several-fold between cards of the same capacity — so putting a tokens-per-second number here would be inventing one. Pick a specific card from hardware and the speed column appears.
Why other calculators disagree
A parameters × bits ÷ 8 estimate ignores two things that dominate at long context. First, the weights themselves are not the nominal rate — quantizations are mixtures, so the real file is consistently larger than the label implies. Second, the KV cache grows linearly with context and, past about 32K, becomes larger than the weights for many models.