<think>…</think> block before answering, and it’s the model DeepSeek is best known for. The way almost everyone runs it locally is a distill — a smaller Qwen or Llama model fine-tuned on R1’s reasoning traces, so the reasoning behavior runs on a laptop-class GPU instead of a multi-GPU server. This page leads with those distills, then covers the full 671B R1 and its siblings (V3.1, V3) for when you have the hardware to run DeepSeek’s frontier weights yourself. Pair Tokios with whatever you land on to reach it from any machine, teammate, or hosted agent through https://api.tokios.com — no inbound ports, no VPN.
Run it locally with Ollama
Thedeepseek-r1 tag on Ollama ships the distills, not the full model. Pull and run the default (currently the 7b Qwen distill):
ollama run deepseek-r1:14b. See the Ollama library page for the full tag list.
Variants & tags
Every value below is from the Ollama library and each model’s Hugging Face config. Tags, sizes, and defaults change as new quantizations ship — confirm against ollama.com/library/deepseek-r1 before you standardize on one.
Sources: ollama.com/library/deepseek-r1/tags, deepseek-ai/DeepSeek-R1 README.
Quantization & formats
Ollama’s default tags areGGUF Q4_K_M. Every distill size and the full 671b also publish -q8_0 and -fp16 tags on the library page for less lossy (and much larger) downloads. See Quantization formats and the hardware they need for what runs on your GPU, and what quantization is for how to read the Q4_K_M-style names.
Hardware fit
Comfort at roughlyQ4 for a modest context length. Treat every entry as an estimate — the ground truth is the actual GGUF size plus the KV cache for your context. See what size model fits your GPU? for the sizing math.
The full
671b needs roughly 404 GB just for weights at Q4_K_M — that’s multiple datacenter-class GPUs or an equivalent unified-memory cluster, not a single workstation. Everything 70b and under is realistic on the hardware hobbyists actually own.
Run it — beginner to advanced
- Ollama (easiest)
- LM Studio (GUI)
- vLLM (advanced)
- SGLang (advanced)
http://127.0.0.1:11434. Raise num_ctx to use more of the model’s context window.Capabilities
- Reasoning: R1 and every distill emit a
<think>…</think>block before the final answer. DeepSeek’s own model card recommends a temperature of0.5–0.7(0.6 suggested), no system prompt, and — for math — explicitly asking the model to “reason step by step” and box its final answer. - Native tool-calling: Not reliable on the distills. Ollama’s chat template for the R1 distills doesn’t support tool/function-calling the way Llama 3.1/3.3 or Qwen3 do — see ollama/ollama#8517 (closed, unresolved for the distill template). If your workload needs an agent that calls tools, pick a model built for it — see Choose a model by task.
- Context: 128K for every distill (
1.5bthrough70b); 160K for the full671bR1 and R1-0528. - Vision: None of the models on this page are multimodal — DeepSeek-R1 and its distills are text-only.
Beyond R1: V3.2 and the V4 frontier
R1 is a reasoning-tuned checkpoint built on DeepSeek’s V3 architecture. Its successors — DeepSeek-V3.2 and the current-frontier DeepSeek-V4 (Flash and Pro) — are also open-weight and MIT-licensed, but they’re multi-GPU or cloud territory, not a single-workstation pull:
Sources: ollama.com/library/deepseek-v3.1/tags, ollama.com/library/deepseek-v3/tags, Hugging Face API/
config.json for deepseek-ai/DeepSeek-V3.2, DeepSeek-V4-Flash, and DeepSeek-V4-Pro.
V3.2 and the V4 line aren’t a one-command Ollama pull yet — as of this writing they’re Hugging Face weights meant for vLLM/SGLang on multi-GPU hardware, or a hosted API. If you want DeepSeek’s current frontier model and don’t have that hardware, a cloud endpoint is the practical option; for local-first use, the R1 distills or the
671b R1/V3/V3.1 tags on Ollama are what you can actually pull today.Connect it with Tokios
Once a DeepSeek model is running locally, pair the Tokios connector so you can reach it ashttps://api.tokios.com from Claude Code, Cline, or any other compatible client — instead of only from localhost:11434.
1
Pair the Tokios connector
Sign in at tokios.com/console, open the Setup tab, and click Start pairing to get a one-time claim code (Then approve the device on the Setup or Connectors tab.
TKS-XXXX-XXXX). Install and run the connector on the machine running Ollama:Windows
macOS
Linux
2
Point the connector at Ollama's /v1 API
Ollama exposes an OpenAI-compatible surface at
/v1. For a single-model setup, the console’s Setup wizard fills this in automatically as http://127.0.0.1:11434/v1. For multiple models, set it explicitly in tokios-connector.json — see Connector config.3
Register a deployment
In the Models tab, register the model and choose a public deployment name, for example
deepseek-r1-tunnel. This name — not Ollama’s local model id — is what clients send in the model field.4
Create an API key
In the Keys tab, click Create key. Copy the
sk-tok-… key now — it’s shown only once.Call it from anywhere
Caveats
- Tool-calling is unreliable on the R1 distills. If you’re wiring up an agent, CLI, or IDE plugin that needs the model to call tools, use a model with confirmed native tool support instead — see Choose a model by task.
- Raise the context window. Ollama’s 2048-token default cuts off R1-style reasoning output quickly; increase
num_ctxfor real use, up to 128K (distills) or 160K (full671b). - A distill is not the full model. The
1.5b–70btags are Qwen/Llama checkpoints fine-tuned on R1’s reasoning traces — they reproduce the reasoning behavior on light hardware, not R1’s full capability. Benchmark quality drops as size drops; see the DeepSeek-R1 model card for the distill evaluation table. - Licensing differs by distill. The full R1/R1-0528 weights and the Qwen-based distills (
1.5b,7b,14b,32b) are MIT. The Llama-based distills (8b,70b) carry Meta’s Llama 3.1/3.3 license instead, inherited from their base model — check that license before commercial use of those two specific tags. - 671B needs real multi-GPU hardware — roughly 404 GB at
Q4_K_Malone — not a typical single-workstation setup. V3.2 and V4-Flash/Pro aren’t on Ollama yet and require the same scale via vLLM/SGLang or a hosted API. - Tokios passes tool-calling requests straight through to whatever the upstream model supports — it doesn’t add tool-calling capability the underlying model lacks.
Quickstart
Pair a connector and register your first model end to end.
Choose a model by task
Pick a model with reliable tool-calling if you’re building an agent.
Match a model to your GPU
Compare VRAM classes across distill sizes before you pick a tag.
Quantization & hardware
Which formats —
GGUF, FP16, and beyond — run on your hardware.