DeepSeek
DeepSeek V3 671B (671B parameters) requires approximately 470.4 GB of VRAM with Q4_K_M quantization. As a Mixture of Experts model with 37B active parameters, it uses less memory than its total parameter count suggests. For the best balance of quality and speed, we recommend hardware with at least 541 GB of VRAM.
Get started
— copy & paste to run locallyCopy-paste commands to run DeepSeek V3 671B on your machine.
Run
ollama run deepseek-v3Quick specs
About this model
Related models
Inference speed
Estimated decode speed (tokens/sec) for DeepSeek V3 671B at Q4_K_M across popular GPUs and Apple Silicon, including multi-GPU rigs, using the fastest local runtime per device. Fastest is Mac Studio M3 Ultra 256GB at ~3 tok/s. Speed is memory-bandwidth bound, so cards that fit the whole model in VRAM run far faster than ones that offload to system RAM.
| GPU / Mac | Memory | Quant | Speed (tok/s) | Fits? |
|---|---|---|---|---|
Mac Studio M3 Ultra 256GB | 256 GB | Q4_K_M | 2.8 | Too big |
Mac Studio M2 Ultra 128GB | 128 GB | Q4_K_M | 2.3 | Too big |
Mac Studio M1 Ultra 128GB | 128 GB | Q4_K_M | 2.2 | Too big |
 RTX 5090 32GB | 32 GB | Q4_K_M | 2.0 | Too big |
| RTX 4090 24GB | 24 GB | Q4_K_M | 2.0 | Too big |
| RTX 4080 Super 16GB | 16 GB | Q4_K_M | 2.0 | Too big |
| RTX 3090 24GB | 24 GB | Q4_K_M | 2.0 | Too big |
| RTX 4070 12GB | 12 GB | Q4_K_M | 2.0 | Too big |
| RTX 3060 12GB | 12 GB | Q4_K_M | 2.0 | Too big |
| RTX 4060 8GB | 8 GB | Q4_K_M | 2.0 | Too big |
RX 7900 XTX 24GB | 24 GB | Q4_K_M | 2.0 | Too big |
MacBook Pro M4 Max 128GB | 128 GB | Q4_K_M | 2.0 | Too big |
MacBook Pro M4 Max 64GB | 64 GB | Q4_K_M | 2.0 | Too big |
MacBook Pro M3 Max 64GB | 64 GB | Q4_K_M | 2.0 | Too big |
MacBook Pro M1 Max 64GB | 64 GB | Q4_K_M | 2.0 | Too big |
MacBook Pro M4 Pro 48GB | 48 GB | Q4_K_M | 2.0 | Too big |
| 2× RTX 4090 24GB | 48 GB | Q4_K_M | 2.0 | Too big |
| 2× RTX 3090 24GB | 48 GB | Q4_K_M | 2.0 | Too big |
2× RX 7900 XTX 24GB | 48 GB | Q4_K_M | 2.0 | Too big |
| 4× RTX 3060 12GB | 48 GB | Q4_K_M | 2.0 | Too big |
Estimates for single-stream decoding at Q4_K_M; real tokens/sec varies with prompt length, context, batch size, and runtime build. Prompt processing (prefill) is faster than the decode figures shown here.
Quantization
How much VRAM DeepSeek V3 671B (671B) needs at each GGUF quant, and whether it fits a 24 GB card (RTX 4090 / 3090). The recommended Q4_K_M uses ~409.3 GB — about 43% less VRAM than Q8_0, at a small quality cost.
| Quant | Bits | VRAM (weights) | Quality | Fits 24 GB? |
|---|---|---|---|---|
| Q2_K | 2 | 261.7 GB | Low | Too big |
| Q3_K_S | 3 | 328.8 GB | Low | Too big |
| NVFP4 | 4 | 375.8 GB | Medium | Too big |
| Q4_K_Mrecommended | 4 | 409.3 GB | Medium | Too big |
| Q5_K_M | 5 | 483.1 GB | High | Too big |
| Q6_K | 6 | 550.2 GB | High | Too big |
| Q8_0 | 8 | 718 GB | Very High | Too big |
| F16 | 16 | 1375.6 GB | Maximum | Too big |
VRAM shown is quantized weights only; add ~1–3 GB runtime overhead plus KV cache for your context length. Lower quants trade quality for memory — Q4_K_M is the usual sweet spot; Q2/Q3 only when you must fit a bigger model.
Quality benchmarks
Coding
Reasoning
General
Source: official · 2024-12-26
Hardware compatibility
Computing compatibility...
Memory breakdown
Frequently asked questions
DeepSeek V3 671B (671B parameters) requires approximately 470.4 GB of VRAM with Q4_K_M quantization. Lower quantizations like Q4_K_M use less memory but may reduce quality.
The recommended quantization for DeepSeek V3 671B is Q4_K_M, which offers the best balance between model quality and memory efficiency. Higher quantizations preserve more quality but require more VRAM.
Yes, DeepSeek V3 671B is well-suited for chat as well as reasoning, code. It was designed with these use cases in mind.
See also