Gemma 4 26B-A4B IT
26B-A4BGoogle Gemma 4
Google's Gemma 4 mixture-of-experts model: about 25B parameters in the text model, roughly 4B active per token, a 256K window and image input. Only 5 of its 30 layers keep a cache that grows with context, and those use fewer, wider heads, so the cache stays small — about 0.9 GB at 32K and 5.3 GB at the full 256K. At Q4_K_M that is about 18.8 GB at 32K: comfortable on a 24 GB card, which can still load the whole window (tight, about 23.6 GB). A 16 GB card cannot hold it, since the Q4_K_M file alone is 17.0 GB. The vision encoder is a separate 1.2 GB file on top. Sizes come from bartowski's GGUF files, whose Q4_K_M works out at 5.40 bits per weight, well above the generic 4-bit rate; Unsloth's UD-Q4_K_M is a different file, 0.09 GB smaller. No per-level quality loss has been published.
262K
Max Context
2
Quant Variants
GGUF Q8_0
Best Quality
—
Perplexity rise (best build)
Quantization Variants
Per-quant VRAM, quality loss, and inference speed on RTX 4090
Measured = run on this site · Estimated = not run here: calculated, or a figure this site has not verified · Community = public reports
| Format | Level | BPW | VRAM | PPL Loss | Speed | Source | Actions |
|---|---|---|---|---|---|---|---|
| GGUF | Q4_K_M | 5.4 | 18.2 GB | — | — | Estimated | |
| GGUF | Q8_0 | 8.51 | 28.5 GB | — | — | Estimated |
Which file each size is for
A file size is not a memory figure: the VRAM column is the calculator's total at 4K context — weights plus KV cache plus a 10% activation buffer. Units differ on purpose: file sizes are decimal GB, as Hugging Face lists them; the VRAM column is GiB (1024³ bytes) with 2% added to the weights, so 7.12 GB of file counts as about 6.8 GiB there. A vision projector (mmproj), where the repo ships one, is a separate download and is in neither number.
- GGUF Q4_K_Mbartowski/google_gemma-4-26B-A4B-it-GGUF · google_gemma-4-26B-A4B-it-Q4_K_M.gguf · 17.04 GB (17,035,039,872 bytes) · + vision projector 1.19 GB, separate · listing read 2026-10-21
- GGUF Q8_0bartowski/google_gemma-4-26B-A4B-it-GGUF · google_gemma-4-26B-A4B-it-Q8_0.gguf · 26.86 GB (26,859,861,120 bytes) · + vision projector 1.19 GB, separate · listing read 2026-10-21
Related community runs
These runs describe their own settings. Their speeds do not replace this estimate or prove your configuration fits.
Our reviewed link index has no run for this model yet. You can browse community reports or share your own test below.
Browse more runs on llamaPerf ↗Similar models
Compare with Gemma 4Gemma 4 31B IT
Google Gemma 4
Google's dense Gemma 4 flagship: about 31B parameters, a 256K window and image input. Only 10 of its 60 layers cache the full context, and those use four wide KV heads, so 128K of context adds about 11 GB of cache where a conventional 60-layer design would need about 120 GB. At Q4_K_M it needs about 22.1 GB at 4K, tight on a 24 GB card; Q3_K_M is about 18.3 GB at 4K. A 32 GB card holds Q4_K_M at 32K comfortably. Google also publishes its own quantization-aware (QAT) Q4_0 build, a single 17.7 GB file: about 20.1 GB at 4K, comfortable on 24 GB up to 16K. Its 1.2 GB vision encoder is a separate file, and with it loaded even 4K is tight on 24 GB. The other levels are sized from bartowski's GGUF files, and no per-level quality loss has been published. That repository also carries two MTP draft-head files (349 MB at Q4_0, 515 MB at Q8_0) for speculative decoding; they are not the model itself and are not counted in these sizes.
Gemma 4 E4B IT
Google Gemma 4
Google's on-device Gemma 4: about 4.7B parameters doing the work plus a 2.8B per-layer embedding table, a 128K window, and image and audio input. Only 4 of its 42 layers keep a cache that grows with context, so the full 128K window costs about 2.0 GB of cache. At Q4_K_M it needs about 5.3 GB at 4K, comfortable on an 8 GB card, and 7.5 GB at 128K, tight on an 8 GB card. An 8 GB Mac gives its GPU about 6 GB, so 5.3 GB at 4K is tight on an 8 GB Mac. Sizes here count the whole model in GPU memory, which is what a Mac or a full GPU load uses; llama.cpp keeps the embedding table in system RAM instead, so on a discrete card real VRAM use is lower than shown. Sizes come from unsloth's files (Q4_K_M 5.0 GB, Q8_0 8.2 GB); other publishers' Q4_K_M files are up to 0.4 GB larger. The image and audio encoder is a separate 1.0 GB file.
Gemma 4 E2B IT
Google Gemma 4
The smallest Gemma 4: about 2.3B parameters doing the work plus a 2.3B per-layer embedding table, a 128K window, and image and audio input. Its cache barely grows — 3 of 35 layers track the full context, about 0.8 GB at 128K. At Q4 it is about 3.0 GB at 4K and 3.8 GB at the full window — comfortable on any card in this index and on an 8 GB Mac. Sizes count the whole model in GPU memory; llama.cpp keeps the embedding table in system RAM, so on a discrete card it needs roughly 1.3 GB less VRAM than shown at Q4. Sizes use the calculator's generic rates — no GGUF file size could be checked.
Gemma 4 12B IT
Google Gemma 4
Google's mid-sized Gemma 4, released in June: a dense 12B with a 256K window. It takes text, images and audio without separate encoders — the raw inputs go straight into the one decoder. Only 8 of its 48 layers cache the full context, each with a single wide KV head, so the cache stays small: about 1 GB at 32K and 4.5 GB at the full 256K. At Q4_K_M (unsloth's 7.1 GB file) that is about 8.5 GB at 32K and 10.2 GB at 128K, both comfortable on a 12 GB card; a 16 GB card holds the whole window comfortably, and an 8 GB card is tight even at 4K. bartowski's Q4_K_M is a larger file (7.7 GB), so add about half a gigabyte if you use it. Sizes come from the published GGUF files; the image and audio embedders ship as a separate mmproj file, and no per-level quality loss has been published.
Running Gemma 4 26B-A4B IT locally
At Q4_K_M and 4K of context, Gemma 4 26B-A4B IT needs about 18.2 GB — 16.2 GB of weights, 0.37 GB of KV cache and a 1.7 GB activation buffer. The smallest cards in this index that clear that comfortably are 24 GB ones — 4 of them, from the RTX 3090 up — and 31 of the 78 cards here do. These are calculated figures, not measurements: the estimate stops counting a card as comfortable at 88% of its VRAM, which is roughly the room a desktop session needs.
What longer context costs
Going from 4K to 32K adds about 0.55 GB, taking the total to 18.8 GB. That is gentler than the parameter count suggests: only 5 of 30 layers keep a KV cache that grows with context, and 25 more cap theirs at a sliding window, so the cache scales at a fraction of the usual rate. The model's native window is 256K; holding all of it at Q4_K_M would need about 24 GB.
Which build to download
This index only tracks Gemma 4 26B-A4B IT in GGUF, across 2 levels (Q4_K_M, Q8_0). No per-level perplexity sweep has been published for this model, so the quality column is empty rather than estimated — within one model, more bits per weight is the only ordering the data supports. No throughput has been measured for this model on this site's hardware. GGUF runs on llama.cpp and Ollama across NVIDIA, AMD and Apple silicon; AWQ and GPTQ target vLLM on CUDA and ROCm; EXL2 is ExLlamaV2 — CUDA only, and now archived, so local use rather than serving.
Common questions
- How much VRAM does Gemma 4 26B-A4B IT need?
- About 18.2 GB at Q4_K_M with 4K of context and batch 1, rising to roughly 18.8 GB at 32K. That figure is weights plus KV cache plus a 10% activation buffer, calculated from the model's architecture rather than measured on a card.
- Will Gemma 4 26B-A4B IT run on a 24GB GPU?
- Yes — at Q4_K_M and 4K context it needs about 18.2 GB, which leaves 5.8 GB spare on a RTX 3090, or on any of the other 24 GB cards here (4 in all). That is the smallest size in this index that clears it comfortably; 31 of 78 do.
- Which quantization of Gemma 4 26B-A4B IT should I use?
- No published quality comparison exists for this model, so pick by footprint: Q4_K_M is the level most people run, and a higher bits-per-weight level is more faithful. All 2 levels in the index are Q4_K_M, Q8_0. Note this is a mixture-of-experts model — all parameters must be resident even though only a fraction are active per token, so the memory cost follows the total, not the active count.
Where this model fits
Sized at Q4_K_M with a 4K context window, smallest card first. Comfortable means the estimate uses at most 88% of the memory.
- Runs comfortably on
- RTX 309024GB · +5.8Radeon RX 7900 XTX24GB · +5.8RTX 409024GB · +5.8Tesla P40 24G24GB · +5.8Mac M5 32G32GB · +5.8
- Tight but possible
- Radeon RX 7900 XT20GBMac M4 24G24GBMac M4 Pro 24G24GB
- Ships in
- GGUF
- Try it yourself
- Size it in the calculatorGenerate the run command
How to actually run this
Deployment guides for this model and this class of hardware.
This page's figures change when the model or the runtime does.Last updated 2026-11-17 RSS → /feed.xml