gemma-3n-E4B-it
google/gemma-3n-E4B-itgemma-3n-E4B-it at Q4_K_M is exactly 4,237,064,064 bytes (3.95 GiB / 4.24 GB) — an effective 4.318 bits per weight, not the nominal 4. Its KV cache at 32K is 0.49 GiB, not the 2.19 GiB a flat formula predicts.
Shipped quantizations
| Quant | Size● | Exact bytes● | Effective bpw● | Tensors● | Publisher |
|---|---|---|---|---|---|
| Q2_K | 2.57 GiB | 2,757,318,528 | 2.810 | — | bartowski |
| UD-IQ2_XXS | 2.64 GiB | 2,830,964,864 | 2.885 | — | unsloth |
| UD-IQ2_M | 2.89 GiB | 3,105,929,344 | 3.165 | — | unsloth |
| IQ3_XS | 2.95 GiB | 3,166,394,240 | 3.227 | — | bartowski |
| Q2_K | 2.97 GiB | 3,190,380,672 | 3.251 | — | unsloth |
| Q2_K_L | 2.97 GiB | 3,190,380,672 | 3.251 | — | unsloth |
| Q3_K_S | 3.03 GiB | 3,251,910,528 | 3.314 | — | bartowski |
| IQ3_M | 3.07 GiB | 3,294,107,520 | 3.357 | — | bartowski |
| UD-IQ3_XXS | 3.12 GiB | 3,349,244,032 | 3.413 | — | unsloth |
| Q3_K_M | 3.20 GiB | 3,440,908,160 | 3.507 | — | bartowski |
| Q3_K_S | 3.26 GiB | 3,500,947,584 | 3.568 | — | unsloth |
| Q3_K_L | 3.35 GiB | 3,601,995,648 | 3.671 | — | bartowski |
| Q3_K_M | 3.44 GiB | 3,689,945,216 | 3.760 | — | unsloth |
| IQ4_XS | 3.63 GiB | 3,895,023,488 | 3.970 | — | bartowski |
| IQ4_NL | 3.81 GiB | 4,089,993,088 | 4.168 | — | bartowski |
| Q4_0 | 3.81 GiB | 4,093,794,176 | 4.172 | — | bartowski |
| Q4_K_S | 3.82 GiB | 4,102,707,072 | 4.181 | — | bartowski |
| Q4_K_M | 3.95 GiB | 4,237,064,064 | 4.318 | — | bartowski |
| IQ4_XS | 3.98 GiB | 4,271,954,048 | 4.354 | — | unsloth |
| IQ4_NL | 4.09 GiB | 4,391,983,232 | 4.476 | — | unsloth |
| Q4_0 | 4.09 GiB | 4,395,784,320 | 4.480 | — | unsloth |
| Q4_K_S | 4.10 GiB | 4,404,697,216 | 4.489 | — | unsloth |
| Q4_1 | 4.17 GiB | 4,477,638,528 | 4.563 | — | bartowski |
| Q4_K_M | 4.23 GiB | 4,539,054,208 | 4.626 | — | unsloth |
| Q2_K_L | 4.30 GiB | 4,612,249,472 | 4.700 | — | bartowski |
| Q4_1 | 4.31 GiB | 4,632,828,032 | 4.721 | — | unsloth |
| Q5_K_S | 4.54 GiB | 4,869,871,488 | 4.963 | — | bartowski |
| Q5_K_S | 4.61 GiB | 4,945,369,216 | 5.040 | — | unsloth |
| Q5_K_M | 4.61 GiB | 4,947,998,592 | 5.043 | — | bartowski |
| Q5_K_M | 4.68 GiB | 5,023,496,320 | 5.120 | — | unsloth |
| Q4_K_L | 5.16 GiB | 5,541,492,608 | 5.647 | — | bartowski |
| Q6_K | 5.31 GiB | 5,703,366,528 | 5.812 | — | bartowski |
| Q5_K_L | 5.55 GiB | 5,958,825,856 | 6.073 | — | bartowski |
| Q6_K | 5.84 GiB | 6,272,219,264 | 6.392 | — | unsloth |
| Q6_K_L | 5.96 GiB | 6,402,242,432 | 6.525 | — | bartowski |
| Q8_0 | 6.85 GiB | 7,353,292,672 | 7.494 | — | bartowski |
| Q8_0 | 6.85 GiB | 7,353,292,928 | 7.494 | — | unsloth |
| F16 | 12.80 GiB | 13,740,103,552 | 14.003 | — | unsloth |
KV cache by context
| Context | KV cache (f16)● | Flat formula | Overstated by | Full / windowed / recurrent |
|---|---|---|---|---|
| 4,096 | 0.11 GiB | 0.27 GiB | 2.50× | 7 / 28 / 0 |
| 8,192 | 0.16 GiB | 0.55 GiB | 3.33× | 7 / 28 / 0 |
| 16,384 | 0.27 GiB | 1.09 GiB | 4.00× | 7 / 28 / 0 |
| 32,768 | 0.49 GiB | 2.19 GiB | 4.44× | 7 / 28 / 0 |
| 65,536 | 0.93 GiB | 4.38 GiB | 4.71× | 7 / 28 / 0 |
| 131,072 | 1.80 GiB | 8.75 GiB | 4.85× | 7 / 28 / 0 |
28 of 35 layers cache only a 512-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 4.11 GiB. The real file is 3.95 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 2.19 GiB at 32K context where the real figure is 0.49 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-3n-E4B-it need?
- Q4_K_M is exactly 4,237,064,064 bytes (3.95 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-3n-E4B-it's KV cache?
- 0.49 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-3n-E4B-it 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.