Can I run DeepSeek R1 1.5B?
DeepSeek R1 1.5B by DeepSeek needs around 3 GB of RAM at the recommended 4-bit quantization (1.1 GB download). Your hardware is checked below — instantly, nothing leaves your browser. Expect roughly ~280 tok/s on a NVIDIA RTX 3060 12GB.
Reading your hardware signals…
Real-world notes
DeepSeek R1 1.5B is a distilled reasoning model, and that word matters: it is tuned to think out loud through a problem rather than chat breezily. At 1.8B parameters it is tiny. A 4-bit quant lands around 1.1 GB, and even the 8-bit build is only 1.9 GB, so it fits in well under 3 GB of minimum RAM. That means it runs anywhere: an old laptop, a Raspberry Pi class board, a phone, or as a background helper that barely touches your GPU. Pull it with ollama run deepseek-r1:1.5b and you are going in seconds.
In daily use it is genuinely quick. On an RTX 3060 you can expect around 280 tokens per second, a 4090 pushes near 785, and an Apple M-series Max sits around 319, so the visible reply is gated more by how long it reasons than by raw speed. Even pure CPU on DDR5 manages roughly 47 tokens per second. The 128K context is the catch: this model burns tokens on its own chain-of-thought, and filling that window pushes total memory to about 9.7 GB, well past the idle footprint. Keep working context modest and let it think in short bursts.
Honestly, at this size the reasoning is hit or miss on anything multi-step; its larger siblings DeepSeek R1 7B and R1 8B are far more reliable when the answer actually matters, and Qwen 3 1.7B is the better pick if you mainly want plain chat rather than visible reasoning. Where the 1.5B wins is reach: it is the smallest way to see R1-style thinking traces run locally, and it does it on hardware nothing else will. The MIT license is the bonus, fully open and free to use commercially with no strings.
Specifications
Size by quantization
| Quantization | Bits/weight | Download | Min RAM | Quality |
|---|---|---|---|---|
| Q2_K | 3.35 | 0.8 GB | 3 GB | Noticeable loss |
| Q4_K_MRecommended | 4.85 | 1.1 GB | 3 GB | Recommended |
| Q5_K_M | 5.65 | 1.3 GB | 4 GB | High |
| Q8_0 | 8.5 | 1.9 GB | 4 GB | Near-original |
| F16 | 16 | 3.6 GB | 6 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 | ~0.3 GB | ~1.4 GB |
| 8K tokens | ~0.5 GB | ~1.6 GB |
| 32K tokens | ~2.1 GB | ~3.2 GB |
| 128K tokens | ~8.6 GB | ~9.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
| Hardware | Bandwidth | ~Speed |
|---|---|---|
| NVIDIA RTX 3060 12GB | 360 GB/s | ~280 tok/s |
| NVIDIA RTX 4090 24GB | 1008 GB/s | ~785 tok/s |
| Apple M-series (base) | 100 GB/s | ~78 tok/s |
| Apple M-series Pro | 270 GB/s | ~210 tok/s |
| Apple M-series Max | 410 GB/s | ~319 tok/s |
| CPU only (dual-channel DDR5) | 60 GB/s | ~47 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:1.5bSources & downloads