Can I run gemma-4-31B-it-NVFP4 on a 16GB card?

No. No published quantization of gemma-4-31B-it-NVFP4 fits a 16GB card at any context with q4_0 KV cache.

How much VRAM does gemma-4-31B-it-NVFP4 need?

Its published quantizations range from 20.61 GiB to 20.61 GiB in weights alone, before KV cache and runtime overhead.

Does gemma-4-31B-it-NVFP4 fit in 16GB of VRAM?

Not at these settings. No indexed quantization of gemma-4-31B-it-NVFP4 fits 16GB card at any context we compute, with q4_0 KV. The smallest shipped quantization is 20.61 GiB in weights alone, against 14.88 GiB usable. CPU offload can still run it, slowly.

From the file· weights summed from filesFrom the file· KV computed per layerPredicted· speed and compute buffer

KV cache dtypef16 q8_0 q4_0— 16 GB card, 14.88 GiB usable after overhead

Every quantization at every context

total memory required; green fits, red does not

Quant	Weights●	4K◐	8K◐	16K◐	32K◐	64K◐	128K◐
NVFP4	20.61 GiB	22.0	22.2	22.5	23.2	24.6	27.4

●From the file◐Predictedwhat these mean

Figures are GiB of total memory: weights plus KV cache plus compute buffer and backend overhead. Weights and KV are near-exact; the overhead term is modeled. Hover any cell for the breakdown.

Why there are no speeds on this page

A capacity is not a card. Whether a model fits depends only on memory, so every figure above holds for any 16GB accelerator. How fast it runs depends on memory bandwidth, which varies several-fold between cards of the same capacity — so putting a tokens-per-second number here would be inventing one. Pick a specific card from hardware and the speed column appears.

Why other calculators disagree

A parameters × bits ÷ 8 estimate ignores two things that dominate at long context. First, the weights themselves are not the nominal rate — quantizations are mixtures, so the real file is consistently larger than the label implies. Second, most of this model's layers cache only a 1,024-token window rather than the full context.