Can I run Gemma 3 1B?
Gemma 3 1B by Google needs around 3 GB of RAM at the recommended 4-bit quantization (0.6 GB download). Your hardware is checked below β instantly, nothing leaves your browser. Expect roughly ~505 tok/s on a NVIDIA RTX 3060 12GB.
Reading your hardware signalsβ¦
Real-world notes
Gemma 3 1B is a tiny chat model from Google, built for the cases where you want a local assistant that loads instantly and runs almost anywhere. At a 4-bit quant it is only about 0.6 GB, and even an 8-bit build is roughly 1.1 GB, so it fits in 3 GB of RAM with room to spare. That means it runs on an old laptop, a Raspberry Pi class device, or a phone-grade chip without touching a discrete GPU. If you need something for quick chat, drafting, or embedding in an app where every megabyte counts, this is the model to reach for.
In daily use the headline is raw speed. On an RTX 4090 it pushes around 1413 tokens per second, and a more typical RTX 3060 still does about 505 tok/s, with an Apple M Max around 575 tok/s. Even pure CPU on DDR5 manages roughly 84 tok/s, faster than you can read. The context window is 32K, and unlike bigger models you can fill a good chunk of it cheaply: at the full 32K the whole thing sits around 2.2 GB total, so memory is never the thing that stops you here.
Honesty about its size matters: at 1B parameters this is not a reasoning or coding model, and it will lose the thread on long multi-step instructions. If you have the headroom, Gemma 3 4B generally handles harder prompts and adds vision, while Llama 3.2 1B is the obvious same-weight alternative to compare against for plain chat. Gemma 3 1B's standout trait is that it is about the smallest genuinely usable chat model you can run. One caveat: it ships under Google's Gemma license, which is open-weight but carries provider-specific terms, so read them before shipping it commercially.
Specifications
Size by quantization
| Quantization | Bits/weight | Download | Min RAM | Quality |
|---|---|---|---|---|
| Q2_K | 3.35 | 0.4 GB | 2 GB | Noticeable loss |
| Q4_K_MRecommended | 4.85 | 0.6 GB | 3 GB | Recommended |
| Q5_K_M | 5.65 | 0.7 GB | 3 GB | High |
| Q8_0 | 8.5 | 1.1 GB | 3 GB | Near-original |
| F16 | 16 | 2.0 GB | 4 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.2 GB | ~0.8 GB |
| 8K tokens | ~0.4 GB | ~1.0 GB |
| 32K tokens | ~1.6 GB | ~2.2 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 | ~505 tok/s |
| NVIDIA RTX 4090 24GB | 1008 GB/s | ~1413 tok/s |
| Apple M-series (base) | 100 GB/s | ~140 tok/s |
| Apple M-series Pro | 270 GB/s | ~379 tok/s |
| Apple M-series Max | 410 GB/s | ~575 tok/s |
| CPU only (dual-channel DDR5) | 60 GB/s | ~84 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:1bSources & downloads