← All modelsMODEL CHECK

Can I run Gemma 4 E4B?

Gemma 4 E4B by Google needs around 8 GB of RAM at the recommended 4-bit quantization (4.9 GB download). Your hardware is checked below β€” instantly, nothing leaves your browser. Expect roughly ~112 tok/s on a NVIDIA RTX 3060 12GB.

Reading your hardware signals…

Real-world notes

Gemma 4 E4B is Google's small mixture-of-experts model, and it's a good fit if you want a local assistant that also reads images. The trick with an MoE is that only about 4.5B of its 8B parameters fire per token, so it runs at the speed of a much smaller model while still needing room for the whole thing in memory. At 4-bit it lands around 4.9 GB, which fits on a 12 GB card like an RTX 3060 with plenty of headroom, and sits fine within unified memory on an 8 GB Apple Silicon Mac. Plan for the full model, not just the active slice.

In daily use it feels quick. On an RTX 3060 you can expect around 112 tokens per second at 4-bit, and a high-end card like the RTX 4090 pushes that past 300, faster than you'll ever read. On Apple Silicon an M-Max sits near 128 tok/s, and even CPU on DDR5 manages roughly 19 tok/s if you're patient. The 128K context window is real but expensive: fill it and total memory climbs to about 21.7 GB, well past what the weights alone suggest. Keep working context to a few thousand tokens on smaller hardware and you'll stay comfortable.

Against Gemma 3 4B, the lighter sibling in the family, E4B tends to give you stronger output while keeping a similar small active footprint, and both handle vision, so it's the better default unless you're truly memory-starved. Its standout trait is that MoE speed-to-quality balance: chat and image understanding at small-model latency. And the license is the easy part. Apache 2.0 means you can use it freely, including commercially and in production, with no provider-specific strings attached. That makes it one of the simpler local models to actually ship something on.

Specifications

Parameters8B (4.5B active)
Context window128K tokens
ProviderGoogle
LicenseApache 2.0
Released2026-04
Best forChat, Vision

Size by quantization

QuantizationBits/weightDownloadMin RAMQuality
Q2_K3.353.4 GB6 GBNoticeable loss
Q4_K_MRecommended4.854.9 GB8 GBRecommended
Q5_K_M5.655.7 GB12 GBHigh
Q8_08.58.5 GB16 GBNear-original
F161616.0 GB24 GBOriginal

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

ContextKV cache (est.)Total memory (Q4)
4K tokens~0.5 GB~5.4 GB
8K tokens~1.0 GB~5.9 GB
32K tokens~4.2 GB~9.1 GB
128K tokens~16.8 GB~21.7 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

HardwareBandwidth~Speed
NVIDIA RTX 3060 12GB360 GB/s~112 tok/s
NVIDIA RTX 4090 24GB1008 GB/s~314 tok/s
Apple M-series (base)100 GB/s~31 tok/s
Apple M-series Pro270 GB/s~84 tok/s
Apple M-series Max410 GB/s~128 tok/s
CPU only (dual-channel DDR5)60 GB/s~19 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:e4b

Frequently asked questions

Gemma 4 E4B System Requirements β€” Can I Run It Locally?