Qwen2.5 Coder 32B Instruct Abliterated needs about 22.5 GB of memory at Q4_K_M (a 19.9 GB file) with an 8K context window, so it fits on a 24 GB GPU. This repository has 26 quants, from 10.0 GB (IQ2_XS) to 65.5 GB (F16). Longer context needs more: at 32K tokens the KV cache alone adds about 8.6 GB.
Qwen2.5 Coder 32B Instruct Abliterated – a 32B coding‑focused LLM
Qwen2.5 Coder 32B Instruct Abliterated is a 32‑billion‑parameter model designed for coding tasks. It supports a 32,768‑token context window and is released under the Apache‑2.0 license. The model is available in multiple GGUF quantizations for llama.cpp.
Good at
- Large‑scale code generation
- Complex programming logic
- Long‑context code understanding
Limits
- No vision support
- Requires large VRAM for full precision
- License is Apache‑2.0
Best for
- Developing code assistants
- Generating long scripts
- Analyzing large codebases
Who it’s for. Engineers and researchers needing a high‑capacity coding model. The model is suitable for local deployment with sufficient GPU memory.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| IQ2_XS | 10.0 GB | 12.6 GB | Too big | Get file → | |
| IQ2_S | 10.4 GB | 13.0 GB | Too big | Get file → | |
| IQ2_M | 11.3 GB | 13.9 GB | Too big | Get file → | |
| Q2_K | 12.3 GB | 15.0 GB | Too big | Get file → | |
| Q2_K_L | 13.1 GB | 15.7 GB | Too big | Get file → | |
| IQ3_XS | 13.7 GB | 16.4 GB | Too big | Get file → | |
| Q3_K_S | 14.4 GB | 17.0 GB | Too big | Get file → | |
| IQ3_M | 14.8 GB | 17.5 GB | Too big | Get file → | |
| Q3_K_M | 15.9 GB | 18.6 GB | Too big | Get file → | |
| Q3_K_L | 17.2 GB | 19.9 GB | Too big | Get file → | |
| IQ4_XS | 17.7 GB | 20.3 GB | Too big | Get file → | |
| Q3_K_XL | 17.9 GB | 20.6 GB | Too big | Get file → | |
| Q4_0 | 18.6 GB | 21.3 GB | Too big | Get file → | |
| Q4_0 | 18.6 GB | 21.3 GB | Too big | Get file → | |
| Q4_0 | 18.6 GB | 21.3 GB | Too big | Get file → | |
| Q4_0 | 18.7 GB | 21.4 GB | Too big | Get file → | |
| Q4_K_S | 18.8 GB | 21.4 GB | Too big | Get file → | |
| Q4_K_M | 19.9 GB | 22.5 GB | Too big | Get file → | |
| Q4_K_L | 20.4 GB | 23.1 GB | Too big | Get file → | |
| Q5_K_S | 22.6 GB | 25.3 GB | Too big | Get file → | |
| Q5_K_M | 23.3 GB | 25.9 GB | Too big | Get file → | |
| Q5_K_L | 23.7 GB | 26.4 GB | Too big | Get file → | |
| Q6_K | 26.9 GB | 29.5 GB | Too big | Get file → | |
| Q6_K_L | 27.3 GB | 29.9 GB | Too big | Get file → | |
| Q8_0 | 34.8 GB | 37.5 GB | Too big | Get file → | |
| F16 | 65.5 GB (2 parts) | 68.2 GB | Too big | Get file → |
For 8 GB VRAM, use IQ2_XS (9.96 GB, ~12.6 GB memory). For 16 GB VRAM, Q4_K_M (19.85 GB, ~22.5 GB memory) is a good balance. For 24 GB VRAM, Q5_K_L (23.74 GB, ~26.4 GB memory) offers higher quality.
What GPU do you need for Qwen2.5 Coder 32B Instruct Abliterated?
These figures add the file size, an fp16 KV cache at an 8K context window (worked out from this model’s own header) and about 0.5 GB for the runtime. They are estimates, so leave a little headroom, and expect to use less context or a smaller quant if you are right at the limit.
- 4 GB VRAM: no quant fits at an 8K context.
- 6 GB VRAM: no quant fits at an 8K context.
- 8 GB VRAM: no quant fits at an 8K context.
- 12 GB VRAM: no quant fits at an 8K context.
- 16 GB VRAM: the best quant that fits is Q2_K_L (13.1 GB file, about 15.7 GB in use).
- 24 GB VRAM: the best quant that fits is Q4_K_L (20.4 GB file, about 23.1 GB in use).
- 32 GB VRAM: the best quant that fits is Q6_K_L (27.3 GB file, about 29.9 GB in use).
- 48 GB VRAM: the best quant that fits is Q8_0 (34.8 GB file, about 37.5 GB in use).
Which Qwen2.5 Coder 32B Instruct Abliterated quant should you choose?
Q4_K_M is the usual starting point for Qwen2.5 Coder 32B Instruct Abliterated: it balances file size and quality well. Here it is a 19.9 GB file.
The Q8_0 file is 34.8 GB, about 1.8 times the size of Q4_K_M. It keeps the weights closer to the original, which only matters if you have the memory to spare.
If memory is tight, the smallest file is IQ2_XS at 10.0 GB, with the quality trade-offs that come with fewer bits. Use it only when memory is very tight. Expect a clear drop in quality, which is usually worse on small models and easier to live with on large ones.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Frequently asked questions about Qwen2.5 Coder 32B Instruct Abliterated
How much VRAM does Qwen2.5 Coder 32B Instruct Abliterated need?
About 22.5 GB at Q4_K_M with an 8K context window. That is the 19.9 GB file, plus the KV cache and roughly 0.5 GB of runtime overhead. Smaller quants need less and longer context needs more.
Can I run Qwen2.5 Coder 32B Instruct Abliterated on an 8 GB GPU?
Not at an 8K context. The smallest file needs about 12.6 GB, so you would need a larger GPU or CPU offloading.
What is the file size of Qwen2.5 Coder 32B Instruct Abliterated GGUF?
It depends on the quant: IQ2_XS is 10.0 GB, IQ2_S is 10.4 GB, IQ2_M is 11.3 GB, Q2_K is 12.3 GB, Q2_K_L is 13.1 GB, IQ3_XS is 13.7 GB and 20 more.
What context length does Qwen2.5 Coder 32B Instruct Abliterated support?
The GGUF header lists a trained context length of 32,768 tokens (32K). The KV cache grows with the context you use: about 2.1 GB at 8K and 8.6 GB at 32K.
Where can I download Qwen2.5 Coder 32B Instruct Abliterated GGUF?
The files are on Hugging Face in the bartowski/Qwen2.5-Coder-32B-Instruct-abliterated-GGUF repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.
What license does Qwen2.5 Coder 32B Instruct Abliterated use?
Hugging Face lists the license as apache-2.0. Licenses can differ between the quantized files and the original model, so check the repository and the base model before commercial use.
Can I run this model on 8 GB VRAM?
Use the IQ2_XS quant, which is 9.96 GB and requires about 12.6 GB of VRAM at 8k context.
What quant gives the best quality?
Higher‑bit quants such as Q5_K_L or Q6_K provide better fidelity but need more VRAM.
Is there a vision capability?
No, the model only supports text and coding tasks.