Does Llama-4-Scout-17B-16E-Instruct-4bit fit in 16GB of VRAM?
Not at these settings. No indexed quantization of Llama-4-Scout-17B-16E-Instruct-4bit fits 16GB card at any context we compute, with q4_0 KV. The smallest shipped quantization is 20.95 GiB in weights alone, against 14.88 GiB usable. CPU offload can still run it, slowly.
Every quantization at every context
| Quant | Weights● | 4K◐ | 8K◐ | 16K◐ | 32K◐ | 64K◐ | 128K◐ |
|---|---|---|---|---|---|---|---|
| F16 | 37.96 GiB | 39.0 | 39.2 | 39.6 | 40.5 | 42.2 | 45.5 |
| Q8_0 | 26.16 GiB | 27.2 | 27.4 | 27.8 | 28.7 | 30.4 | 33.7 |
| Q4_K_M | 20.95 GiB | 22.0 | 22.2 | 22.6 | 23.5 | 25.1 | 28.5 |
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 16GB 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, most of this model's layers cache only a 8,192-token window rather than the full context.