Hardware for Running DeepSeek R1 671B Locally
The full DeepSeek R1 — a 671B-total MoE that needs hundreds of gigabytes even at Q4, far beyond any single unified-memory box. Run a DeepSeek-R1 distill instead.
Quick answer
DeepSeek R1 671B (671B params) needs about 403 GB of memory even at Q4 — more than any single unified-memory box we track can allocate. You can't run it locally on one box; run a smaller distill or more aggressively quantized model instead — see the full model list. These are estimates including runtime overhead.
Estimated Memory Requirements
Estimated from the 671B parameter count (quantization × bytes/param + ~20% runtime overhead), not measured. MoE models load by total parameters.
| Precision | Est. Memory | Notes |
|---|---|---|
| FP16 (full precision) | ~1611 GB | Best quality, highest memory usage |
| Q8 (8-bit quantized) | ~806 GB | Near-lossless quality, good balance |
| Q4 (4-bit quantized) | ~403 GB | Smallest footprint, slight quality loss |
No single box runs this locally
At 403 GB (estimated, Q4) DeepSeek R1 671B exceeds the memory every unified-memory box in our catalog can allocate. Rather than list hardware that can't run it, we point you to models that can — browse the full model list for a distill or smaller sibling, or size any parameter count against the catalog with the VRAM calculator.
Disclosure: Some links on this page are affiliate links. We may earn a commission if you make a purchase — at no extra cost to you. This helps support our independent reviews.