DeepSeek Coder V2 Instruct needs about 183.2 GB of memory at Q4_K_M (a 142.5 GB file) with an 8K context window, which is more than a 48 GB GPU holds. This repository has 13 quants, from 85.9 GB (Q2_K) to 471.6 GB (F16). Longer context needs more: at 32K tokens the KV cache alone adds about 161.1 GB.
DeepSeek Coder V2 Instruct – 236B MoE code model
DeepSeek Coder V2 Instruct is a 236B parameter Mixture‑of‑Experts model focused on coding tasks. It supports 128K context length and 338 programming languages. The model is available in multiple GGUF quantizations for local inference.
Good at
- Code generation
- Code completion
- Mathematical reasoning
Limits
- No vision support
- Requires 8K context for memory estimates
- License is other
Best for
- Local code assistants
- Educational coding tools
- Code review automation
Who it’s for. Developers and researchers needing a large‑scale code model that can run locally with quantized GGUF files. The model is suitable for teams that prefer open‑source solutions and can manage the memory requirements of a 236B MoE architecture.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q2_K | 85.9 GB (3 parts) | 126.7 GB | Too big | Get file → | |
| Q3_K_S | 101.7 GB (4 parts) | 142.4 GB | Too big | Get file → | |
| Q3_K_M | 112.7 GB (4 parts) | 153.4 GB | Too big | Get file → | |
| Q3_K_L | 122.4 GB (5 parts) | 163.1 GB | Too big | Get file → | |
| Q4_0 | 132.9 GB (5 parts) | 173.7 GB | Too big | Get file → | |
| Q4_K_S | 133.9 GB (5 parts) | 174.6 GB | Too big | Get file → | |
| Q4_K_M | 142.5 GB (5 parts) | 183.2 GB | Too big | Get file → | |
| Q5_0 | 162.3 GB (6 parts) | 203.1 GB | Too big | Get file → | |
| Q5_K_S | 162.3 GB (6 parts) | 203.1 GB | Too big | Get file → | |
| Q5_K_M | 167.2 GB (6 parts) | 208.0 GB | Too big | Get file → | |
| Q6_K | 193.5 GB (7 parts) | 234.3 GB | Too big | Get file → | |
| Q8_0 | 250.6 GB (9 parts) | 291.4 GB | Too big | Get file → | |
| F16 | 471.6 GB (17 parts) | 512.4 GB | Too big | Get file → |
For 8‑GB VRAM use Q2_K (85.95 GB file, 126.7 GB memory at 8K). For 16‑GB VRAM use Q4_K_M (142.45 GB file, 183.2 GB memory). For 24‑GB VRAM use Q5_K_M (167.22 GB file, 208 GB memory). Estimates are approximate.
What GPU do you need for DeepSeek Coder V2 Instruct?
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: no quant fits at an 8K context.
- 24 GB VRAM: no quant fits at an 8K context.
- 32 GB VRAM: no quant fits at an 8K context.
- 48 GB VRAM: no quant fits at an 8K context.
Which DeepSeek Coder V2 Instruct quant should you choose?
Q4_K_M is the usual starting point for DeepSeek Coder V2 Instruct: it balances file size and quality well. Here it is a 142.5 GB file.
The Q8_0 file is 250.6 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 Q2_K at 85.9 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
Source
Frequently asked questions about DeepSeek Coder V2 Instruct
How much VRAM does DeepSeek Coder V2 Instruct need?
About 183.2 GB at Q4_K_M with an 8K context window. That is the 142.5 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 Instruct on an 8 GB GPU?
Not at an 8K context. The smallest file needs about 126.7 GB, so you would need a larger GPU or CPU offloading.
What is the file size of DeepSeek Coder V2 Instruct GGUF?
It depends on the quant: Q2_K is 85.9 GB, Q3_K_S is 101.7 GB, Q3_K_M is 112.7 GB, Q3_K_L is 122.4 GB, Q4_0 is 132.9 GB, Q4_K_S is 133.9 GB and 7 more.
What context length does DeepSeek Coder V2 Instruct support?
The GGUF header lists a trained context length of 163,840 tokens (160K). The KV cache grows with the context you use: about 40.3 GB at 8K and 161.1 GB at 32K.
Where can I download DeepSeek Coder V2 Instruct GGUF?
The files are on Hugging Face in the second-state/DeepSeek-Coder-V2-Instruct-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 Instruct 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 Instruct on 8 GB VRAM?
Use the Q2_K quantized file; it requires about 126.7 GB memory at 8K context, which is beyond 8 GB VRAM, so it is not feasible.
Does the model support image inputs?
No, the model has no vision capabilities.
What is the maximum context length?
The model supports up to 128000 tokens of context.