Can I run DeepSeek R1 70B?
DeepSeek R1 70B by DeepSeek needs around 64 GB of RAM at the recommended 4-bit quantization (42.8 GB download). Your hardware is checked below β instantly, nothing leaves your browser. Expect roughly ~8 tok/s on a Apple M-series Max.
Reading your hardware signalsβ¦
Real-world notes
DeepSeek R1 70B is the model you reach for when you want chain-of-thought reasoning running entirely on your own hardware, not a quick chat helper. At 4-bit it weighs about 42.8 GB and needs around 64 GB of RAM minimum, which rules out a single consumer GPU outright: it will not fit on an RTX 3060 12GB or even an RTX 4090 24GB. The realistic home for it is a Mac with plenty of unified memory or a workstation with 64 GB or more, where the full set of weights can actually stay resident. This is a serious commitment, not a casual download.
In daily use the honest headline is that it's slow. On an Apple M-Max you're looking at roughly 8 tokens per second, and on a CPU with DDR5 it drops to about 1 token per second, so replies arrive at reading pace at best and crawl at worst. Because R1 thinks out loud before answering, a lot of those tokens go into visible reasoning, so a single response can take a while. The 128K context is there, but filling it pushes total memory to about 87.5 GB, well past the 64 GB floor, so keep working context modest unless you have headroom to spare.
Against its own family the trade is straightforward: DeepSeek R1 7B or the tiny 1.5B run far faster and fit on modest hardware, but this 70B generally holds up better on harder multi-step reasoning where the smaller distills tend to lose the thread. Compared to Llama 3.1 70B, which is tuned for chat, R1 70B's standout trait is that explicit reasoning style, better suited to math and logic problems than open conversation. The MIT license is the easy part here: you can use it commercially and in production without provider-specific strings attached. Just budget for the memory and the wait.
Specifications
Size by quantization
| Quantization | Bits/weight | Download | Min RAM | Quality |
|---|---|---|---|---|
| Q2_K | 3.35 | 29.6 GB | 48 GB | Noticeable loss |
| Q4_K_MRecommended | 4.85 | 42.8 GB | 64 GB | Recommended |
| Q5_K_M | 5.65 | 49.9 GB | 64 GB | High |
| Q8_0 | 8.5 | 75.0 GB | 96 GB | Near-original |
| F16 | 16 | 141.2 GB | 192 GB | Original |
Sizes are estimates from parameter count Γ bits per weight; real GGUF builds vary slightly. Β· Data updated: 2026-06-11 Β· How we calculate these numbers β
Memory needed by context length
| Context | KV cache (est.) | Total memory (Q4) |
|---|---|---|
| 4K tokens | ~1.4 GB | ~44.2 GB |
| 8K tokens | ~2.8 GB | ~45.6 GB |
| 32K tokens | ~11.2 GB | ~54.0 GB |
| 128K tokens | ~44.7 GB | ~87.5 GB |
The KV cache grows with context length β a model that fits at 4K can run out of memory at 32K. Estimates assume an FP16 cache with grouped-query attention; actual usage varies by runtime.
Estimated speed by hardware
| Hardware | Bandwidth | ~Speed |
|---|---|---|
| NVIDIA RTX 3060 12GB | 360 GB/s | Won't fit in VRAM |
| NVIDIA RTX 4090 24GB | 1008 GB/s | Won't fit in VRAM |
| Apple M-series (base) | 100 GB/s | ~2 tok/s |
| Apple M-series Pro | 270 GB/s | ~5 tok/s |
| Apple M-series Max | 410 GB/s | ~8 tok/s |
| CPU only (dual-channel DDR5) | 60 GB/s | ~1 tok/s |
Token generation is memory-bandwidth bound: tok/s β bandwidth Γ 0.85 Γ· model size at Q4. Real-world numbers vary by runtime and context length.
Run it locally
The easiest path is Ollama β one command and you're chatting:
ollama run deepseek-r1:70bSources & downloads