Can I run Gemma 4 E2B?
Gemma 4 E2B by Google needs around 6 GB of RAM at the recommended 4-bit quantization (3.1 GB download). Your hardware is checked below — instantly, nothing leaves your browser. Expect roughly ~219 tok/s on a NVIDIA RTX 3060 12GB.
Reading your hardware signals…
Real-world notes
Gemma 4 E2B is Google's small mixture-of-experts model, and the interesting part is the math: it carries 5.1B parameters total but only activates about 2.3B per token. That means it runs at the speed of a much smaller model while still needing memory for the whole thing. A 4-bit quant lands around 3.1 GB, and you'll want roughly 6 GB of RAM minimum to hold the full set of weights. That fits an entry-level 8 GB GPU or any Apple Silicon Mac with room to spare, and it handles both chat and vision, so you can feed it images, not just text.
In daily use the active-parameter trick pays off in raw throughput. On an RTX 3060 12GB it pushes around 219 tokens per second at 4-bit, and an RTX 4090 takes that past 600; an M-series Max sits near 250. Replies stream far faster than you read. The 128K context is the catch to watch: fill it and total memory climbs to roughly 16.8 GB, well past the 6 GB you need at short context. On a small card, keep working context to a few thousand tokens or the KV cache will outgrow the model itself.
Against its own family, Gemma 3 4B is the dense alternative if you'd rather not deal with the MoE memory footprint, and Qwen 3 4B generally has the edge on multi-step reasoning since that's its stated focus. Gemma 4 E2B's standout is the speed-to-capability ratio plus native vision in a package this light, which is rare at this size. It's Apache 2.0, so unlike Google's older Gemma terms you can use it commercially in production with no special license to read. Pull it with ollama run gemma4:e2b and you're set.
Specifications
Size by quantization
| Quantization | Bits/weight | Download | Min RAM | Quality |
|---|---|---|---|---|
| Q2_K | 3.35 | 2.1 GB | 6 GB | Noticeable loss |
| Q4_K_MRecommended | 4.85 | 3.1 GB | 6 GB | Recommended |
| Q5_K_M | 5.65 | 3.6 GB | 6 GB | High |
| Q8_0 | 8.5 | 5.4 GB | 12 GB | Near-original |
| F16 | 16 | 10.2 GB | 16 GB | Original |
Sizes are estimates from parameter count × bits per weight; real GGUF builds vary slightly. · Data updated: 2026-06-11 · How we calculate these numbers →
Memory needed by context length
| Context | KV cache (est.) | Total memory (Q4) |
|---|---|---|
| 4K tokens | ~0.4 GB | ~3.5 GB |
| 8K tokens | ~0.9 GB | ~4.0 GB |
| 32K tokens | ~3.4 GB | ~6.5 GB |
| 128K tokens | ~13.7 GB | ~16.8 GB |
The KV cache grows with context length — a model that fits at 4K can run out of memory at 32K. Estimates assume an FP16 cache with grouped-query attention; actual usage varies by runtime.
Estimated speed by hardware
| Hardware | Bandwidth | ~Speed |
|---|---|---|
| NVIDIA RTX 3060 12GB | 360 GB/s | ~219 tok/s |
| NVIDIA RTX 4090 24GB | 1008 GB/s | ~614 tok/s |
| Apple M-series (base) | 100 GB/s | ~61 tok/s |
| Apple M-series Pro | 270 GB/s | ~165 tok/s |
| Apple M-series Max | 410 GB/s | ~250 tok/s |
| CPU only (dual-channel DDR5) | 60 GB/s | ~37 tok/s |
Token generation is memory-bandwidth bound: tok/s ≈ bandwidth × 0.85 ÷ model size at Q4. Real-world numbers vary by runtime and context length.
Run it locally
The easiest path is Ollama — one command and you're chatting:
ollama run gemma4:e2bSources & downloads