deepseek-v4 requirements — can you run it?
~402.9B parameters · 6 quantizations measured · updated 2026-08-31 · source: antirez/deepseek-v4-gguf
Every quantization: real file size vs what you actually need
| Quant | File (measured) | VRAM/RAM needed (8K ctx) | Runs on (first fit) |
|---|---|---|---|
| Q2KDown-AProjQ8-SExpQ8-OutQ8-chat-v2-imatrix-fixed-0731 | 97.6 GB | 118.6 GB | Mac 256GB unified |
| Q2KDown-AProjQ8-SExpQ8-OutQ8-chat-v2-imatrix-fixed | 97.6 GB | 118.6 GB | Mac 256GB unified |
| Q2KDown-AProjQ8-SExpQ8-OutQ8 | 97.6 GB | 118.6 GB | Mac 256GB unified |
| Q4K-Layers-31-output | 442.0 GB | 531.9 GB | 1TB server RAM (CPU) |
| Q4K-Layers00-30 | 457.5 GB | 550.5 GB | 1TB server RAM (CPU) |
| F16 | 805.9 GB | 968.5 GB | 2TB server RAM (CPU) |
KV cache uses a flat +20% context/overhead rule because this repo does not publish its config; exact numbers may differ for long contexts. MoE models keep all experts in memory — total size counts, not just active params.
Can I run deepseek-v4 on my GPU? (Q2KDown-AProjQ8-SExpQ8-OutQ8 recommended quant)
| Hardware | Memory | Verdict |
|---|---|---|
| RTX 3060 12GB | 12 GB | no |
| RTX 4060 Ti 16GB | 16 GB | no |
| RTX 3090 24GB | 24 GB | no |
| RTX 4090 24GB | 24 GB | no |
| RTX 5090 32GB | 32 GB | no |
| RTX PRO 6000 96GB | 96 GB | no |
| Mac 16GB unified | 16 GB | no |
| Mac 32GB unified | 32 GB | no |
| Mac 64GB unified | 64 GB | no |
| Mac 128GB unified | 128 GB | tight |
| Mac 256GB unified | 256 GB | RUNS |
| Mac 512GB unified | 512 GB | RUNS |
| 32GB system RAM (CPU) | 32 GB | no |
| 64GB system RAM (CPU) | 64 GB | no |
| 128GB system RAM (CPU) | 128 GB | tight |
| 256GB system RAM (CPU) | 256 GB | RUNS |
| 1TB server RAM (CPU) | 1024 GB | RUNS |
| 2TB server RAM (CPU) | 2048 GB | RUNS |
How much VRAM does deepseek-v4 need?
The honest answer: 118.6 GB at the Q2KDown-AProjQ8-SExpQ8-OutQ8 quant with 8K context — that is the measured file size (97.6 GB) plus KV cache and runtime overhead. The smallest published build needs 118.6 GB; the lossless one needs 968.5 GB.
Can I run it with CPU offload?
Yes, if combined RAM+VRAM ≥ file size — but generation speed is limited by memory bandwidth. Expect roughly: DDR5 dual channel ~10-30 tok/s for small MoE actives, single digits for big ones, 0.1-1 tok/s when experts page from disk. CPU-only is fine for batch jobs, painful for chat.
Why do other sites show different numbers?
Most pages compute weights from a formula (params × bits/8). We use the actual file sizes published in GGUF repos, which include the embedding table, unquantized tensors, and container overhead — that is why our numbers can differ from a naive calculation.
FAQ
How much VRAM does deepseek-v4 need?
The measured answer: 118.6 GB at the Q2KDown-AProjQ8-SExpQ8-OutQ8 quant with 8K context. The smallest published build needs 118.6 GB; the lossless (F16/BF16) build needs 968.5 GB. These are real GGUF file sizes from Hugging Face, not formula estimates.
Can I run deepseek-v4 on a 24GB GPU (RTX 3090/4090)?
Not at Q2KDown-AProjQ8-SExpQ8-OutQ8 (118.6 GB). Nothing fits 24GB — the smallest build needs 118.6 GB. Use the hosted API or a smaller model.
Can I run deepseek-v4 on CPU with system RAM?
Yes, if your usable RAM is at least the file size. At Q2KDown-AProjQ8-SExpQ8-OutQ8 you need ~118.6 GB of RAM. CPU generation is memory-bandwidth-bound: expect single-digit tok/s for large MoE models, 10-30 tok/s for small active params, and below 1 tok/s when experts page from disk.
Why do VRAM numbers for deepseek-v4 differ between sites?
Most sites compute weights from a formula (params x bits/8). ModelFit uses the actual GGUF file sizes published on Hugging Face, which include the embedding table, unquantized tensors, and container overhead — so our numbers reflect what you really download and load.