Can I run DeepSeek R1 32B?
DeepSeek R1 32B by DeepSeek needs around 32 GB of RAM at the recommended 4-bit quantization (19.9 GB download). Your hardware is checked below β instantly, nothing leaves your browser. Expect roughly ~18 tok/s on a Apple M-series Max.
Reading your hardware signalsβ¦
Real-world notes
DeepSeek R1 32B is a reasoning model for people who want chain-of-thought work done locally rather than quick chat. At 32.8B parameters it is not a casual download: a 4-bit quant is about 19.9 GB, and you want at least 32 GB of RAM to run it comfortably. It will not fit on a 12 GB card like an RTX 3060, so realistically you are looking at a 24 GB GPU, a high-memory Apple Silicon Mac, or a workstation with plenty of system memory. If you have that hardware, it is one of the better open-weight reasoners you can self-host.
In daily use it thinks out loud before answering, which is the point but also the cost: every reply spends tokens reasoning, so raw speed matters. On an RTX 4090 you can expect roughly 43 tokens per second at 4-bit, fast enough that the visible reasoning stream stays readable; on an Apple M Max it drops to around 18 tok/s, and on a CPU with DDR5 it crawls at about 3 tok/s, which is workable for batch jobs but not interactive. The 128K context is generous, but filling it is expensive here: at the full window total memory climbs to about 51.6 GB, so plan for a fat machine or keep context modest.
Against Qwen 3 32B, which is the same size and also handles reasoning, DeepSeek R1 32B tends to lean harder into explicit step-by-step deliberation while Qwen 3 32B generally feels more balanced for mixed chat-plus-reasoning work. R1 32B's standout trait is that visible reasoning trace: for math, logic, and multi-step problems where you want to see and check the model's working, it is hard to beat at this size. It ships under the MIT license, so you can use it commercially and in production without the provider-specific terms that come with some open-weight families.
Specifications
Size by quantization
| Quantization | Bits/weight | Download | Min RAM | Quality |
|---|---|---|---|---|
| Q2_K | 3.35 | 13.7 GB | 24 GB | Noticeable loss |
| Q4_K_MRecommended | 4.85 | 19.9 GB | 32 GB | Recommended |
| Q5_K_M | 5.65 | 23.2 GB | 32 GB | High |
| Q8_0 | 8.5 | 34.8 GB | 48 GB | Near-original |
| F16 | 16 | 65.6 GB | 96 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.0 GB | ~20.9 GB |
| 8K tokens | ~2.0 GB | ~21.9 GB |
| 32K tokens | ~7.9 GB | ~27.8 GB |
| 128K tokens | ~31.7 GB | ~51.6 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 | ~43 tok/s |
| Apple M-series (base) | 100 GB/s | ~4 tok/s |
| Apple M-series Pro | 270 GB/s | ~12 tok/s |
| Apple M-series Max | 410 GB/s | ~18 tok/s |
| CPU only (dual-channel DDR5) | 60 GB/s | ~3 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:32bSources & downloads