RedHatAI · vision language

gemma-4-31B-it-NVFP4

RedHatAI/gemma-4-31B-it-NVFP4

gemma-4-31B-it-NVFP4 at NVFP4 is exactly 22,132,161,664 bytes (20.61 GiB / 22.13 GB) — an effective 8.911 bits per weight, not the nominal 4. Its KV cache at 32K is 6.17 GiB, not the 30.00 GiB a flat formula predicts.

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

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
NVFP420.61 GiB22,132,161,6648.911williamliao

KV cache by context

computed per layer — this model uses sliding-window attention
ContextKV cache (f16)Flat formulaOverstated byFull / windowed / recurrent
4,0961.80 GiB3.75 GiB2.09×10 / 50 / 0
8,1922.42 GiB7.50 GiB3.10×10 / 50 / 0
16,3843.67 GiB15.00 GiB4.09×10 / 50 / 0
32,7686.17 GiB30.00 GiB4.86×10 / 50 / 0
65,53611.17 GiB60.00 GiB5.37×10 / 50 / 0
131,07221.17 GiB120.00 GiB5.67×10 / 50 / 0

50 of 60 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 NVFP4 at roughly 10.41 GiB. The real file is 20.61 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 30.00 GiB at 32K context where the real figure is 6.17 GiB, because most of this model's layers cache a fixed window rather than the whole context.

Architecture

from config.json
Layers
60
Attention heads
32
KV heads
16
Head dim
256
Hidden size
5376
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-31B-it-NVFP4 need?
NVFP4 is exactly 22,132,161,664 bytes (20.61 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-31B-it-NVFP4's KV cache?
6.17 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-31B-it-NVFP4 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.