DeepSeek R1 0528 needs about 406.1 GB of memory at Q4_K_M (a 404.5 GB file) with an 8K context window, which is more than a 48 GB GPU holds. This repository has 5 quants, from 289.2 GB (Q3_K_S) to 1342.3 GB (BF16). Longer context needs more: at 32K tokens the KV cache alone adds about 4.3 GB.
DeepSeek R1 0528 is a 671B-parameter DeepSeek model in GGUF format, quantized by bullerwins. Its trained context length is 160K tokens. The repository has 5 quant files, from 289.2 GB (Q3_K_S) to 1342.3 GB (BF16).
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q3_K_S | 289.2 GB (7 parts) | 290.7 GB | Too big | Get file → | |
| Q3_K_M | 319.3 GB (8 parts) | 320.9 GB | Too big | Get file → | |
| Q3_K_L | 347.5 GB (8 parts) | 349.1 GB | Too big | Get file → | |
| Q4_K_M | 404.5 GB (10 parts) | 406.1 GB | Too big | Get file → | |
| BF16 | 1342.3 GB (35 parts) | 1343.9 GB | Too big | Get file → |
What GPU do you need for DeepSeek R1 0528?
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 R1 0528 quant should you choose?
Q4_K_M is the usual starting point for DeepSeek R1 0528: it balances file size and quality well. Here it is a 404.5 GB file.
If memory is tight, the smallest file is Q3_K_S at 289.2 GB, with the quality trade-offs that come with fewer bits. A reasonable choice when a 4-bit file will not fit, mostly on larger models. Quality loss is noticeable but often acceptable.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about DeepSeek R1 0528
How much VRAM does DeepSeek R1 0528 need?
About 406.1 GB at Q4_K_M with an 8K context window. That is the 404.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 R1 0528 on an 8 GB GPU?
Not at an 8K context. The smallest file needs about 290.7 GB, so you would need a larger GPU or CPU offloading.
What is the file size of DeepSeek R1 0528 GGUF?
It depends on the quant: Q3_K_S is 289.2 GB, Q3_K_M is 319.3 GB, Q3_K_L is 347.5 GB, Q4_K_M is 404.5 GB, BF16 is 1342.3 GB.
What context length does DeepSeek R1 0528 support?
The GGUF header lists a trained context length of 163,840 tokens (160K). The KV cache grows with the context you use: about 1.1 GB at 8K and 4.3 GB at 32K.
Where can I download DeepSeek R1 0528 GGUF?
The files are on Hugging Face in the bullerwins/DeepSeek-R1-0528-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 R1 0528 use?
Hugging Face lists the license as mit. Licenses can differ between the quantized files and the original model, so check the repository and the base model before commercial use.