Can I run Gemma 3 4B?
Gemma 3 4B by Google needs around 6 GB of RAM at the recommended 4-bit quantization (2.6 GB download). Your hardware is checked below β instantly, nothing leaves your browser. Expect roughly ~117 tok/s on a NVIDIA RTX 3060 12GB.
Reading your hardware signalsβ¦
Real-world notes
Gemma 3 4B is Google's small workhorse for people who want a capable local assistant that also understands images. At 4.3B parameters it punches above the size you expect from a 4B model, and the footprint is tiny: a 4-bit quant is about 2.6 GB, and you only need around 6 GB of RAM to run it. That means it fits on almost anything with a pulse: an old 8 GB laptop GPU, a base Apple Silicon Mac, even a 12 GB RTX 3060 with room to spare. If you want vision plus chat without a heavy machine, this is the obvious starting point.
In daily use it feels quick. On an RTX 3060 you can expect around 117 tokens per second at 4-bit, and on an RTX 4090 it climbs to roughly 329, so replies stream faster than you read on either. An Apple M Max sits around 134 tok/s, and even pure CPU on DDR5 manages about 20, which is usable for short prompts. The 128K context window is real but expensive: fill it completely and total memory climbs to about 15.3 GB, so on a small GPU keep your working context to a few thousand tokens or drop to a smaller quant.
Against Qwen 3 4B, the honest trade is clear: Qwen 3 generally has the edge on reasoning and structured, multi-step tasks, while Gemma 3 4B's standout is vision. Few models this small genuinely read images, and that alone makes it the pick when you need a local multimodal model on modest hardware. If you outgrow it, Gemma 3 12B is the natural step up in the same family. One caveat: the Gemma license is open-weight, not open-source, and carries Google's own usage terms, so read them before shipping it in a product.
Specifications
Size by quantization
| Quantization | Bits/weight | Download | Min RAM | Quality |
|---|---|---|---|---|
| Q2_K | 3.35 | 1.8 GB | 4 GB | Noticeable loss |
| Q4_K_MRecommended | 4.85 | 2.6 GB | 6 GB | Recommended |
| Q5_K_M | 5.65 | 3.0 GB | 6 GB | High |
| Q8_0 | 8.5 | 4.6 GB | 8 GB | Near-original |
| F16 | 16 | 8.6 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.0 GB |
| 8K tokens | ~0.8 GB | ~3.4 GB |
| 32K tokens | ~3.2 GB | ~5.8 GB |
| 128K tokens | ~12.7 GB | ~15.3 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 | ~117 tok/s |
| NVIDIA RTX 4090 24GB | 1008 GB/s | ~329 tok/s |
| Apple M-series (base) | 100 GB/s | ~33 tok/s |
| Apple M-series Pro | 270 GB/s | ~88 tok/s |
| Apple M-series Max | 410 GB/s | ~134 tok/s |
| CPU only (dual-channel DDR5) | 60 GB/s | ~20 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 gemma3Sources & downloads