What GPU do I need to run RedHatAI/gemma-4-26B-A4B-it-FP8-dynamic?

26.5B parameters, published in F8_E4M3. View on Hugging Face

26.5B
Parameters
F8_E4M3
Native precision
Gemma4ForConditionalGeneration
Architecture
image-text-to-text
Pipeline

gemma-4-26B-A4B-it-FP8-dynamic is published by RedHatAI on Hugging Face, with 731,600 downloads and 40 likes to date. It's a Gemma4ForConditionalGeneration model built for image-text-to-text, published natively in F8_E4M3.

VRAM required & cheapest live GPU fit

Required VRAM = weight size at each precision times a flat 1.2 overhead for activations and fragmentation. The KV-cache grows with context and is not in that factor; it is listed per model below where the architecture is published. Full formula and assumptions: methodology.

PrecisionWeight sizeRequired VRAMCheapest live fitGPUs neededEst. $/hr (full fit)
FP8 (native)24.7 GB29.7 GBRTX 4080 Super1$0.338/hr
INT4 (quantized)12.4 GB14.8 GBRTX A50001$0.176/hr

A GPU is only matched to a row if its hardware supports that precision, and the primary recommendation is always a single-GPU fit when one exists.

INT4 requires a quantized checkpoint actually published for this model, check its Hugging Face page before relying on this row.

Cheapest way to run gemma-4-26B-A4B-it-FP8-dynamic at its published (F8_E4M3) precision: 1× RTX 4080 Super, at $0.338/hr per GPU ($0.338/hr total). Quantizing to FP8 or INT4 (rows above) can cost less, but requires a compatible quantized checkpoint to exist for this model.

gemma-4-26B-A4B-it-FP8-dynamic: KV cache by context length

The KV cache is the memory the attention layers hold for every token of context, on top of the weights. It is not part of the flat 1.2x overhead in the table above, grows with context length and with every concurrent request, and is why a long-context deployment needs more VRAM than the table shows.

Sliding-window attention: windowed layers stop growing at the window, the full-attention layers keep growing. Cached per token: 245,760 bytes at 16-bit while the context is inside the window.

ContextKV cache, one sequence
4K0.35 GB
32K1.4 GB
128K5.2 GB
256K (model maximum)10.2 GB

Computed from the layer, head and window counts in the model's own configuration (RedHatAI/gemma-4-26B-A4B-it-FP8-dynamic), at 16 bits per cached value. Each concurrent sequence needs its own cache, on top of the weights.

gemma-4-26B-A4B-it-FP8-dynamic: common questions

Does gemma-4-26B-A4B-it-FP8-dynamic fit on a 32 GB GPU?

Yes. At FP8 (native) it needs 29.7 GB of VRAM, so a 32 GB card holds it with 2.3 GB to spare. A 24 GB card is not enough for it at FP8 (native).

Is gemma-4-26B-A4B-it-FP8-dynamic already quantized?

Yes. It is published in FP8, one byte per parameter, so the 29.7 GB figure is already a quantized footprint rather than a full-precision one. Only INT4 goes below it, at 14.8 GB. A GPU without FP8 tensor cores cannot run it as published, which is why cards here are matched on precision support and not on VRAM alone.

What is the least VRAM gemma-4-26B-A4B-it-FP8-dynamic can run in?

14.8 GB, at INT4 (quantized), which fits a 16 GB card, against 29.7 GB at FP8 (native). That row assumes an INT4 checkpoint has actually been published for this model, so check its Hugging Face page before planning around it.

Does quantizing gemma-4-26B-A4B-it-FP8-dynamic lower the GPU bill?

Yes. At FP8 (native) the cheapest live fit is one RTX 4080 Super at $0.338/hr. At INT4 (quantized) it drops to one RTX A5000 at $0.176/hr, provided a quantized checkpoint exists for it.

Weight-to-VRAM math, the fit rules, and how live prices are normalized: full methodology.

More Gemma 4 models

All 42 Gemma 4 models: VRAM and GPU requirements

Lineage

Based on gemma-4-26B-A4B-it.

Alternatives at this size

Other models for image-text-to-text within about a third of gemma-4-26B-A4B-it-FP8-dynamic's 26.5B parameters, from other model lines.

More on gemma-4-26B-A4B-it-FP8-dynamic

Related reading: H100 pricing and specs, How much VRAM you need for LLMs, Serving LLMs with vLLM, vLLM vs TensorRT-LLM vs SGLang, and Best GPU for LLM inference.

Submit the job. Everything after that is ours.

Sign up in 60 seconds. Pay for the GPU minutes you actually use.

© 2026 Aquanode. All rights reserved.

All trademarks, logos and brand names are the property of their respective owners.