GLM-4.7 has 358.3B parameters (33B active per token). In BF16 its weights alone take 657 GiB; quantized to 4-bit, about 199 GiB. Each 32K-token request adds 11.5 GiB of KV cache. Cheapest way to run it today: 5 × RTX A6000 (48 GB) at $1.96 per hour.
Weights plus the KV cache of one request (BF16 cache), in GiB. Add 1 to 3 GiB for the inference engine itself.
Weights format
Weights only
+ 8K context
+ 32K context
+ 128K context
+ 198K context
BF16 / FP16
657
660
669
703
728
FP8 / INT8
330
333
342
376
401
4-bit (GGUF Q4_K_M)
199
201
210
245
270
GLM-4.7 GGUF files
Exact size of each quantization in unsloth/GLM-4.7-GGUF (opens in a new tab), and the smallest GPU that runs it with llama.cpp, Ollama or LM Studio and an 8K-token context.
Quantization
File size
Smallest GPU
BF16
668 GiB
More than 96 GB: see the calculator
UD-Q8_K_XL
368 GiB
More than 96 GB: see the calculator
Q8_0
355 GiB
More than 96 GB: see the calculator
UD-Q6_K_XL
280 GiB
More than 96 GB: see the calculator
Q6_K
274 GiB
More than 96 GB: see the calculator
Q5_K_M
237 GiB
More than 96 GB: see the calculator
UD-Q5_K_XL
236 GiB
More than 96 GB: see the calculator
Q5_K_S
230 GiB
More than 96 GB: see the calculator
Q4_1
209 GiB
More than 96 GB: see the calculator
Q4_K_M
202 GiB
More than 96 GB: see the calculator
UD-Q4_K_XL
191 GiB
More than 96 GB: see the calculator
Q4_K_S
190 GiB
More than 96 GB: see the calculator
Q4_0
189 GiB
More than 96 GB: see the calculator
IQ4_NL
189 GiB
More than 96 GB: see the calculator
IQ4_XS
178 GiB
More than 96 GB: see the calculator
Q3_K_M
160 GiB
More than 96 GB: see the calculator
UD-Q3_K_XL
148 GiB
More than 96 GB: see the calculator
Q3_K_S
144 GiB
More than 96 GB: see the calculator
UD-IQ3_XXS
135 GiB
More than 96 GB: see the calculator
UD-Q2_K_XL
126 GiB
More than 96 GB: see the calculator
Q2_K_L
122 GiB
More than 96 GB: see the calculator
Q2_K
122 GiB
More than 96 GB: see the calculator
UD-IQ2_M
114 GiB
More than 96 GB: see the calculator
UD-IQ2_XXS
108 GiB
More than 96 GB: see the calculator
UD-IQ1_M
100 GiB
More than 96 GB: see the calculator
UD-IQ1_S
90.5 GiB
More than 96 GB: see the calculator
UD-TQ1_0
78.7 GiB
RTX PRO 6000 Blackwell (96 GB)
Read every day from Hugging Face. Split files are added together; vision projectors are left out.
How many GPUs to run GLM-4.7
Fewest GPUs that fit the weights plus one 8K-token request. Data-center GPUs use vLLM (90% of memory usable), the others llama.cpp. Several GPUs split the model with tensor or pipeline parallelism.
GPU
BF16 / FP16
8-bit
4-bit
GeForce RTX 4090 24 GB
48 (several servers)
24 (several servers)
16 (several servers)
GeForce RTX 5090 32 GB
24 (several servers)
16 (several servers)
7
RTX PRO 6000 Blackwell 96 GB
8
4
3
Mac M5 Max 128 GB 96 GB usable
8
4
3
NVIDIA H100 80 GB
16 (several servers)
5
3
NVIDIA H200 141 GB
6
3
2
NVIDIA B200 (HGX) 180 GB
5
3
2
8-bit: FP8 with vLLM (INT8 on GPUs without FP8), Q8_0 with llama.cpp. 4-bit: AWQ / GPTQ with vLLM, Q4_K_M with llama.cpp, both counted at the Q4_K_M size.
Cheapest way to run GLM-4.7 today
For each GPU: the fewest cards that fit GLM-4.7 with one 8K-token request, the most faithful weight format at that count, and the cheapest on-demand price (2026-10-14).
On-demand prices from RunPod, Vast.ai, Azure, Oracle Cloud, OVHcloud, Scaleway, Verda and Akash, checked every hour. Serving many users needs more KV cache, so more memory: size it in the calculator. Some links are affiliate links: StudioTV may earn a commission, at no extra cost to you.
KV cache: how memory grows with context
Architecture: 92 layers · 92 full attention (8 KV × 128). Every layer keeps keys and values for every token (grouped-query attention), so the cache grows linearly with context. Only 33B parameters are active per token, but all 358B must sit in memory: VRAM depends on the total, speed on the active part.
Context per request
BF16 cache
FP8 cache
8K tokens
2.88 GiB
1.44 GiB
32K tokens
11.5 GiB
5.75 GiB
128K tokens
46.0 GiB
23.0 GiB
198K tokens
71.2 GiB
35.6 GiB
GLM-4.7 VRAM FAQ
How much VRAM does GLM-4.7 need?
In BF16 the weights alone take 657 GiB (706 GB). In FP8 that is 330 GiB, and about 199 GiB with 4-bit quantization (Q4_K_M). Each request then adds KV cache: 2.88 GiB at 8K tokens and 11.5 GiB at 32K (BF16 cache).
Can GLM-4.7 run on a single RTX 4090 (24 GB)?
No. Even in 4-bit it needs 16 (several servers) RTX 4090s. In 4-bit it needs 3 H100 GPUs.
What is the cheapest way to run GLM-4.7?
On 2026-10-14, the cheapest on-demand setup is 5 × RTX A6000 (48 GB) with Q4_K_M weights on Vast.ai, at $1.96 per hour (about $1,427.15 per month). Next: 5 × RTX 6000 Ada (48 GB) with Q4_K_M weights on Vast.ai, at $2.81 per hour. Sized for one 8K-token request; prices are checked every hour.
How many H100 GPUs does GLM-4.7 need?
With one request and an 8K-token context: 16 (several servers) in BF16, 5 in FP8 and 3 in 4-bit (vLLM, 90% of memory usable). Serving many users at once needs more memory for their KV caches: the calculator sizes that for you.
GLM-4.7 VRAM badge
For a model card or a README: the 4-bit size and the smallest GPU it fits on, linked to this page. Data as JSON: /api/models/glm-4-7.json.
Estimates, not guarantees: computed from the official config.json with the same engine as the LLM VRAM Calculator. Real usage depends on your engine version and settings.