gemma-4-E2B-it
google/gemma-4-E2B-itgemma-4-E2B-it at Q4_K_M is exactly 3,106,738,272 bytes (2.89 GiB / 3.11 GB) — an effective 4.851 bits per weight, not the nominal 4. Its KV cache at 32K is 0.25 GiB, not the 1.09 GiB a flat formula predicts.
Shipped quantizations
| Quant | Size● | Exact bytes● | Effective bpw● | Tensors● | Publisher |
|---|---|---|---|---|---|
| UD-IQ2_M | 2.13 GiB | 2,290,860,128 | 3.577 | — | unsloth |
| IQ1_S | 2.16 GiB | 2,315,847,744 | 3.616 | — | DuoNeural |
| UD-IQ3_XXS | 2.21 GiB | 2,372,993,120 | 3.705 | — | unsloth |
| Q3_K_S | 2.28 GiB | 2,445,652,064 | 3.819 | — | unsloth |
| Q3_K_M | 2.36 GiB | 2,536,786,016 | 3.961 | 601 | unsloth |
| IQ2_M | 2.38 GiB | 2,553,153,600 | 3.987 | — | DuoNeural |
| IQ2_M | 2.44 GiB | 2,620,200,416 | 4.091 | — | bartowski |
| IQ3_XXS | 2.47 GiB | 2,648,066,112 | 4.135 | — | DuoNeural |
| IQ4_XS | 2.78 GiB | 2,983,944,288 | 4.660 | 601 | unsloth |
| Q2_K | 2.81 GiB | 3,020,053,984 | 4.716 | — | bartowski |
| IQ4_NL | 2.83 GiB | 3,041,083,488 | 4.749 | — | unsloth |
| Q4_0 | 2.83 GiB | 3,041,378,400 | 4.749 | — | unsloth |
| Q4_K_S | 2.83 GiB | 3,043,934,304 | 4.753 | — | unsloth |
| IQ3_XS | 2.89 GiB | 3,100,712,416 | 4.842 | — | bartowski |
| Q4_K_M | 2.89 GiB | 3,106,738,272 | 4.851 | — | unsloth |
| Q3_K_S | 2.92 GiB | 3,134,793,184 | 4.895 | — | bartowski |
| IQ3_M | 2.92 GiB | 3,134,964,672 | 4.895 | — | HauhauCS |
| Q4_1 | 2.94 GiB | 3,154,919,520 | 4.926 | — | unsloth |
| IQ3_M | 2.94 GiB | 3,161,611,744 | 4.937 | — | bartowski |
| Q3_K_M | 2.97 GiB | 3,191,940,960 | 4.984 | — | DuoNeural |
| Q3_K_M | 3.00 GiB | 3,224,043,456 | 5.034 | — | braydenh563 |
| Q3_K_M | 3.01 GiB | 3,226,811,872 | 5.039 | 601 | bartowski |
| Q3_K_L | 3.06 GiB | 3,290,414,560 | 5.138 | — | bartowski |
| IQ4_XS | 3.07 GiB | 3,292,383,296 | 5.141 | — | DuoNeural |
| Q5_K_S | 3.09 GiB | 3,321,151,584 | 5.186 | — | unsloth |
| IQ4_XS | 3.10 GiB | 3,324,311,008 | 5.191 | 601 | bartowski |
| Q5_K_M | 3.13 GiB | 3,356,037,216 | 5.241 | — | unsloth |
| Q4_0 | 3.15 GiB | 3,378,740,704 | 5.276 | 601 | bartowski |
| IQ4_NL | 3.15 GiB | 3,380,639,200 | 5.279 | — | bartowski |
| Q4_K_S | 3.15 GiB | 3,382,083,040 | 5.281 | — | bartowski |
| Q4_K_M | 3.18 GiB | 3,416,101,728 | 5.334 | — | DuoNeural |
| Q4_K_M | 3.19 GiB | 3,427,880,384 | 5.353 | 601 | lmstudio-community |
| Q4_K_M | 3.21 GiB | 3,450,277,824 | 5.388 | — | braydenh563 |
| Q4_K_M | 3.22 GiB | 3,462,680,032 | 5.407 | 601 | bartowski |
| Q4_1 | 3.25 GiB | 3,490,069,984 | 5.450 | — | bartowski |
| Q5_K_S | 3.36 GiB | 3,603,758,560 | 5.627 | — | bartowski |
| Q5_K_M | 3.37 GiB | 3,616,691,040 | 5.648 | — | DuoNeural |
| Q5_K_M | 3.41 GiB | 3,658,384,864 | 5.713 | 601 | bartowski |
| Q5_K_M | 3.41 GiB | 3,663,440,832 | 5.721 | — | braydenh563 |
| Q2_K_L | 3.43 GiB | 3,686,424,032 | 5.756 | — | bartowski |
KV cache by context
| Context | KV cache (f16)● | Flat formula | Overstated by | Full / windowed / recurrent |
|---|---|---|---|---|
| 4,096 | 0.05 GiB | 0.14 GiB | 2.50× | 7 / 28 / 0 |
| 8,192 | 0.08 GiB | 0.27 GiB | 3.33× | 7 / 28 / 0 |
| 16,384 | 0.14 GiB | 0.55 GiB | 4.00× | 7 / 28 / 0 |
| 32,768 | 0.25 GiB | 1.09 GiB | 4.44× | 7 / 28 / 0 |
| 65,536 | 0.46 GiB | 2.19 GiB | 4.71× | 7 / 28 / 0 |
| 131,072 | 0.90 GiB | 4.38 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 2.68 GiB. The real file is 2.89 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.09 GiB at 32K context where the real figure is 0.25 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-E2B-it need?
- Q4_K_M is exactly 3,106,738,272 bytes (2.89 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-E2B-it's KV cache?
- 0.25 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-E2B-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.