Skip to content
RfRigFit

Yes. Gemma 4 26B-A4B fits on the Framework Desktop 128GB at FP16, with 34.1 GB of headroom. Usable memory is 96.0 GB.

Can the Framework Desktop 128GB run Gemma 4 26B-A4B?

Data updated . Last reviewed the same day, when this catalog snapshot was written.

Usable memory on this 128 GB unified-memory config is 96.0 GB (75% of the sticker figure). A result under 2 GB of headroom is labeled tight.

Quant ladder

Estimated memory for Gemma 4 26B-A4B on Framework Desktop 128GB
QuantEstimateHeadroomEst. tok/sVerdict
Q417.3 GB78.7 GB103 tok/sYes
Q827.2 GB68.8 GB64.7 tok/sYes
FP1661.9 GB34.1 GB33.7 tok/sYes

KV cache at 8K and 32K

FP16 KV-cache estimate: 0.3 GB at 8,192 tokens and 1.3 GB at 32,768 tokens. GQA counts two tensors (K and V) for the stored KV heads and head dimension. config.json also sets a sliding window of 1,024 tokens. The figures above assume every counted layer stores the full context, so they can overstate cache on sliding layers.

Offload

This machine has one memory pool. Weights are not offloaded to a second bank of system RAM.

Ollama

This command pulls the Q4_K_M file from unsloth/gemma-4-26B-A4B-it-GGUF, the Hub repo whose file size is used above. It is not an official Ollama library tag.

ollama run hf.co/unsloth/gemma-4-26B-A4B-it-GGUF:Q4_K_M

Other picks

All hardware for Gemma 4 26B-A4B · All models for the Framework Desktop 128GB

Questions

How much memory does Gemma 4 26B-A4B need at Q4?
The Q4 figure used here is 17.3 GB. GGUF file size plus an FP16 KV-cache estimate at 8,192 tokens. The cache counts only the layers and heads named in the method on the About page.
Can the Framework Desktop 128GB run Gemma 4 26B-A4B?
Yes. Gemma 4 26B-A4B fits on the Framework Desktop 128GB at FP16, with 34.1 GB of headroom. Usable memory is 96.0 GB.
What is the cheapest catalog device that runs Gemma 4 26B-A4B at Q4?
Radeon RX 7900 XT, list price $899.
How fast is Gemma 4 26B-A4B on the Framework Desktop 128GB, as a bandwidth estimate?
About 33.7 tok/s at FP16. That is device bandwidth divided by active weight bytes, not a measured run.