google · text

gemma-4-26B-A4B-it-assistant

google/gemma-4-26B-A4B-it-assistant

gemma-4-26B-A4B-it-assistant at Q4_K_M is exactly 325,452,000 bytes (0.30 GiB / 0.33 GB) — an effective 6.203 bits per weight, not the nominal 4. Its KV cache at 32K is 0.29 GiB, not the 1.00 GiB a flat formula predicts.

From the file· summed from 1 file(s)From the file· KV per layer
Parameters
420M
Architecture
gemma4-assistant
4 layers
Context
262,144
native (config.json)
License
apache-2.0

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
IQ4_NL0.30 GiB321,126,4966.121RachidAR
Q4_00.30 GiB321,126,4966.121RachidAR
Q4_K_S0.30 GiB321,126,6246.121AtomicChat
Q4_K_M0.30 GiB325,452,0006.203AtomicChat
Q4_K_M0.31 GiB329,777,2486.286RachidAR
Q5_K_M0.32 GiB342,261,9846.524AtomicChat
Q5_K_M0.32 GiB344,490,0806.566RachidAR
Q6_K0.34 GiB360,122,4646.864RachidAR
Q8_00.43 GiB461,765,3128.802Radamanthys11
Q8_00.43 GiB461,766,7528.802RachidAR
Q8_00.43 GiB461,766,8808.802AtomicChat
F160.80 GiB855,227,04016.301Radamanthys11
BF160.80 GiB855,228,51216.301RachidAR
F160.80 GiB855,228,64016.301AtomicChat

KV cache by context

computed per layer — this model uses sliding-window attention
ContextKV cache (f16)Flat formulaOverstated byFull / windowed / recurrent
4,0960.07 GiB0.13 GiB1.88×1 / 3 / 0
8,1920.10 GiB0.25 GiB2.56×1 / 3 / 0
16,3840.16 GiB0.50 GiB3.12×1 / 3 / 0
32,7680.29 GiB1.00 GiB3.51×1 / 3 / 0
65,5360.54 GiB2.00 GiB3.74×1 / 3 / 0
131,0721.04 GiB4.00 GiB3.86×1 / 3 / 0

3 of 4 layers cache only a 1,024-token window rather than the full context, on a period of . Figures assume the default configuration; --swa-full disables the saving entirely.

Compare with

same modality, comparable size

Will it run on your card?

full quant x context sweep

Why other calculators give a different number

A parameters × bits ÷ 8 estimate puts Q4_K_M at roughly 0.22 GiB. The real file is 0.30 GiB, because a quantization is a mixture and some tensors are always kept at higher precision. The larger discrepancy is the cache: a flat formula gives 1.00 GiB at 32K context where the real figure is 0.29 GiB, because most of this model's layers cache a fixed window rather than the whole context.

Architecture

from config.json
Layers
4
Attention heads
16
KV heads
8
Head dim
256
Hidden size
1024
Vocab
262,144
Sliding window
1024
SWA period
MLA
no
Experts
Experts per token
use_sliding_window

Questions people ask

How much VRAM does gemma-4-26B-A4B-it-assistant need?
Q4_K_M is exactly 325,452,000 bytes (0.30 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
How large is gemma-4-26B-A4B-it-assistant's KV cache?
0.29 GiB at 32K context with an f16 cache, computed per layer. Quantizing the cache to q8_0 roughly halves it, which is often the difference between a context length fitting and not.
Which quantization of gemma-4-26B-A4B-it-assistant should I use?
Q4_K_M is the usual default. Pick the largest quantization that fits your card at the context you actually need — the table above gives exact sizes for every one published.