← All modelsMODEL CHECK

Can I run DeepSeek R1 8B?

DeepSeek R1 8B by DeepSeek needs around 8 GB of RAM at the recommended 4-bit quantization (4.9 GB download). Your hardware is checked below — instantly, nothing leaves your browser. Expect roughly ~63 tok/s on a NVIDIA RTX 3060 12GB.

Reading your hardware signals…

Real-world notes

DeepSeek R1 8B is a reasoning-first model, not a general chat workhorse, and that framing matters before you download it. It is a dense 8B model, so at 4-bit it lands around 4.9 GB and fits an 8 GB GPU with room to spare; the listed 8 GB minimum RAM makes it viable on a modest desktop or any Apple Silicon Mac with unified memory. The MIT license is the easy part: you can use it commercially, in production, with no provider strings attached. Reach for it when you want a model that thinks through a problem rather than one that just answers fast.

In daily use it feels quick for its size on real hardware. An RTX 3060 12GB pushes about 63 tok/s, an M-series Max around 72 tok/s, and a 4090 roughly 177 tok/s, so streaming never bottlenecks. CPU on DDR5 drops to about 11 tok/s, fine for the occasional query but not a working loop. The real caveat is the chain-of-thought habit: R1 reasons out loud, so it eats context faster than a plain chat model. The 128K window is genuine, but filling it pushes total memory to roughly 21.7 GB, so keep working context modest unless you have headroom.

Positioned honestly, this is a distilled reasoning model rather than a frontier brain in a small box. Against Llama 3.1 8B it generally trades broad conversational polish and tooling maturity for stronger step-by-step reasoning, while the smaller DeepSeek R1 7B and 1.5B exist if you need to go lighter at some cost to depth. Its standout trait is that visible reasoning trace, which is genuinely useful for math, logic, and debugging where you want to see the work. If you mostly want quick casual chat, a chat-tuned 8B is the better default; if you want a local model that reasons, R1 8B earns its place.

Specifications

Parameters8B
Context window128K tokens
ProviderDeepSeek
LicenseMIT
Released2025-01
Best forReasoning

Size by quantization

QuantizationBits/weightDownloadMin RAMQuality
Q2_K3.353.4 GB6 GBNoticeable loss
Q4_K_MRecommended4.854.9 GB8 GBRecommended
Q5_K_M5.655.7 GB12 GBHigh
Q8_08.58.5 GB16 GBNear-original
F161616.0 GB24 GBOriginal

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

ContextKV cache (est.)Total memory (Q4)
4K tokens~0.5 GB~5.4 GB
8K tokens~1.0 GB~5.9 GB
32K tokens~4.2 GB~9.1 GB
128K tokens~16.8 GB~21.7 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

HardwareBandwidth~Speed
NVIDIA RTX 3060 12GB360 GB/s~63 tok/s
NVIDIA RTX 4090 24GB1008 GB/s~177 tok/s
Apple M-series (base)100 GB/s~18 tok/s
Apple M-series Pro270 GB/s~47 tok/s
Apple M-series Max410 GB/s~72 tok/s
CPU only (dual-channel DDR5)60 GB/s~11 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:8b

Frequently asked questions