DeepSeek V4 Pro has 1598.8B parameters (49B active per token). In BF16 its weights alone take 2930 GiB; quantized to 4-bit, about 885 GiB. Each 32K-token request adds 0.28 GiB of KV cache. Cheapest way to run it today: 5 × AMD MI300X (192 GB) at $11.95 per hour.
Read every day from Hugging Face. Split files are added together; vision projectors are left out.
How many GPUs to run DeepSeek V4 Pro
Fewest GPUs that fit the weights plus one 8K-token request. Data-center GPUs use vLLM (90% of memory usable), the others llama.cpp. Several GPUs split the model with tensor or pipeline parallelism.
GPU
FP4 experts + FP8 (native)
BF16 / FP16
FP8 / INT8
4-bit (GGUF Q4_K_M)
GeForce RTX 4090 24 GB
48 (several servers)
> 128
96 (several servers)
48 (several servers)
GeForce RTX 5090 32 GB
32 (several servers)
128 (several servers)
64 (several servers)
32 (several servers)
RTX PRO 6000 Blackwell 96 GB
16 (several servers)
48 (several servers)
24 (several servers)
16 (several servers)
Mac M5 Max 128 GB 96 GB usable
16 (several servers)
48 (several servers)
24 (several servers)
16 (several servers)
NVIDIA H100 80 GB
16 (several servers)
48 (several servers)
24 (several servers)
16 (several servers)
NVIDIA H200 141 GB
7
24 (several servers)
16 (several servers)
8
NVIDIA B200 (HGX) 180 GB
6
24 (several servers)
16 (several servers)
6
Cheapest way to run DeepSeek V4 Pro today
For each GPU: the fewest cards that fit DeepSeek V4 Pro with one 8K-token request, the most faithful weight format at that count, and the cheapest on-demand price (2026-10-10).
On-demand prices from RunPod, Vast.ai, Verda and Azure, checked every hour. Serving many users needs more KV cache, so more memory: size it in the calculator. Some links are affiliate links: StudioTV may earn a commission, at no extra cost to you.
KV cache: how memory grows with context
Architecture: MoE 384 experts · 512-wide latent: 128-token window + sequence compression (30 layers 4×, 31 layers 128×). Its KV cache is 6.8× smaller than if every layer used full attention, because it keeps only a short window of tokens at full detail and compresses the rest of the sequence. Only 49B parameters are active per token, but all 1599B must sit in memory: VRAM depends on the total, speed on the active part.
Context per request
BF16 cache
FP8 cache
8K tokens
0.08 GiB
0.05 GiB
32K tokens
0.28 GiB
0.17 GiB
128K tokens
1.10 GiB
0.68 GiB
1M tokens
8.72 GiB
5.39 GiB
Plus 17.8 MiB of recurrent state per request, whatever the context.
DeepSeek V4 Pro VRAM FAQ
How much VRAM does DeepSeek V4 Pro need?
In BF16 the weights alone take 2930 GiB (3146 GB). In FP8 that is 1467 GiB, and about 885 GiB with 4-bit quantization (Q4_K_M); the official FP4 experts + FP8 checkpoint is 792 GiB. Each request then adds KV cache: 0.08 GiB at 8K tokens and 0.28 GiB at 32K (BF16 cache).
Can DeepSeek V4 Pro run on a single RTX 4090 (24 GB)?
No. Even in 4-bit it needs 48 (several servers) RTX 4090s. In 4-bit it needs 16 (several servers) H100 GPUs.
What is the cheapest way to run DeepSeek V4 Pro?
On 2026-10-10, the cheapest on-demand setup is 5 × AMD MI300X (192 GB) with FP4 experts + FP8 weights on RunPod, at $11.95 per hour (about $8,723.50 per month). Next: 4 × AMD MI355X / MI350X (288 GB) with FP4 experts + FP8 weights on RunPod, at $21.96 per hour. Sized for one 8K-token request; prices are checked every hour.
How many H100 GPUs does DeepSeek V4 Pro need?
With one request and an 8K-token context: 48 (several servers) in BF16, 24 (several servers) in FP8 and 16 (several servers) in 4-bit (vLLM, 90% of memory usable). Serving many users at once needs more memory for their KV caches: the calculator sizes that for you.
DeepSeek V4 Pro VRAM badge
For a model card or a README: the 4-bit size and the smallest GPU it fits on, linked to this page. Data as JSON: /api/models/deepseek-v4-pro.json.
[](https://studiotvai.com/vram-requirements/deepseek-v4-pro)
Estimates, not guarantees: computed from the official config.json with the same engine as the LLM VRAM Calculator. Real usage depends on your engine version and settings.