How to Deploy GLM 5.3 Flash Locally
GLM 5.3 Flash is a 320B MoE that Zhipu released in August 2026, and it uses 18B parameters per token. It has 1M of context and an MIT license, and it is the first model in the GLM 5 series that natively understands images. A 128GB machine can run its 2-bit version (about 109 GB) at about 28 to 29 tokens/s; 4-bit is about 200 GB and needs a 512GB Mac Studio, two DGX Sparks or several high-VRAM cards. Its long context is especially light: even the full 1M takes only about 11 GB more than 32K.
GLM 5.3 Flash details
- Min VRAM at 4-bit201 GB · 8K
- Parameters320B
- Active params18B
- Max context1M
- Architecture
- MoE
- Experts offloaded
- 9 GB VRAM + 194 GB RAM
- License
- MIT
- Launch date
- Aug 26, 2026
- Vendor
- Z.ai / Zhipu AI
- Hugging Face repo
- zai-org/GLM-5.3-Flash
- GGUF repo
- unsloth/GLM-5.3-Flash-GGUF
- NVFP4 repo (Blackwell)
- nvidia/GLM-5.3-Flash-NVFP4
- MLX repo (Apple)
- mlx-community/GLM-5.3-Flash-4bit
- Layers
- 45
- Hidden size
- 4,096
- KV heads
- 64
- Head dim
- 256
How much VRAM does GLM 5.3 Flash need for local deployment?
| Quantization | WeightsGB | 32K contextGB | 128K contextGB | 256K contextGB | 1M context (max)GB |
|---|---|---|---|---|---|
| 1-bit | 97.6GGUF | 99 | 100.2 | 101.6 | 110.5 |
| 2-bit | 108.7GGUF | 110.1 | 111.3 | 112.7 | 121.6 |
| 3-bit | 147.5GGUF | 148.9 | 150.1 | 151.5 | 160.4 |
| 4-bit | 199.7GGUF | 201.1 | 202.3 | 203.7 | 212.6 |
| 5-bit | 240.3GGUF | 241.7 | 242.9 | 244.3 | 253.2 |
| 8-bit | 341GGUF | 342.4 | 343.6 | 345 | 353.9 |
| BF16/FP16 | 641.6GGUF | 643 | 644.2 | 645.6 | 654.5 |
Full calculation rules are on the Methodology page.
Can a single GPU run GLM 5.3 Flash?
Not on any single GPU, but a 128GB unified-memory machine can run it at 2-bit. The 2-bit weights are about 109 GB, just too big for a 96GB RTX PRO 6000. The DGX Spark and Ryzen AI Max+ 395 fit it and run at 28 to 29 tokens/s, since each token reads only 18B parameters, and because most of its layers use a fixed amount of memory no matter how long the context gets, both can open the full window. The trade-off is quality: in Unsloth's tests 3-bit is clearly more accurate than 2-bit, but the standard 3-bit file won't fit in 128GB. For 4-bit on a single machine, only the 512GB Mac Studio M3 Ultra will do, at about 44 tokens/s.
| Device | Price | Speed t/s | Max context |
|---|---|---|---|
| Ryzen AI Max+ 395 128GBWhole system · 128 GB | $4,46420 listings | 27.7 | 1M |
| MacBook Pro M5 Max 128GBWhole system · 128 GB | $7,54920 listings | 56.2 | 1M |
| $8,08123 listings | 29.3 | 1M | |
| Mac Studio M3 Ultra 512GBWhole system · 512 GB | $22,90013 listings | 68.9 | 1M |
| Device | Price | Speed t/s | Max context |
|---|---|---|---|
| Mac Studio M3 Ultra 512GBWhole system · 512 GB | $22,90013 listings | 44.1 | 1M |
| Device | Price | Speed t/s | Max context |
|---|---|---|---|
| Mac Studio M3 Ultra 512GBWhole system · 512 GB | $22,90013 listings | 28.3 | 1M |
Only common GPUs and systems are listed, one set for models under 50B and another for larger ones, sorted by price from low to high.
How many GPUs do you need to run GLM 5.3 Flash?
The easiest 4-bit setup is two DGX Spark units joined by a single direct cable, no switch needed, for 256GB total, though it only does about 17 tokens/s. For speed, four 96GB RTX PRO 6000 cards reach about 77 tokens/s, and two are enough for 2-bit, which is faster still. 24GB cards need eight to cover 2-bit, and software is the bigger catch: the official vLLM recipe currently supports only recent NVIDIA cards, which rules out older ones like the RTX 3090, 4090 and A6000 as well as AMD's RX 7900 XTX. On those you'd use llama.cpp to split layers across the cards, which is usually slower than vLLM for a single user.
| Device | Cards | Total price | Total VRAM | Speed t/s | Total power |
|---|---|---|---|---|---|
| 4 cards | $3,580 | 128 GB | 72.3 | 1,000 W | |
| 4 cards | $7,400 | 128 GB | 54.9 | 920 W | |
| Instinct MI21064 GB per card | 2 cards | $9,988 | 128 GB | 103 | 600 W |
| Radeon RX 7900 XTX24 GB per card | 8 cards | $10,000 | 192 GB | 75.4 | 2,840 W |
| 8 cards | $14,392 | 192 GB | 74.2 | 2,800 W | |
| 4 cards | $19,596 | 192 GB | 65 | 1,200 W | |
| 2 cards | $21,444 | 144 GB | 92.5 | 600 W | |
| 8 cards | $30,064 | 192 GB | 77.8 | 3,600 W | |
| 4 cards | $33,188 | 128 GB | 107.7 | 2,300 W | |
| 2 cards | $37,998 | 160 GB | 111.8 | 600 W | |
| 2 cards | $44,700 | 192 GB | 107.7 | 1,200 W | |
| 4 cards | No price | 192 GB | 77.8 | 1,800 W |
| Device | Cards | Total price | Total VRAM | Speed t/s | Total power |
|---|---|---|---|---|---|
| 8 cards | $7,160 | 256 GB | 47.1 | 2,000 W | |
| 8 cards | $14,800 | 256 GB | 34.3 | 1,840 W | |
| 2 units | $16,162 | 256 GB | 16.9 | 480 W | |
| Instinct MI21064 GB per card | 4 cards | $19,976 | 256 GB | 72.5 | 1,200 W |
| 8 cards | $39,192 | 384 GB | 41.5 | 2,400 W | |
| 4 cards | $42,888 | 288 GB | 63.4 | 1,200 W | |
| 8 cards | $66,376 | 256 GB | 76.9 | 4,600 W | |
| 4 cards | $75,996 | 320 GB | 80.7 | 1,200 W | |
| 4 cards | $89,400 | 384 GB | 76.9 | 2,400 W | |
| 8 cards | No price | 384 GB | 51.4 | 3,600 W |
| Device | Cards | Total price | Total VRAM | Speed t/s | Total power |
|---|---|---|---|---|---|
| 4 units | $32,324 | 512 GB | 10.3 | 960 W | |
| 8 cards | $39,192 | 384 GB | 26.6 | 2,400 W | |
| Instinct MI21064 GB per card | 8 cards | $39,952 | 512 GB | 49.7 | 2,400 W |
| 8 cards | $85,776 | 576 GB | 42.6 | 2,400 W | |
| 4 cards | $89,400 | 384 GB | 53.2 | 2,400 W | |
| 8 cards | $151,992 | 640 GB | 56.3 | 2,400 W | |
| 8 cards | No price | 384 GB | 33.6 | 3,600 W |
Full calculation rules are on the Methodology page.
What PC or server build do you need to run GLM 5.3 Flash locally?
With the experts in system RAM, 2-bit runs on an ordinary desktop: a DDR5 desktop with 128GB of RAM and a 16GB Tesla V100 does about 21 tokens/s, and a DDR4 one about 13; an 8-channel DDR4 server with an RTX 3090 does about 34, and a 12-channel DDR5 server with an RTX PRO 6000 about 104. 4-bit needs an 8-channel DDR4 server (fully populated with 256GB) with an RTX 3090, at about 19 tokens/s, or about 56 on a 12-channel DDR5 server. KTransformers has a dedicated guide for this model, linked from the model card.
Tesla V100 32GB + Dual Xeon E5 DDR4
BudgetGeForce RTX 3090 + Dual EPYC DDR4
Best valueGeForce RTX 5090 + Single EPYC DDR5
FlagshipTesla V100 32GB + Dual Xeon E5 DDR4
BudgetGeForce RTX 3090 + Dual EPYC DDR4
Best valueGeForce RTX 5090 + Single EPYC DDR5
FlagshipTesla V100 32GB + Dual Xeon E5 DDR4
BudgetGeForce RTX 3090 + Dual EPYC DDR4
Best valueGeForce RTX 5090 + Dual EPYC DDR5
Flagship2 × RTX PRO 6000 + Dual EPYC DDR5
Giant modelsDetailed calculation rules are on the Methodology page.
As an eBay Partner, VRAMGlass may be compensated if you buy through the eBay links on this page. The price you pay stays the same.
What to know before running GLM 5.3 Flash locally
Which quantization to pick
Unsloth measured how often each quant picks the same top token as the original model: about 78% for 2-bit (about 109 GB), about 86% for 3-bit (about 148 GB) and about 92% for 4-bit (about 200 GB). 3-bit is about 8 percentage points above 2-bit, so if you have the memory, we recommend at least 3-bit. But that 3-bit quant doesn't fit on a 128GB device; for 128GB devices, Unsloth's demo uses a smaller 3-bit quant, UD-IQ3_XXS (about 82%).
Mainline llama.cpp runs it now
Mainline llama.cpp merged support on September 30, 2026 (PR #27773), covering both text and images. Unsloth updated its GGUF shards on October 5 to match the mainline changes, so stock llama.cpp now loads them and you no longer need their fork. MTP speculative decoding also landed in mainline on October 7 (PR #29928), which speeds up generation at long context. The glm-5.3-flash entry in the Ollama library only has a :cloud tag, which calls a cloud service rather than running locally.
vLLM limitations
The vLLM recipe requires Hopper or newer NVIDIA cards and FlashInfer 0.6.17 or later, and on NVIDIA you need the vllm/vllm-openai:glm53-flash image for now. On Hopper, this model doesn't support storing the context cache in FP8. The official main repository holds FP8 weights; BF16 lives separately in GLM-5.3-Flash-BF16.
Thinking levels
Usage is the same as for GLM 5.3: there are only three levels, low, high and max, with max as the default, and you should turn on
clear_thinkingfor chat. Unsloth's parameters aretemperature1.0 andtop_p0.95 for general tasks, andtemperature0.95 andtop_p1.0 for coding tasks like DeepSWE.Why long context takes almost no VRAM
34 of its 45 layers use linear attention (the same kind as Kimi K3). These layers store only a fixed-size state that doesn't grow with context; only the cache in the other 11 layers grows. So at 4-bit, going from 32K to 1M adds only about 11 GB.
Launch commands
llama.cpp
- NVIDIA
- AMD
- Mac
- CPU
llama-server -hf unsloth/GLM-5.3-Flash-GGUF:UD-Q4_K_XL -c 8192Short on VRAM? Add --cpu-moe to keep the routed experts in system RAM (about 194 GB needed).
llama-server -hf unsloth/GLM-5.3-Flash-GGUF:UD-Q4_K_XL -c 8192 -ngl 99 \ --cpu-moe
vLLM
- Linux
- NVIDIA
Follow the deployment guide to prepare the required runtime and hardware.
vllm serve zai-org/GLM-5.3-Flash \ --tensor-parallel-size 4 \ --speculative-config '{"method":"mtp","num_speculative_tokens":5}' \ --tool-call-parser glm47 \ --reasoning-parser glm47 \ --enable-auto-tool-choice \ --served-model-name zai-org/GLM-5.3-Flash
MLX
- Apple Silicon
Vision models run on mlx-vlm: on a Mac, pip install mlx-vlm first; this command downloads the MLX weights from Hugging Face and starts a server.
mlx_vlm.server --model mlx-community/GLM-5.3-Flash-4bitOllama
- Windows
- macOS
- Linux
Ollama only has a cloud version, glm-5.3-flash:cloud, which runs on Ollama's servers rather than on your machine.
File names follow that week's model-library snapshot; the definitions are in the methodology. Methodology
Other models in the GLM family
| Model | Total params | Active params | 4-bit size |
|---|---|---|---|
| 30B | 3B | 18.3 GB | |
| 106B | 12B | 73 GB | |
| 744B | 40B | 465.8 GB | |
| 744B | 40B | 467.3 GB |