How much memory does DeepSeek V4 need in NVFP4?
DeepSeek V4 has 1600 billion parameters. The NVFP4 format decides how much memory is needed to load them.
How is this footprint calculated?
DeepSeek V4 totals 1600 billion parameters. The NVFP4 format takes 0.5 byte per parameter (4 bits per parameter, hence 0.5 byte; 4-bit published weights weigh 0.54 to 0.56 byte per parameter with their scales (DeepSeek V4 Pro 865 GB for 1,599 billion, Kimi K3 1,561 GB for 2,780 billion)). The product gives the weights, to which a 15% runtime margin is added for activations and buffers: 1,600 billion parameters × 0.5 byte (NVFP4) = 800.0 GB of weights; × 1.15 runtime margin = 920.0 GB. The attention cache is not calculated on this page. These models’ architectures (compressed latent, linear or sparse attention, Mamba layers) share no per-token formula; it is measured on the machine, with the target context and concurrency [TO BE MEASURED].
What does the format change?
NVFP4 brings Blackwell format, native FP4 compute.
| Format | Weights in memory | Compatible platforms |
|---|---|---|
| FP16 | 3,680 GB | 1 |
| FP8 | 1,840 GB | 2 |
| NVFP4 | 920 GB | 4 |
| Q4 | 1,104 GB | 4 |
Which platforms qualify?
See the DeepSeek V4 fact sheet.
How much memory for DeepSeek V4 in NVFP4?
About 920 GB for the weights, excluding the attention cache.
Which format should I choose for DeepSeek V4?
NVFP4 brings Blackwell format, native FP4 compute. The most precise format that fits the target machine remains the best choice.
Method and sources
Memory footprints are calculated, not measured: a reading on real hardware may differ depending on the engine and the exact weight format. Every figure below carries its source and the date of its last check.
- DeepSeek V4: 1,600 billion parameters, 49 billion active, 1,048,576-token context, MIT licence. Hugging Face repository (config.json, API, model card), checked on 2 September 2026. Pro variant, 1.6 trillion announced; the repository holds 1,599 billion elements, published in mixed FP4 and FP8 (865 GB).
- Bytes per parameter: FP16 2 (16 bits per parameter, hence 2 bytes); FP8 1 (8 bits per parameter (E4M3), hence 1 byte, block scales not counted); NVFP4 0.5 (4 bits per parameter, hence 0.5 byte; 4-bit published weights weigh 0.54 to 0.56 byte per parameter with their scales (DeepSeek V4 Pro 865 GB for 1,599 billion, Kimi K3 1,561 GB for 2,780 billion)); Q4 0.6 (taken here as llama.cpp Q4_K_M, 0.6 byte per parameter including scales; Q4_K_S weighs 0.56, AWQ and GPTQ 0.55). Source: connaissance/faits.yaml, quantifications family, checked on 2026-08-31.
- Runtime margin × 1.15: QDNA operating assumption, not measured: 15% above the weights for activations, buffers and fragmentation.
- “Fits” threshold at 75% of memory: QDNA assumption, not measured, which keeps the remaining quarter for the attention cache and concurrency.