Can I run Gemma 3 12B?
Gemma 3 12B by Google needs around 12 GB of RAM at the recommended 4-bit quantization (7.4 GB download). Your hardware is checked below β instantly, nothing leaves your browser. Expect roughly ~41 tok/s on a NVIDIA RTX 3060 12GB.
Reading your hardware signalsβ¦
Real-world notes
Gemma 3 12B is Google's mid-size open-weight model, and it lands in a useful spot for people who want more capability than the usual 7-8B chat models without jumping to something that needs a workstation. At a 4-bit quant it sits around 7.4 GB, which fits on a 12 GB card like an RTX 3060 with a little headroom, and runs comfortably in unified memory on a 16 GB-plus Apple Silicon Mac. The floor is 12 GB of RAM to load it at all. It also handles vision, so you can feed it images alongside text, which most models this size cannot.
In daily use it feels responsive on consumer hardware. On an RTX 3060 12GB you get around 41 tokens per second at 4-bit, faster than you read, and an Apple M Max pushes that to roughly 47 tok/s. A 4090 will fly at about 116 tok/s if you have one. The 128K context window is the catch: it is genuinely there, but filling it is expensive. At the full 128K the model plus KV cache needs about 27.7 GB total, well past what a 12 GB card holds, so keep working context modest unless you have a 24 GB GPU or plenty of unified memory.
Against Mistral Nemo 12B, the obvious same-size alternative, Gemma 3 12B generally has the edge on instruction-following and multimodal work since Nemo is text-only, though Nemo tends to be the lighter pick for pure long-context chat. If you want to stay smaller, Gemma 3 4B drops the footprint while keeping vision. Gemma 3 12B's standout is being a capable vision-and-chat model that still runs on a single mid-range GPU. One caveat: it ships under Google's Gemma license, which is open-weight but carries provider-specific terms, so read them before any commercial deployment rather than assuming it is plain open source.
Specifications
Size by quantization
| Quantization | Bits/weight | Download | Min RAM | Quality |
|---|---|---|---|---|
| Q2_K | 3.35 | 5.1 GB | 8 GB | Noticeable loss |
| Q4_K_MRecommended | 4.85 | 7.4 GB | 12 GB | Recommended |
| Q5_K_M | 5.65 | 8.6 GB | 16 GB | High |
| Q8_0 | 8.5 | 13.0 GB | 24 GB | Near-original |
| F16 | 16 | 24.4 GB | 32 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.6 GB | ~8.0 GB |
| 8K tokens | ~1.3 GB | ~8.7 GB |
| 32K tokens | ~5.1 GB | ~12.5 GB |
| 128K tokens | ~20.3 GB | ~27.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
| Hardware | Bandwidth | ~Speed |
|---|---|---|
| NVIDIA RTX 3060 12GB | 360 GB/s | ~41 tok/s |
| NVIDIA RTX 4090 24GB | 1008 GB/s | ~116 tok/s |
| Apple M-series (base) | 100 GB/s | ~11 tok/s |
| Apple M-series Pro | 270 GB/s | ~31 tok/s |
| Apple M-series Max | 410 GB/s | ~47 tok/s |
| CPU only (dual-channel DDR5) | 60 GB/s | ~7 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 gemma3:12bSources & downloads