Deepseek Coder 33b Secure 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 24 quants, from 0.0 GB to 27.4 GB (Q6_K).
Deepseek Coder 33b Secure – a 33.3B llama model fine‑tuned for coding
Deepseek Coder 33b Secure is a 33.3B parameter llama model fine‑tuned for coding tasks. It supports a 16384 token context window and is released under the apache‑2.0 license. The model is available in multiple GGUF quantizations.
Good at
- Large‑scale code generation
- Complex programming queries
- Multi‑language coding support
Limits
- No vision or audio support
- Requires high VRAM for larger quants
- No built‑in safety filters
Best for
- Developers needing code completion
- Automated code review tools
- Educational coding assistants
Who it’s for. This model is suited for developers, researchers, and educators who need a powerful code generation engine. It is ideal for environments where a large context window and high‑quality code output are required.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| — | 0.0 GB | 2.6 GB | Fits | Get file → | |
| IQ1_S | 7.2 GB | 9.7 GB | Too big | Get file → | |
| IQ1_M | 7.8 GB | 10.4 GB | Too big | Get file → | |
| IQ2_XXS | 8.9 GB | 11.5 GB | Too big | Get file → | |
| IQ2_XS | 9.9 GB | 12.5 GB | Too big | Get file → | |
| IQ2_S | 10.5 GB | 13.1 GB | Too big | Get file → | |
| IQ2_M | 11.4 GB | 13.9 GB | Too big | Get file → | |
| Q2_K_S | 11.4 GB | 14.0 GB | Too big | Get file → | |
| Q2_K | 12.4 GB | 14.9 GB | Too big | Get file → | |
| IQ3_XXS | 12.9 GB | 15.4 GB | Too big | Get file → | |
| IQ3_XS | 13.7 GB | 16.3 GB | Too big | Get file → | |
| Q3_K_S | 14.4 GB | 17.0 GB | Too big | Get file → | |
| IQ3_S | 14.5 GB | 17.1 GB | Too big | Get file → | |
| IQ3_M | 15.0 GB | 17.6 GB | Too big | Get file → | |
| Q3_K_M | 16.1 GB | 18.7 GB | Too big | Get file → | |
| Q3_K_L | 17.6 GB | 20.1 GB | Too big | Get file → | |
| IQ4_XS | 17.9 GB | 20.4 GB | Too big | Get file → | |
| Q4_0 | 18.9 GB | 21.5 GB | Too big | Get file → | |
| Q4_K_S | 18.9 GB | 21.5 GB | Too big | Get file → | |
| Q4_K_M | 19.9 GB | 22.5 GB | Too big | Get file → | |
| Q4_1 | 20.9 GB | 23.5 GB | Too big | Get file → | |
| Q5_K_S | 23.0 GB | 25.5 GB | Too big | Get file → | |
| Q5_K_M | 23.5 GB | 26.1 GB | Too big | Get file → | |
| Q6_K | 27.4 GB | 29.9 GB | Too big | Get file → |
For 8 GB VRAM, use IQ1_S (7.16 GB file, 9.7 GB memory). For 12 GB VRAM, IQ2_XS (9.91 GB file, 12.5 GB memory) or Q2_K (12.36 GB file, 14.9 GB memory). For 16 GB VRAM, Q3_K_M (16.09 GB file, 18.7 GB memory) or Q4_K_M (19.94 GB file, 22.5 GB memory).
What GPU do you need for Deepseek Coder 33b Secure?
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 2.6 GB in use).
- 6 GB VRAM: the best quant that fits is the main file (0.0 GB file, about 2.6 GB in use).
- 8 GB VRAM: the best quant that fits is the main file (0.0 GB file, about 2.6 GB in use).
- 12 GB VRAM: the best quant that fits is IQ2_XXS (8.9 GB file, about 11.5 GB in use).
- 16 GB VRAM: the best quant that fits is IQ3_XXS (12.9 GB file, about 15.4 GB in use).
- 24 GB VRAM: the best quant that fits is Q4_1 (20.9 GB file, about 23.5 GB in use).
- 32 GB VRAM: the best quant that fits is Q6_K (27.4 GB file, about 29.9 GB in use).
Which Deepseek Coder 33b Secure quant should you choose?
Q4_K_M is the usual starting point for Deepseek Coder 33b Secure: it balances file size and quality well. Here it is a 19.9 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
Source
Frequently asked questions about Deepseek Coder 33b Secure
How much VRAM does Deepseek Coder 33b Secure 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 Deepseek Coder 33b Secure on an 8 GB GPU?
Yes, with the smaller files: the 0.0 GB file needs about 2.6 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of Deepseek Coder 33b Secure GGUF?
It depends on the quant: file is 0.0 GB, IQ1_S is 7.2 GB, IQ1_M is 7.8 GB, IQ2_XXS is 8.9 GB, IQ2_XS is 9.9 GB, IQ2_S is 10.5 GB and 18 more.
What context length does Deepseek Coder 33b Secure support?
The GGUF header lists a trained context length of 16,384 tokens (16K). The KV cache grows with the context you use: about 2.1 GB at 8K and 4.2 GB at 16K.
Where can I download Deepseek Coder 33b Secure GGUF?
The files are on Hugging Face in the mradermacher/deepseek-coder-33b-secure-i1-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 33b Secure 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 Deepseek Coder 33b Secure on 8 GB VRAM?
Use the IQ1_S quant, which requires 9.7 GB of VRAM at 8k context. It may be close to the limit, so consider reducing context or using a lower quant.
Does the model support image inputs?
No, the model has no vision capability and only processes text.
What license applies to this model?
The model is released under the apache‑2.0 license.