Can I run Gemma 4 31B?
Gemma 4 31B by Google needs around 32 GB of RAM at the recommended 4-bit quantization (18.6 GB download). Your hardware is checked below — instantly, nothing leaves your browser. Expect roughly ~19 tok/s on a Apple M-series Max.
Reading your hardware signals…
Real-world notes
Gemma 4 31B is Google's mid-large open-weight model at 30.7B parameters, built for chat, coding, reasoning, and vision in one package. This is not a laptop-and-go model. At a 4-bit quant it weighs about 18.6 GB, and you need at least 32 GB of RAM to load it at all, so a 12 GB card like the RTX 3060 simply does not fit. The realistic home for it is a 24 GB GPU such as an RTX 4090, or an Apple Silicon Mac with plenty of unified memory. If you want a capable all-rounder and have the hardware, this is the tier where local models start feeling genuinely useful.
In daily use it is comfortable rather than blazing. On an RTX 4090 you can expect around 46 tokens per second at 4-bit, fast enough to read along as it streams; on an Apple M Max it settles closer to 19 tokens per second, still fine for interactive work. Pure CPU on DDR5 drops to roughly 3 tokens per second, which is patience-only territory. The 256K context window is generous, but it is expensive: pushing toward 128K already takes about 49.3 GB total memory, so treat the full window as a ceiling and keep working context modest unless you have headroom to spare.
Against Qwen 3 30B-A3B, a near-identical 30.5B sibling, the trade is architectural: Qwen's mixture-of-experts design tends to run lighter per token, while Gemma 4 31B is a dense model that uses its full weight on every pass and generally feels steadier on vision and broad instruction-following. If you want something far smaller, Gemma 3 4B is the lighter pick. The standout here is breadth: one model covering chat, code, reasoning, and images, under a clean Apache 2.0 license you can use commercially and in production without provider-specific restrictions.
Specifications
Size by quantization
| Quantization | Bits/weight | Download | Min RAM | Quality |
|---|---|---|---|---|
| Q2_K | 3.35 | 12.9 GB | 24 GB | Noticeable loss |
| Q4_K_MRecommended | 4.85 | 18.6 GB | 32 GB | Recommended |
| Q5_K_M | 5.65 | 21.7 GB | 32 GB | High |
| Q8_0 | 8.5 | 32.6 GB | 48 GB | Near-original |
| F16 | 16 | 61.4 GB | 96 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 | ~1.0 GB | ~19.6 GB |
| 8K tokens | ~1.9 GB | ~20.5 GB |
| 32K tokens | ~7.7 GB | ~26.3 GB |
| 128K tokens | ~30.7 GB | ~49.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 | Won't fit in VRAM |
| NVIDIA RTX 4090 24GB | 1008 GB/s | ~46 tok/s |
| Apple M-series (base) | 100 GB/s | ~5 tok/s |
| Apple M-series Pro | 270 GB/s | ~12 tok/s |
| Apple M-series Max | 410 GB/s | ~19 tok/s |
| CPU only (dual-channel DDR5) | 60 GB/s | ~3 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:31bSources & downloads