DeepSeek Coder V2 Lite Instruct Abliterated needs about 11.3 GB of memory at Q4_K_M (a 10.4 GB file) with an 8K context window, so it fits on a 12 GB GPU. This repository has 25 quants, from 0.0 GB to 14.1 GB (Q6_K). Longer context needs more: at 32K tokens the KV cache alone adds about 1.9 GB.
DeepSeek Coder V2 Lite Instruct Abliterated – 17B coding model in GGUF format
DeepSeek Coder V2 Lite Instruct Abliterated is a 17 billion‑parameter model optimized for code generation. It supports a 163 840‑token context window and is available in multiple quantized GGUF variants. The model is tailored for instruction‑driven coding tasks.
Good at
- Code completion
- Bug detection
- API usage examples
Limits
- Large context requires significant VRAM
- No vision or multimodal support
- License not specified
Best for
- Developers writing scripts
- Debugging code snippets
- Generating API documentation
Who it’s for. Engineers and developers who need a lightweight code assistant. The model is suitable for local deployment on machines with moderate GPU memory.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| — | 0.0 GB | 1.0 GB | Fits | Get file → | |
| IQ1_S | 5.0 GB | 6.0 GB | Fits | Get file → | |
| IQ1_M | 5.2 GB | 6.2 GB | Fits | Get file → | |
| IQ2_XXS | 5.6 GB | 6.6 GB | Fits | Get file → | |
| IQ2_XS | 6.0 GB | 7.0 GB | Fits | Get file → | |
| IQ2_S | 6.0 GB | 7.0 GB | Fits | Get file → | |
| IQ2_M | 6.3 GB | 7.3 GB | Tight | Get file → | |
| Q2_K | 6.4 GB | 7.4 GB | Tight | Get file → | |
| Q2_K_S | 6.5 GB | 7.4 GB | Tight | Get file → | |
| IQ3_XXS | 7.0 GB | 8.0 GB | Tight | Get file → | |
| IQ3_XS | 7.1 GB | 8.1 GB | Too big | Get file → | |
| IQ3_S | 7.5 GB | 8.5 GB | Too big | Get file → | |
| Q3_K_S | 7.5 GB | 8.5 GB | Too big | Get file → | |
| IQ3_M | 7.6 GB | 8.5 GB | Too big | Get file → | |
| Q3_K_M | 8.1 GB | 9.1 GB | Too big | Get file → | |
| Q3_K_L | 8.5 GB | 9.4 GB | Too big | Get file → | |
| IQ4_XS | 8.6 GB | 9.6 GB | Too big | Get file → | |
| IQ4_NL | 8.9 GB | 9.9 GB | Too big | Get file → | |
| Q4_0 | 8.9 GB | 9.9 GB | Too big | Get file → | |
| Q4_K_S | 9.5 GB | 10.5 GB | Too big | Get file → | |
| Q4_1 | 9.9 GB | 10.9 GB | Too big | Get file → | |
| Q4_K_M | 10.4 GB | 11.3 GB | Too big | Get file → | |
| Q5_K_S | 11.1 GB | 12.1 GB | Too big | Get file → | |
| Q5_K_M | 11.9 GB | 12.8 GB | Too big | Get file → | |
| Q6_K | 14.1 GB | 15.1 GB | Too big | Get file → |
For 8 GB VRAM, use IQ1_S (6 GB memory) or IQ1_M (6.2 GB). With 12 GB VRAM, IQ2_S (7 GB) or Q2_K (7.4 GB) are suitable. For 16 GB VRAM, IQ3_S (8.5 GB) or Q3_K_M (9.1 GB) provide better quality.
What GPU do you need for DeepSeek Coder V2 Lite 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: the best quant that fits is the main file (0.0 GB file, about 1.0 GB in use).
- 6 GB VRAM: the best quant that fits is IQ1_S (5.0 GB file, about 6.0 GB in use).
- 8 GB VRAM: the best quant that fits is IQ3_XXS (7.0 GB file, about 8.0 GB in use).
- 12 GB VRAM: the best quant that fits is Q4_K_M (10.4 GB file, about 11.3 GB in use).
- 16 GB VRAM: the best quant that fits is Q6_K (14.1 GB file, about 15.1 GB in use).
Which DeepSeek Coder V2 Lite Instruct Abliterated quant should you choose?
Q4_K_M is the usual starting point for DeepSeek Coder V2 Lite Instruct Abliterated: it balances file size and quality well. Here it is a 10.4 GB file.
If memory is tight, the smallest file is the first one in the table at 0.0 GB, with the quality trade-offs that come with fewer bits.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Frequently asked questions about DeepSeek Coder V2 Lite Instruct Abliterated
How much VRAM does DeepSeek Coder V2 Lite Instruct Abliterated need?
About 11.3 GB at Q4_K_M with an 8K context window. That is the 10.4 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 DeepSeek Coder V2 Lite Instruct Abliterated on an 8 GB GPU?
Yes, with IQ3_XXS: the 7.0 GB file needs about 8.0 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of DeepSeek Coder V2 Lite Instruct Abliterated GGUF?
It depends on the quant: file is 0.0 GB, IQ1_S is 5.0 GB, IQ1_M is 5.2 GB, IQ2_XXS is 5.6 GB, IQ2_XS is 6.0 GB, IQ2_S is 6.0 GB and 19 more.
What context length does DeepSeek Coder V2 Lite Instruct Abliterated support?
The GGUF header lists a trained context length of 163,840 tokens (160K). The KV cache grows with the context you use: about 0.5 GB at 8K and 1.9 GB at 32K.
Where can I download DeepSeek Coder V2 Lite Instruct Abliterated GGUF?
The files are on Hugging Face in the mradermacher/DeepSeek-Coder-V2-Lite-Instruct-abliterated-i1-GGUF repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.
Can I run this model on 8 GB VRAM?
Yes, use IQ1_S or IQ1_M quantizations, which require about 6 GB of VRAM at 8 k context.
Does this model support image inputs?
No, the model has no vision or multimodal capabilities.
What is the maximum context length?
The model supports up to 163,840 tokens in its context window.