DeepSeek-Coder-V2-Lite-Base needs about 13.1 GB of memory at Q4_K_M (a 10.4 GB file) with an 8K context window, so it fits on a 16 GB GPU. This repository has 22 quants, from 6.0 GB (IQ2_XS) to 62.8 GB (F32). Longer context needs more: at 32K tokens the KV cache alone adds about 9.1 GB.
DeepSeek-Coder-V2-Lite-Base – 15.7B coding model in GGUF format
DeepSeek-Coder-V2-Lite-Base is a 15.7B parameter coding model built on the deepseek2 architecture. It is quantized into multiple GGUF files for flexible deployment. The model supports a context length of 163840 tokens.
Good at
- Coding tasks
- Code generation
- Programming assistance
Limits
- No vision support
- License type is other
- No explicit language support listed
Best for
- Developers needing lightweight code generation
- Embedded coding assistants
- Rapid prototyping
Who it’s for. This model is suitable for developers and researchers who require a large‑parameter coding model that can be run locally with llama.cpp. It is ideal for environments where GPU memory is limited but a high‑quality code assistant is desired.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| IQ2_XS | 6.0 GB | 8.7 GB | Too big | Get file → | |
| IQ2_S | 6.0 GB | 8.8 GB | Too big | Get file → | |
| IQ2_M | 6.3 GB | 9.1 GB | Too big | Get file → | |
| Q2_K | 6.4 GB | 9.2 GB | Too big | Get file → | |
| IQ3_XXS | 7.0 GB | 9.7 GB | Too big | Get file → | |
| IQ3_XS | 7.1 GB | 9.9 GB | Too big | Get file → | |
| Q3_K_S | 7.5 GB | 10.3 GB | Too big | Get file → | |
| IQ3_M | 7.6 GB | 10.3 GB | Too big | Get file → | |
| Q3_K_M | 8.1 GB | 10.9 GB | Too big | Get file → | |
| Q3_K_L | 8.5 GB | 11.2 GB | Too big | Get file → | |
| IQ4_XS | 8.6 GB | 11.3 GB | Too big | Get file → | |
| Q4_K_S | 9.5 GB | 12.3 GB | Too big | Get file → | |
| Q4_K_M | 10.4 GB | 13.1 GB | Too big | Get file → | |
| Q4_K_L | 10.9 GB | 13.7 GB | Too big | Get file → | |
| Q5_K_S | 11.1 GB | 13.9 GB | Too big | Get file → | |
| Q5_K_M | 11.9 GB | 14.6 GB | Too big | Get file → | |
| Q5_K_L | 12.4 GB | 15.1 GB | Too big | Get file → | |
| Q6_K | 14.1 GB | 16.8 GB | Too big | Get file → | |
| Q6_K_L | 14.6 GB | 17.3 GB | Too big | Get file → | |
| Q8_0 | 16.7 GB | 19.5 GB | Too big | Get file → | |
| Q8_0 | 17.1 GB | 19.9 GB | Too big | Get file → | |
| F32 | 62.8 GB (2 parts) | 65.6 GB | Too big | Get file → |
For 8‑GB VRAM, use IQ2_XS or IQ2_S (file size 5.97‑6.01 GB, estimated memory 8.7‑8.8 GB). For 12‑GB VRAM, Q4_K_S (9.53 GB, 12.3 GB). For 16‑GB VRAM, Q5_K_M (11.85 GB, 14.6 GB). Larger models require more memory.
What GPU do you need for DeepSeek-Coder-V2-Lite-Base?
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: the best quant that fits is IQ4_XS (8.6 GB file, about 11.3 GB in use).
- 16 GB VRAM: the best quant that fits is Q5_K_L (12.4 GB file, about 15.1 GB in use).
- 24 GB VRAM: the best quant that fits is Q8_0 (17.1 GB file, about 19.9 GB in use).
- 32 GB VRAM: the best quant that fits is Q8_0 (17.1 GB file, about 19.9 GB in use).
- 48 GB VRAM: the best quant that fits is Q8_0 (17.1 GB file, about 19.9 GB in use).
Which DeepSeek-Coder-V2-Lite-Base quant should you choose?
Q4_K_M is the usual starting point for DeepSeek-Coder-V2-Lite-Base: it balances file size and quality well. Here it is a 10.4 GB file.
The Q8_0 file is 16.7 GB, about 1.6 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 6.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 DeepSeek-Coder-V2-Lite-Base
How much VRAM does DeepSeek-Coder-V2-Lite-Base need?
About 13.1 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-Base on an 8 GB GPU?
Not at an 8K context. The smallest file needs about 8.7 GB, so you would need a larger GPU or CPU offloading.
What is the file size of DeepSeek-Coder-V2-Lite-Base GGUF?
It depends on the quant: IQ2_XS is 6.0 GB, IQ2_S is 6.0 GB, IQ2_M is 6.3 GB, Q2_K is 6.4 GB, IQ3_XXS is 7.0 GB, IQ3_XS is 7.1 GB and 16 more.
What context length does DeepSeek-Coder-V2-Lite-Base support?
The GGUF header lists a trained context length of 163,840 tokens (160K). The KV cache grows with the context you use: about 2.3 GB at 8K and 9.1 GB at 32K.
Where can I download DeepSeek-Coder-V2-Lite-Base GGUF?
The files are on Hugging Face in the bartowski/DeepSeek-Coder-V2-Lite-Base-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 DeepSeek-Coder-V2-Lite-Base use?
Hugging Face lists the license as other. 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 DeepSeek-Coder-V2-Lite-Base on 8 GB VRAM?
Yes, using the IQ2_XS or IQ2_S quantizations which fit within 8‑GB VRAM with estimated memory usage of 8.7‑8.8 GB.
What is the context length of this model?
The model supports a context length of 163840 tokens.
Does this model support vision tasks?
No, the model does not support vision capabilities.