Yes, just — 2.4 GB spare
Gemma 4 26B-A4B at Q4_K_M fits your RTX 4000 Ada entirely on the GPU at 8K context, at an estimated 39 tokens per second. Past 69K the KV cache pushes it over — quantise the cache to q8_0, or step down a quantisation, to go longer.
Fully on GPU
8K context
Q4_K_M · 14.9 GB
Apache 2.0
Released 2 Apr 2026
Vision
Mixture of experts with 3.8B active. Slower to think than Qwen3.6 35B-A3B, faster to answer, and it sees images.
The VRAM budget
weights 14.9 GB
Weights 14.9 GB
KV cache @ 8K 0.51 GB
Runtime overhead 0.6 GB
Free 2.4 GB of 18.4 GB
Quantisation ladder
| Quant | Weights | Total @ 8K | Max context | Tok/s | Quality | Fit |
|---|---|---|---|---|---|---|
| Q8_0 | 26.2 GB | 27.3 GB | — | ~8.2 | −0.1% ppl | 8.9 GB over |
| Q6_K | 20.2 GB | 21.3 GB | — | ~17 | −0.4% ppl | 2.9 GB over |
| Q5_K_M | 17.5 GB | 18.6 GB | 2K | ~32 | −0.8% ppl | 0.2 GB over |
| Q4_K_M | 14.9 GB | 16.0 GB | 69K | 39 | −1.9% ppl | Recommended |
| Q3_K_M | 12.1 GB | 13.2 GB | 141K | 48 | −5.4% ppl | Long context |
| Q2_K | 10.3 GB | 11.4 GB | 186K | 57 | −15% ppl | Long context |
Quality is the published perplexity delta against f16 weights. Max context assumes an f16 KV cache; q8_0 roughly doubles it. This model interleaves sliding-window layers (1024 tokens, 5 of 30 layers global), which is why its cache barely grows with context.
How to run it
$ llama-server \
-hf google/gemma-4-26B-A4B-it:Q4_K_M \
-c 8192 -ngl 99
The engine underneath most of the others. Every knob is exposed. More on llama.cpp.
01Download is 14.9 GB. Keep it on an SSD — a first load off a spinning disk takes minutes.
02Close anything else holding VRAM. A browser with hardware acceleration can sit on 1–2 GB.
03Only 2.4 GB is spare, so a long system prompt can still push it over. Its real ceiling here is 69K context.