DeepSeek V4 Flash has 290.9B parameters (13B active per token). In BF16 its weights alone take 530 GiB; quantized to 4-bit, about 160 GiB. Each 32K-token request adds 0.20 GiB of KV cache. Cheapest way to run it today: 7 × GeForce RTX 3090 (24 GB) at $1.00 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 Flash
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
7
32 (several servers)
16 (several servers)
8
GeForce RTX 5090 32 GB
6
24 (several servers)
16 (several servers)
6
RTX PRO 6000 Blackwell 96 GB
2
6
3
2
Mac M5 Max 128 GB 96 GB usable
2
6
3
2
NVIDIA H100 80 GB
3
8
4
3
NVIDIA H200 141 GB
2
5
3
2
NVIDIA B200 (HGX) 180 GB
1
4
2
2
Cheapest way to run DeepSeek V4 Flash today
For each GPU: the fewest cards that fit DeepSeek V4 Flash 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 256 experts · 512-wide latent: 128-token window + sequence compression (21 layers 4×, 20 layers 128×). Its KV cache is 6.9× 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 13B parameters are active per token, but all 291B must sit in memory: VRAM depends on the total, speed on the active part.
Context per request
BF16 cache
FP8 cache
8K tokens
0.05 GiB
0.03 GiB
32K tokens
0.20 GiB
0.12 GiB
128K tokens
0.77 GiB
0.47 GiB
1M tokens
6.09 GiB
3.76 GiB
Plus 11.6 MiB of recurrent state per request, whatever the context.
DeepSeek V4 Flash VRAM FAQ
How much VRAM does DeepSeek V4 Flash need?
In BF16 the weights alone take 530 GiB (569 GB). In FP8 that is 266 GiB, and about 160 GiB with 4-bit quantization (Q4_K_M); the official FP4 experts + FP8 checkpoint is 145 GiB. Each request then adds KV cache: 0.05 GiB at 8K tokens and 0.20 GiB at 32K (BF16 cache).
Can DeepSeek V4 Flash run on a single RTX 4090 (24 GB)?
No. Even in 4-bit it needs 8 RTX 4090s. In 4-bit it needs 3 H100 GPUs.
What is the cheapest way to run DeepSeek V4 Flash?
On 2026-10-10, the cheapest on-demand setup is 7 × GeForce RTX 3090 (24 GB) with FP4 experts + FP8 weights on Vast.ai, at $1.00 per hour (about $730.73 per month). Next: 4 × RTX 6000 Ada (48 GB) with FP4 experts + FP8 weights on Vast.ai, at $1.98 per hour. Sized for one 8K-token request; prices are checked every hour.
How many H100 GPUs does DeepSeek V4 Flash need?
With one request and an 8K-token context: 8 in BF16, 4 in FP8 and 3 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 Flash 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-flash.json.
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.