How to Deploy DeepSeek V4 Flash Locally
DeepSeek V4 Flash is a 284B MoE released in late July 2026, and it uses only 13B parameters per token. So despite its size, it isn't slow on machines with lots of memory. At 4-bit it is about 155 GB, too big for any single GPU or 128GB machine; at 2-bit it is about 97 GB, which the 128GB DGX Spark and Ryzen AI Max+ 395 hold entirely, at about 37 to 38 tokens/s. Its expert weights already ship in a 4-bit format, so 4-bit quantization is nearly lossless, and 8-bit is only about 7 GB larger than 4-bit.
DeepSeek V4 Flash details
- Min VRAM at 4-bit157 GB · 8K
- Parameters284B
- Active params13B
- Max context1M
- Architecture
- MoE
- Experts offloaded
- 6 GB VRAM + 152 GB RAM
- License
- MIT
- Launch date
- Jul 31, 2026
- Vendor
- DeepSeek
- Hugging Face repo
- deepseek-ai/DeepSeek-V4-Flash-0731
- GGUF repo
- unsloth/DeepSeek-V4-Flash-0731-GGUF
- NVFP4 repo (Blackwell)
- nvidia/DeepSeek-V4-Flash-0731-NVFP4
- Revision
- 0731
- Layers
- 43
- Hidden size
- 4,096
- KV heads
- 1
- Head dim
- 512
How much VRAM does DeepSeek V4 Flash need for local deployment?
| Quantization | WeightsGB | 32K contextGB | 128K contextGB | 256K contextGB | 1M context (max)GB |
|---|---|---|---|---|---|
| 1-bit | 86.9GGUF | 88.2 | 88.7 | 89.4 | 93.8 |
| 2-bit | 96.8GGUF | 98.1 | 98.6 | 99.3 | 103.7 |
| 3-bit | 128.2GGUF | 129.5 | 130 | 130.7 | 135.1 |
| 4-bit | 155.1GGUF | 156.4 | 156.9 | 157.6 | 162 |
| 5-bit | — | — | — | — | — |
| 8-bit | 161.9GGUF | 163.2 | 163.7 | 164.4 | 168.8 |
| BF16/FP16 | 596.4est. | 597.7 | 598.2 | 598.9 | 603.3 |
Full calculation rules are on the Methodology page.
Can a single GPU run DeepSeek V4 Flash?
Only at 2-bit, and only on a 96GB card or a 128GB machine. 4-bit is about 155 GB, bigger than any GPU; 2-bit is about 97 GB, which just fits on an RTX PRO 6000 and runs fast there. 128GB machines like the DGX Spark and Ryzen AI Max+ 395 hold 2-bit too, and because each token touches only a small fraction of the parameters, they still manage over 30 tokens/s. The trade-off is quality: the experts ship in 4-bit form, so 4-bit is nearly lossless and 2-bit is where real damage starts. For 4-bit on one machine, only the 512GB Mac Studio has room, at about 62 tokens/s.
| Device | Price | Speed t/s | Max context |
|---|---|---|---|
| Ryzen AI Max+ 395 128GBWhole system · 128 GB | $4,46420 listings | 36.5 | 1M |
| Mac Studio M5 Ultra 96GBWhole system · 96 GB | $7,27412 listings | 106.1 | 918K |
| MacBook Pro M5 Max 128GBWhole system · 128 GB | $7,54920 listings | 70.6 | 1M |
| $8,24022 listings | 38.5 | 1M | |
| $22,50011 listings | 125.9 | 918K | |
| Mac Studio M3 Ultra 512GBWhole system · 512 GB | $22,90013 listings | 84.8 | 1M |
| Device | Price | Speed t/s | Max context |
|---|---|---|---|
| Mac Studio M3 Ultra 512GBWhole system · 512 GB | $22,90013 listings | 62.3 | 1M |
| Device | Price | Speed t/s | Max context |
|---|---|---|---|
| Mac Studio M3 Ultra 512GBWhole system · 512 GB | $22,90013 listings | 60.5 | 1M |
Only common GPUs and systems are listed, one set for models under 50B and another for larger ones, sorted by price from low to high.
How many GPUs do you need to run DeepSeek V4 Flash?
Two 96GB RTX PRO 6000 cards are the simplest setup, and you can go straight to 8-bit: the experts ship in 4-bit form, so 8-bit is only slightly bigger, essentially original quality, fits the same two cards and runs at around 100 tokens/s. 24GB consumer cards take a full eight, since 4-bit plus 32K of context is about 156 GB, far beyond what four can hold; eight RTX 3090s do about 68 tokens/s. Four RTX A6000s or two linked DGX Sparks also hold 4-bit. Gaming cards aren't on vLLM's validated list, so confirm they work before you commit.
| Device | Cards | Total price | Total VRAM | Speed t/s | Total power |
|---|---|---|---|---|---|
| 4 cards | $3,580 | 128 GB | 88.9 | 1,000 W | |
| 4 cards | $7,400 | 128 GB | 69.5 | 920 W | |
| Instinct MI21064 GB per card | 2 cards | $9,988 | 128 GB | 120.5 | 600 W |
| Radeon RX 7900 XTX24 GB per card | 8 cards | $10,000 | 192 GB | 92.2 | 2,840 W |
| 8 cards | $14,392 | 192 GB | 90.9 | 2,800 W | |
| 4 cards | $19,596 | 192 GB | 80.8 | 1,200 W | |
| 2 cards | $21,444 | 144 GB | 110 | 600 W | |
| 8 cards | $30,064 | 192 GB | 94.8 | 3,600 W | |
| 4 cards | $33,580 | 128 GB | 125.1 | 2,300 W | |
| 2 cards | $37,998 | 160 GB | 129.1 | 600 W | |
| 2 cards | $45,000 | 192 GB | 125.1 | 1,200 W | |
| 4 cards | No price | 192 GB | 94.8 | 1,800 W |
| Device | Cards | Total price | Total VRAM | Speed t/s | Total power |
|---|---|---|---|---|---|
| 8 cards | $7,160 | 256 GB | 66.1 | 2,000 W | |
| Radeon RX 7900 XTX24 GB per card | 8 cards | $10,000 | 192 GB | 69.1 | 2,840 W |
| 8 cards | $14,392 | 192 GB | 67.9 | 2,800 W | |
| 8 cards | $14,800 | 256 GB | 49.7 | 1,840 W | |
| 2 units | $16,480 | 256 GB | 25.6 | 480 W | |
| 4 cards | $19,596 | 192 GB | 59.1 | 1,200 W | |
| Instinct MI21064 GB per card | 4 cards | $19,976 | 256 GB | 95.9 | 1,200 W |
| 8 cards | $30,064 | 192 GB | 71.4 | 3,600 W | |
| 4 cards | $42,888 | 288 GB | 85.6 | 1,200 W | |
| 2 cards | $45,000 | 192 GB | 100.7 | 1,200 W | |
| 8 cards | $67,160 | 256 GB | 100.7 | 4,600 W | |
| 4 cards | $75,996 | 320 GB | 104.7 | 1,200 W | |
| 4 cards | No price | 192 GB | 71.4 | 1,800 W |
| Device | Cards | Total price | Total VRAM | Speed t/s | Total power |
|---|---|---|---|---|---|
| 8 cards | $7,160 | 256 GB | 64.2 | 2,000 W | |
| Radeon RX 7900 XTX24 GB per card | 8 cards | $10,000 | 192 GB | 67.2 | 2,840 W |
| 8 cards | $14,392 | 192 GB | 66 | 2,800 W | |
| 8 cards | $14,800 | 256 GB | 48.1 | 1,840 W | |
| 2 units | $16,480 | 256 GB | 24.7 | 480 W | |
| 4 cards | $19,596 | 192 GB | 57.3 | 1,200 W | |
| Instinct MI21064 GB per card | 4 cards | $19,976 | 256 GB | 93.7 | 1,200 W |
| 8 cards | $30,064 | 192 GB | 69.4 | 3,600 W | |
| 4 cards | $42,888 | 288 GB | 83.5 | 1,200 W | |
| 2 cards | $45,000 | 192 GB | 98.4 | 1,200 W | |
| 8 cards | $67,160 | 256 GB | 98.4 | 4,600 W | |
| 4 cards | $75,996 | 320 GB | 102.5 | 1,200 W | |
| 4 cards | No price | 192 GB | 69.4 | 1,800 W |
Full calculation rules are on the Methodology page.
What PC or server build do you need to run DeepSeek V4 Flash locally?
With the experts in system RAM, speed depends mainly on how many memory channels you have. At 4-bit, a used 8-channel DDR4 server with one RTX 3090 does about 28 tokens/s, and a 12-channel DDR5 server with an RTX PRO 6000 about 82. At 2-bit, even an ordinary desktop can run it: a DDR5 desktop with a 16GB V100 does about 28, and a DDR4 one about 17. The 2-bit weights total about 97 GB, so a desktop needs all four slots filled with 32GB sticks. Adding -ngl 99 --cpu-moe to the llama-server command on this page puts all the experts in system RAM.
Tesla V100 32GB + Dual Xeon E5 DDR4
BudgetGeForce RTX 3090 + Single EPYC DDR4
Best valueGeForce RTX 5090 + Single EPYC DDR5
Flagship2 × Tesla V100 32GB + Dual Xeon E5 DDR4
BudgetGeForce RTX 3090 + Dual EPYC DDR4
Best valueGeForce RTX 5090 + Single EPYC DDR5
Flagship2 × Tesla V100 32GB + Dual Xeon E5 DDR4
BudgetGeForce RTX 3090 + Dual EPYC DDR4
Best valueGeForce RTX 5090 + Single EPYC DDR5
FlagshipDetailed calculation rules are on the Methodology page.
As an eBay Partner, VRAMGlass may be compensated if you buy through the eBay links on this page. The price you pay stays the same.
What to know before running DeepSeek V4 Flash locally
Quantization: use 8-bit if you can
According to unsloth's analysis, the experts, which make up 96% of the official weights, already come in a 4-bit format (MXFP4), and the rest is FP8 and BF16. So 4-bit quantization is nearly lossless and 8-bit essentially lossless, and 8-bit is only about 7 GB larger than 4-bit (161.9 vs. 155.1 GB). Only 2-bit and 3-bit are truly lossy compression; use them only when memory is short.
llama.cpp supports it, including DSpark
llama.cpp merged V4 support in late June 2026 and added DSpark speculative decoding in July (a small draft model guesses the next tokens, then the large model checks them). The draft model is a separate Q8_0 GGUF that takes about 10 GB more, and unsloth says it makes generation up to about twice as fast. Running the 0731 version in vLLM requires 0.25.0 or later.
Three thinking levels
The 0731 version has three thinking levels, low, high and max, and unsloth says the default is high. To turn thinking off in llama.cpp, use
--chat-template-kwargs '{"enable_thinking":false}'. For high and max, DeepSeek recommends leaving room for up to 384K of output. That sounds like a lot, but its context cache is tiny: at 4-bit, going from 32K to 256K adds only about 1.2 GB, so leaving plenty of context takes almost no VRAM.Official sampling parameters
Temperature 1.0;
top_p0.95 for agent use and 1.0 otherwise. unsloth's llama.cpp example also adds--min-p0.01.
Launch commands
llama.cpp
- NVIDIA
- AMD
- Mac
- CPU
llama-server -hf unsloth/DeepSeek-V4-Flash-0731-GGUF:UD-Q4_K_XL -c 8192Short on VRAM? Add --cpu-moe to keep the routed experts in system RAM (about 152 GB needed).
llama-server -hf unsloth/DeepSeek-V4-Flash-0731-GGUF:UD-Q4_K_XL \ -c 8192 -ngl 99 --cpu-moe
vLLM
- Linux
- NVIDIA
Follow the deployment guide to prepare the required runtime and hardware.
vllm serve deepseek-ai/DeepSeek-V4-Flash-0731 \ --trust-remote-code \ --kv-cache-dtype fp8 \ --block-size 256 \ --enable-expert-parallel \ --tensor-parallel-size 8 \ --tokenizer-mode deepseek_v4 \ --tool-call-parser deepseek_v4 \ --enable-auto-tool-choice \ --reasoning-parser deepseek_v4 \ --reasoning-config '{"reasoning_parser":"deepseek_v4","reasoning_start_str":"","reasoning_end_str":""}' \ --speculative-config '{"method":"dspark","num_speculative_tokens":7,"draft_sample_method":"probabilistic"}'
Ollama
- Windows
- macOS
- Linux
The Ollama library has no official tag for it yet.
File names follow that week's model-library snapshot; the definitions are in the methodology. Methodology
Other models in the DeepSeek family
| Model | Total params | Active params | 4-bit size |
|---|---|---|---|
| 8.2B | 8.2B | 5 GB | |
| 14.8B | 14.8B | 9 GB | |
| 32.8B | 32.8B | 19.9 GB | |
| 671B | 37B | 405.4 GB | |
| 763B | 8 / 16B | 444.7 GB | |
| 1,600B | 49B | 849.7 GB |