GLM-4.5-Air GGUF size and VRAM requirements
unsloth/GLM-4.5-Air-GGUF is a very large language model with 110.47 billion parameters, built on the glm4moe architecture. It is released under the mit license and has been downloaded 28,775 times.
GLM-4.5-Air-GGUF is a Mixture-of-Experts model with 128 experts, of which 8 are active on each token. Routing only 8 of 128 experts makes it noticeably faster than a dense model of the same size — but every expert still has to be held in memory, so the numbers below are set by the full parameter count, not the active one. It is built from 46 transformer layers, a hidden size of 4,096, 96 attention heads. It uses grouped-query attention (96 query heads sharing 8 key/value heads), which already trims KV-cache memory compared with full multi-head attention.
To run unsloth/GLM-4.5-Air-GGUF locally at a 4,096-token context, its quantized versions need between 37.15 GB (TQ1_0, lowest quality) and 207.34 GB (BF16, highest quality) of memory, weights plus KV cache and a system margin included. Context length drives that memory directly: at 4,096 tokens the KV cache for GLM-4.5-Air-GGUF is about 0.72 GB, rising to roughly 23.0 GB at its full 131,072-token context. Shorter prompts free up memory for a higher-quality quantization.
Available GGUF quantizations for unsloth/GLM-4.5-Air-GGUF include TQ1_0, IQ1_S, IQ1_M, IQ2_XXS, IQ2_M, Q2_K, Q2_K_L, Q2_K_XL, IQ3_XXS, Q3_K_S, Q3_K_XL, Q3_K_M, IQ4_XS, IQ4_NL, Q4_0, Q4_K_S, Q4_K_XL, Q4_1, Q4_K_M, Q5_K_S, Q5_K_XL, Q5_K_M, Q6_K, Q6_K_XL, Q8_0, Q8_K_XL, BF16. The model supports a native context length of up to 131,072 tokens; a longer context grows the KV cache and the memory needed.
GGUF file size and memory by quantization
Compare real GGUF weight sizes, estimated KV cache and total memory for Q4, Q5, Q8 and every quantization published in this repository.
| Quant. | Bits | Quality | Weights | KV | Total | Speed~ | Verdict |
|---|---|---|---|---|---|---|---|
| TQ1_0 | 2.77 | Low | 35.63 GB | 0.72 GB | 37.15 GB | — | Insufficient |
| IQ1_S | 2.79 | Low | 35.86 GB | 0.72 GB | 37.38 GB | — | Insufficient |
| IQ1_M | 2.9 | Low | 37.31 GB | 0.72 GB | 38.83 GB | — | Insufficient |
| IQ2_XXS | 3.09 | Low | 39.75 GB | 0.72 GB | 41.27 GB | — | Insufficient |
| IQ2_M | 3.21 | Low | 41.34 GB | 0.72 GB | 42.86 GB | — | Insufficient |
| Q2_K | 3.28 | Low | 42.21 GB | 0.72 GB | 43.73 GB | — | Insufficient |
| Q2_K_L | 3.29 | Low | 42.34 GB | 0.72 GB | 43.86 GB | — | Insufficient |
| Q2_K_XL | 3.44 | Fair | 44.19 GB | 0.72 GB | 45.71 GB | — | Insufficient |
| IQ3_XXS | 3.73 | Fair | 47.91 GB | 0.72 GB | 49.43 GB | — | Insufficient |
| Q3_K_S | 3.81 | Fair | 49.04 GB | 0.72 GB | 50.56 GB | — | Insufficient |
| Q3_K_XL | 3.97 | Fair | 51.02 GB | 0.72 GB | 52.54 GB | — | Insufficient |
| Q3_K_M | 4.14 | Fair | 53.28 GB | 0.72 GB | 54.79 GB | — | Insufficient |
| IQ4_XS | 4.38 | Good | 56.33 GB | 0.72 GB | 57.85 GB | — | Insufficient |
| IQ4_NL | 4.54 | Good | 58.4 GB | 0.72 GB | 59.92 GB | — | Insufficient |
| Q4_0 | 4.55 | Good | 58.47 GB | 0.72 GB | 59.99 GB | — | Insufficient |
| Q4_K_S | 4.85 | Good | 62.43 GB | 0.72 GB | 63.95 GB | — | Insufficient |
| Q4_K_XL | 4.9 | Good | 63.07 GB | 0.72 GB | 64.59 GB | — | Insufficient |
| Q4_1 | 5.03 | Very good | 64.64 GB | 0.72 GB | 66.16 GB | — | Insufficient |
| Q4_K_M | 5.28 | Very good | 67.96 GB | 0.72 GB | 69.48 GB | — | Insufficient |
| Q5_K_S | 5.68 | Very good | 73.03 GB | 0.72 GB | 74.55 GB | — | Insufficient |
| Q5_K_XL | 6.0 | Very good | 77.16 GB | 0.72 GB | 78.67 GB | — | Insufficient |
| Q5_K_M | 6.05 | Very good | 77.78 GB | 0.72 GB | 79.3 GB | — | Insufficient |
| Q6_K | 7.17 | Excellent | 92.21 GB | 0.72 GB | 93.73 GB | — | Insufficient |
| Q6_K_XL | 7.35 | Excellent | 94.58 GB | 0.72 GB | 96.1 GB | — | Insufficient |
| Q8_0 | 8.51 | Excellent | 109.39 GB | 0.72 GB | 110.91 GB | — | Insufficient |
| Q8_K_XL | 9.25 | Excellent | 118.97 GB | 0.72 GB | 120.49 GB | — | Insufficient |
| BF16 | 16.0 | Excellent | 205.82 GB | 0.72 GB | 207.34 GB | — | Insufficient |
KV cache computed from the model's exact architecture. Speed is a rough estimate bounded by memory bandwidth.
Frequently asked questions
What kind of model is unsloth/GLM-4.5-Air-GGUF?
unsloth/GLM-4.5-Air-GGUF is a language model with 110.47 billion parameters, based on the glm4moe architecture. It is released under the mit license and distributed as GGUF files for local inference.
Is unsloth/GLM-4.5-Air-GGUF a Mixture-of-Experts (MoE) model?
Yes. unsloth/GLM-4.5-Air-GGUF is a Mixture-of-Experts model with 128 experts, of which 8 are activated per token. That makes it faster than a dense model of the same size, but all 128 experts must be loaded into memory, so the VRAM/RAM it needs is driven by the total parameter count, not the active one.
How much VRAM do you need to run unsloth/GLM-4.5-Air-GGUF?
You need about 45.71 GB of VRAM to run unsloth/GLM-4.5-Air-GGUF entirely on the GPU using the Q2_K_XL quantization (at a 4,096-token context). Smaller quantizations lower the requirement at the cost of quality.
Can I run unsloth/GLM-4.5-Air-GGUF on an 8 GB GPU?
No. unsloth/GLM-4.5-Air-GGUF does not fit on an 8 GB GPU, even with the smallest quantization and system RAM offloading.
Can I run unsloth/GLM-4.5-Air-GGUF on a 16 GB GPU?
Partially. unsloth/GLM-4.5-Air-GGUF only fits on a 16 GB GPU by offloading part of it to system RAM (with Q2_K_XL), which runs but is slower.
Can I run unsloth/GLM-4.5-Air-GGUF on a 24 GB GPU?
Partially. unsloth/GLM-4.5-Air-GGUF only fits on a 24 GB GPU by offloading part of it to system RAM (with Q4_K_M), which runs but is slower.
What context length does unsloth/GLM-4.5-Air-GGUF support?
unsloth/GLM-4.5-Air-GGUF supports a native context length of up to 131,072 tokens. A longer context grows the KV cache, so it increases the memory needed to run the model.
What is the best quantization for unsloth/GLM-4.5-Air-GGUF?
For unsloth/GLM-4.5-Air-GGUF, a strong default is Q4_K_M, which needs about 69.48 GB and keeps most of the quality while roughly halving the memory versus 8-bit. With VRAM to spare, Q5_K_M or Q6_K add a little more quality; if you are tight on memory, a smaller quantization still runs. Pick the highest quantization that fits your VRAM.