DeepSeek-R1 vs jina-ocr-v1
DeepSeek-R1 has 684B parameters (36.6B active per token) and takes 689 GB on disk; jina-ocr-v1 has 3.37B (708M active) and takes 6.74 GB. Compare them layer by layer.
At a glance
| deepseek-ai/DeepSeek-R1 | jinaai/jina-ocr-v1 | |
|---|---|---|
| Repo created | Jan 20, 2025updated Mar 27, 2025 | Sep 1, 2026updated Sep 18, 2026 |
| Model type | Mixture of expertsFull attention (MLA) | Mixture of expertsFull attention (MHA) |
| Inputs | Text | Text + images303M vision encoder |
| Total parameters | 684B203× more | 3.37B203× less |
| Active per token | 36.6B52× more5.4% of the model | 708M52× less21% of the model |
| Experts | 8 of 256 activeplus 1 shared, always on | 6 of 64 activeplus 2 shared, always on |
| Max context (from config) | 160K tokens5.0× more | 32K tokens5.0× less |
| Layers | 615.1× moreplus 1 extra prediction layer | 125.1× less |
| On disk | 689 GB102× more163 files | 6.74 GB102× less2 files |
| Precision | FP8 E4M3 (99%), BF16 (1.1%) | BF16 (100%) |
| Quantization | FP8 E4M3blocks of 128×128 · 99% of parameters | Noneoriginal precision (BF16) |
| Fewest GPUs | 6× NVIDIA H200fits in one 8-GPU server · weights only | 1× RTX 4060a single 8 GB card · weights only |
| License | mit | cc-by-nc-4.0 |
| GitHub | deepseek-ai/DeepSeek-R1 | Not linked |
Where the parameters live
Each bar is one model, split by component and drawn on the same scale.
Anatomy map
Every rectangle is one component in one layer, with area proportional to its size. When you compare two models, both maps use the same scale, so a model twice the size covers twice the area.
Layer map
The model's layers from input (left) to output (right): which kind of attention each one uses, and whether its feed-forward block is a mixture of experts or a single dense network.
One token's route
In a mixture-of-experts layer, a router picks a few experts for each token. This shows how many that is, drawn to scale: the lit cells are one token's share of a single layer, and everything else sits idle in memory. Which cells light up is a random example, not the model's real router.
Can my GPU handle this model?
At a datacenter
The fewest GPUs of each type whose combined memory can hold the weights, assuming 90% of each GPU's memory is usable. Real deployments need more memory for context (KV cache), and usually round up to 8 or 16 GPUs so the model splits evenly. The list covers NVIDIA data-center GPUs widely rentable as of September 2026, best first.
At home
Whether the weights fit on popular home GPUs, assuming 90% of the card's memory is usable. People at home usually run 4-bit versions (GGUF files for llama.cpp, Ollama or LM Studio), which are much smaller than what labs publish, so both are shown. The 4-bit size is an estimate of about 4.5 bits per parameter. "Tight" means the weights fit but leave little room for context.
Context memory
Besides its weights, a model needs memory for the text it's working on (the "KV cache"), and it grows with every token of context. Figures are for one conversation stored in 16-bit precision: each simultaneous conversation needs its own, and servers that store it in 8-bit (FP8) need half as much.