gemma-4-26B-A4B-it-assistant
google/gemma-4-26B-A4B-it-assistantgemma-4-26B-A4B-it-assistant at Q4_K_M is exactly 325,452,000 bytes (0.30 GiB / 0.33 GB) — an effective 6.203 bits per weight, not the nominal 4. Its KV cache at 32K is 0.29 GiB, not the 1.00 GiB a flat formula predicts.
Shipped quantizations
| Quant | Size● | Exact bytes● | Effective bpw● | Tensors● | Publisher |
|---|---|---|---|---|---|
| IQ4_NL | 0.30 GiB | 321,126,496 | 6.121 | — | RachidAR |
| Q4_0 | 0.30 GiB | 321,126,496 | 6.121 | — | RachidAR |
| Q4_K_S | 0.30 GiB | 321,126,624 | 6.121 | — | AtomicChat |
| Q4_K_M | 0.30 GiB | 325,452,000 | 6.203 | — | AtomicChat |
| Q4_K_M | 0.31 GiB | 329,777,248 | 6.286 | — | RachidAR |
| Q5_K_M | 0.32 GiB | 342,261,984 | 6.524 | — | AtomicChat |
| Q5_K_M | 0.32 GiB | 344,490,080 | 6.566 | — | RachidAR |
| Q6_K | 0.34 GiB | 360,122,464 | 6.864 | — | RachidAR |
| Q8_0 | 0.43 GiB | 461,765,312 | 8.802 | — | Radamanthys11 |
| Q8_0 | 0.43 GiB | 461,766,752 | 8.802 | — | RachidAR |
| Q8_0 | 0.43 GiB | 461,766,880 | 8.802 | — | AtomicChat |
| F16 | 0.80 GiB | 855,227,040 | 16.301 | — | Radamanthys11 |
| BF16 | 0.80 GiB | 855,228,512 | 16.301 | — | RachidAR |
| F16 | 0.80 GiB | 855,228,640 | 16.301 | — | AtomicChat |
KV cache by context
| Context | KV cache (f16)● | Flat formula | Overstated by | Full / windowed / recurrent |
|---|---|---|---|---|
| 4,096 | 0.07 GiB | 0.13 GiB | 1.88× | 1 / 3 / 0 |
| 8,192 | 0.10 GiB | 0.25 GiB | 2.56× | 1 / 3 / 0 |
| 16,384 | 0.16 GiB | 0.50 GiB | 3.12× | 1 / 3 / 0 |
| 32,768 | 0.29 GiB | 1.00 GiB | 3.51× | 1 / 3 / 0 |
| 65,536 | 0.54 GiB | 2.00 GiB | 3.74× | 1 / 3 / 0 |
| 131,072 | 1.04 GiB | 4.00 GiB | 3.86× | 1 / 3 / 0 |
3 of 4 layers cache only a 1,024-token window rather than the full context, on a period of . Figures assume the default configuration; --swa-full disables the saving entirely.
Compare with
Will it run on your card?
Why other calculators give a different number
A parameters × bits ÷ 8 estimate puts Q4_K_M at roughly 0.22 GiB. The real file is 0.30 GiB, because a quantization is a mixture and some tensors are always kept at higher precision. The larger discrepancy is the cache: a flat formula gives 1.00 GiB at 32K context where the real figure is 0.29 GiB, because most of this model's layers cache a fixed window rather than the whole context.
Architecture
Questions people ask
- How much VRAM does gemma-4-26B-A4B-it-assistant need?
- Q4_K_M is exactly 325,452,000 bytes (0.30 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
- How large is gemma-4-26B-A4B-it-assistant's KV cache?
- 0.29 GiB at 32K context with an f16 cache, computed per layer. Quantizing the cache to q8_0 roughly halves it, which is often the difference between a context length fitting and not.
- Which quantization of gemma-4-26B-A4B-it-assistant 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.