Skip to content
Llama Builds

DeepSeek · Released May 2025

DeepSeek R1 (0528)

What it takes to run DeepSeek R1 (0528) locally: memory by quantization, the GPUs that handle it, and how fast it runs.

Updated

Parameters
671B (37B active)
Architecture
Mixture of experts
Context
128K tokens
License
MIT license
Memory at Q4_K_M
~420GB

What do you need to run DeepSeek R1 (0528)?

DeepSeek R1 (0528) needs about 420GB of VRAM at Q4_K_M with 8K context (407GB for the weights plus KV cache and overhead). Because it is a mixture-of-experts model with 37B active parameters, it generates text much faster than a dense model of the same size, and it tolerates partial CPU offload better.

See the full hardware guide for DeepSeek R1 (0528)

What to buy

GPUs for DeepSeek R1 (0528)

Unified memory

M3 Ultra 512GB

512GB unified · $9,499 MSRP

Quant
Q3_K_M
Speed (est.)
~14 tok/s
Fits, tight

Speeds are estimates at the quantization shown with 8K context. We may earn a commission when you buy through these links. Learn more.

Memory

DeepSeek R1 (0528) VRAM requirements by quantization

Lower-bit quantizations shrink the model at some cost to quality. Q4_K_M is the usual sweet spot. Totals include the KV cache for the context length shown plus runtime overhead.

Memory needed for DeepSeek R1 (0528) at each quantization level
QuantizationQualityWeightsTotal @ 8K ctxTotal @ 32K ctx
Q2_KRough252 GB260 GB262 GB
Q3_K_MUsable327 GB338 GB340 GB
Q4_K_MRecommendedDefault407 GB420 GB422 GB
Q5_K_MVery good478 GB494 GB495 GB
Q6_KNear-lossless554 GB571 GB573 GB
Q8_0Practically lossless713 GB736 GB737 GB
BF16Full precision1,342 GB1,383 GB1,385 GB

KV cache note: Multi-head latent attention caches one compressed 576-value latent per layer (512 for keys and values plus 64 for the RoPE key): 61 layers x 576 x 2 bytes = 70,272 bytes per token, about 9.2GB at 128K. Runtimes without MLA support expand this to full per-head keys and values, roughly 70 times larger.

Performance

How fast DeepSeek R1 (0528) runs

Single-user generation speed on popular GPUs that fit the model entirely in memory, at the best quantization each can hold.

  1. M5 Ultra 512GB

    Q3_K_M · 512GB

    ~21tok/s

  2. M3 Ultra 512GB

    Q3_K_M · 512GB

    ~14tok/s

Estimated (method)

Overview

About DeepSeek R1 (0528)

DeepSeek R1 was the open reasoning model that shook the industry in January 2025, and the May 2025 (0528) update closed much of the gap to the best closed models of the time. DeepSeek's V4 generation has since superseded it with a 1M-token context, a toggleable thinking mode, and far lower memory per token of context. At 671B parameters it needs about 420GB at Q4_K_M with 8K context, so local use means a 512GB Mac Studio, a large multi-GPU server, or a high-memory EPYC system running the experts from RAM. Aggressive 1-bit to 2-bit dynamic quants roughly halve that at a real quality cost.

Strengths

  • +Strong step-by-step reasoning, math, and writing
  • +MLA keeps the KV cache compact (about 69 KiB per token)
  • +MIT license

Weaknesses

  • −Needs about 420GB at Q4_K_M, impractical for most home setups
  • −Always thinks, often at great length, which is slow at local speeds
  • −Superseded by DeepSeek V4, which is stronger and cheaper to run
  • −Text only
ReasoningMathCodingWritingReasoning model

Setup

How to run DeepSeek R1 (0528)

Ollama
$ ollama run deepseek-r1:671b
llama.cpp
$ llama-server -hf unsloth/DeepSeek-R1-0528-GGUF:Q4_K_M -c 8192 -ngl 99

Weights: deepseek-ai/DeepSeek-R1-0528 · GGUF: unsloth/DeepSeek-R1-0528-GGUF

Alternatives

Frequently asked questions

How much VRAM do you need to run DeepSeek R1 (0528)?

About 420GB at Q4_K_M with 8K tokens of context: 406.8GB of weights, 0.6GB of KV cache, and 12.8GB of runtime overhead. Higher-precision quants and longer contexts need more; see the table above.

Is DeepSeek R1 (0528) free for commercial use?

DeepSeek R1 (0528) is released under the MIT license. That is a permissive license, so commercial use is allowed.

How long a context does DeepSeek R1 (0528) support?

Up to 131,072 tokens (128K). Long contexts need a lot of extra memory for the KV cache, so most local setups run 8K to 32K.

Sources: DeepSeek R1 0528 model card (Hugging Face), Unsloth DeepSeek R1 0528 GGUF files. Capability score basis: Placed just below the gpt-oss-120b anchor from its Artificial Analysis Intelligence Index v3 standing (October 2025).