GLM-4.5-Air VRAM Requirements

GLM-4.5-Air needs about 62.1 GB of VRAM at Q4_K_M with an 8K context: 59.8 GB for weights, 1.4 GB for the KV cache and 0.9 GB of runtime overhead. At Q8_0 it needs 107 GB and at full FP16 precision 200 GB. The smallest GPU that runs it fully is the A100 80GB.

By Z.ai · Updated October 14, 2026 · Values from config.json on Hugging Face

62.1 GB VRAM

GLM-4.5-Air at Q4_K_M with 8K context and the KV cache in FP16.

  • Weights 59.8 GB
  • KV cache 1.4 GB
  • Runtime overhead 0.9 GB

Mixture of experts: all 106B parameters need memory, but only 12B are read per token, so it runs at the speed of a much smaller model.

Which GPUs can run it

Multi-GPU: about 3× 24 GB cards (RTX 3090 / 4090) with the model split across them.

GLM-4.5-Air VRAM by quantization

Total memory with an FP16 KV cache. "Smallest tier" is the smallest standard VRAM size with a 6% safety margin at 8K.

QuantizationBits/weightWeightsTotal at 8KTotal at 32KSmallest tier
Q4_K_M4.8559.8 GB62.1 GB66.5 GB80 GB
Q5_K_M5.6970.2 GB72.5 GB76.8 GB80 GB
Q6_K6.5981.3 GB83.6 GB87.9 GB96 GB
Q8_08.50105 GB107 GB111 GB128 GB
FP16 / BF1616.00197 GB200 GB204 GBMulti-GPU / server
Q3_K_M3.9148.2 GB50.5 GB54.9 GB64 GB
Q2_K3.0037.0 GB39.3 GB43.6 GB48 GB

VRAM by context length

At Q4_K_M. The KV cache grows linearly with context: 0.18 GB per 1,000 tokens in FP16.

ContextKV cache (FP16)KV cache (Q8_0)Total, FP16 cacheTotal, Q8_0 cache
4K tokens0.7 GB0.4 GB61.4 GB61.1 GB
8K tokens1.4 GB0.8 GB62.1 GB61.5 GB
32K tokens5.8 GB3.1 GB66.5 GB63.8 GB
128K tokens23.0 GB12.2 GB83.7 GB72.9 GB

GPUs that can run GLM-4.5-Air

At Q4_K_M with 8K context. "Best quant" is the highest-quality format that fits fully; "max context" is at Q4_K_M.

GPUUsable memoryStatusBest quantMax contextSpeed
A100 80GB80.0 GBFitsQ5_K_M80K~94 tok/s
H100 80GB SXM80.0 GBFitsQ5_K_M80K~121 tok/s
Ryzen AI Max+ 395 128GB96.0 GBFitsQ6_K128K~18 tok/s
Apple M3 Max 128GB96.0 GBFitsQ6_K128K~28 tok/s
Apple M4 Max 128GB96.0 GBFitsQ6_K128K~37 tok/s
Apple M5 Max 128GB96.0 GBFitsQ6_K128K~40 tok/s
RTX PRO 6000 Blackwell 96GB96.0 GBFitsQ6_K128K~87 tok/s
NVIDIA DGX Spark 128GB112 GBFitsQ6_K128K~19 tok/s
NVIDIA H200 141GB141 GBFitsQ8_0128K~139 tok/s
Apple M2 Ultra 192GB144 GBFitsQ8_0128K~50 tok/s
AMD Instinct MI300X 192GB192 GBFitsQ8_0128K~136 tok/s
Apple M3 Ultra 512GB384 GBFitsFP16 / BF16128K~51 tok/s
RTX 6000 Ada 48GB48.0 GB73% on GPUQ2_K–~15 tok/s
RTX A6000 48GB48.0 GB73% on GPUQ2_K–~15 tok/s
L40S 48GB48.0 GB73% on GPUQ2_K–~15 tok/s
A100 40GB40.0 GB61% on GPU––~12 tok/s
RTX 5090 32GB32.0 GB48% on GPU––~9.4 tok/s
Radeon AI PRO R9700 32GB32.0 GB48% on GPU––~8.7 tok/s

Multi-GPU: about 3× 24 GB cards (RTX 3090 or 4090) run it at Q4_K_M, using tensor or layer splitting in llama.cpp, vLLM or ExLlamaV2.

About GLM-4.5-Air

A 106B mixture-of-experts with 12B active parameters that became a favourite for 96–128 GB machines. It uses standard grouped-query attention across 46 layers, so a long context adds memory steadily: 184 KB per token in FP16. Strong at coding and tool use for its active size.

SpecValue
Parameters106B total, 12B active (MoE)
Layers46
Hidden size4096
Attention heads / KV heads96 / 8
Head dimension128
Vocabulary151,552
Max context (used here)128K tokens
KV cache per token (FP16)184 KB
Released2025-07
LicenseMIT

GLM-4.5-Air VRAM: common questions

Can GLM-4.5-Air run on 64GB of RAM and a 24GB GPU?

Yes with partial offload. Keep attention and shared layers on the GPU and the experts in system RAM; with only 12B active parameters it still reaches usable speed.

How much VRAM does GLM-4.5-Air need?

About 62.1 GB at Q4_K_M with an 8K context, 107 GB at Q8_0 and 200 GB at FP16. Longer contexts add 0.18 GB per 1,000 tokens with an FP16 cache.

What is the cheapest GPU that can run GLM-4.5-Air?

The smallest listed device that fits it fully at Q4_K_M with 8K context is the A100 80GB (80.0 GB usable). With 24 GB cards you need about 3 of them.

Does GLM-4.5-Air need VRAM for all 106B parameters?

Yes. All experts must be loaded because any token can use any expert. Only 12B parameters are read per token, so it generates text about as fast as a 12B dense model.

Related