Start with 8B on a 16 GB system. Treat 14B and 32B as larger-memory candidates. Check the exact artifact, context and GPU path before downloading.
Use the explanations below when you want to know why each step matters.
The direct answer
DeepSeek R1 is a family name, not a single laptop download. The smaller distilled models and the full 671B model have very different memory needs. Do not choose the full model because its name matches a smaller-model tutorial.
For a first planning check, use 8B with 16 GB RAM, 14B with 24–32 GB RAM, and 32B with 48–64 GB RAM. These are conservative starting configurations for one user and a short context, not minimum requirements or measured speed claims. A GPU can change where memory is used; enter the exact card in the calculator.
Smallest of these three choices.
Needs extra room for context and runtime.
A larger workstation candidate.
Do not confuse 8B revisions
Ollama identifies its updated 8B version as DeepSeek-R1-0528-Qwen3-8B. Older articles may refer to a different 8B distilled release. Record the exact tag and model information when comparing results. A family name alone is not enough to reproduce a benchmark.
The 14B and 32B choices also need an exact artifact and quantization. A guide using a Q4 download cannot prove that a Q8 file will fit the same computer.
Choose by the work you will verify
For occasional reasoning, begin with the smallest candidate that fits. Prepare a few questions with answers you can check independently. Include the sort of arithmetic, explanation or code you actually need. A longer reasoning response does not automatically mean a correct answer.
Write down correct results, unsupported claims and total waiting time. If the smaller model passes your task, a larger download may add cost without improving your workflow. If it fails, try a stronger candidate only after checking its memory plan.
When a GPU is too small
A 12 GB card cannot hold a 20 GB model file fully in VRAM. Partial offload may let a configuration run when enough system RAM is available, but this changes speed and runtime behavior. Do not apply a full-GPU benchmark to a partly CPU-based setup.
The calculator reports a planning estimate. Close other heavy applications, start with a short context and watch actual memory use. If the machine becomes unresponsive, stop the run and reduce model size.
Keep the test reproducible
- Save the model tag, quantization, engine version and operating system.
- Record system RAM, exact GPU and available VRAM.
- Keep prompt length, output limit and simultaneous users fixed.
- Repeat the same test after a model, driver or runtime update.
- Use the model profile to reach the official artifact, then submit your measured result through the contribution form.
Official facts and real user evidence
Official documentation supports product and model facts. Community discussions show real setups, failures, and questions. A community result is supporting evidence, not a promise that another computer will perform the same way.
Find a model your computer can run.
MamiLens checks your hardware and shows a careful starting point.
Run the free compatibility check →This guide is educational. Model software, licenses, and hardware support can change. Check official sources before an important deployment.