No single consumer GPU runs DeepSeek V4. (LongCat 2 lands in the same place, for the same reason.) The smallest working quant of V4-Flash weighs roughly 81GB as of July 2026, so before you spend anything, here is what every hardware tier actually gets you.
| Hardware tier | Usable memory | What fits | Expected experience |
|---|---|---|---|
| Single 24GB (RTX 3090/4090) | 24GB | Nothing from V4 — run DeepSeek-R1 32B instead | Great, just not V4 |
| Dual 24GB (2x 3090/4090) | 48GB | Still ~33GB short of V4-Flash’s smallest quant | Dead end for V4 |
| Quad 24GB (4x RTX 3090) | 96GB | V4-Flash at aggressive ~2-bit quants (~81GB weights) | Works, tight on context |
| 96GB workstation (2x RTX 6000 Ada) | 96GB | Same fit, two slots instead of four | Cleaner, pricier |
| 128GB Mac Studio (unified) | ~115GB usable | V4-Flash at low-to-mid quants | Usable, slow prompt processing |
| Cloud 2x H200 (rented) | 282GB | V4-Flash Q4_K_M (~158GB) + ~10GB KV cache | Comfortable, full context |
| Anything you own | — | V4-Pro: not happening (~800GB at Q4) | API only |
NVIDIA GeForce RTX 3090
24GB GDDR6XFour used RTX 3090s is the cheapest path to the ~81GB minimum that V4-Flash's smallest quant demands.
Affiliate links — we may earn a commission at no extra cost to you. Amazon ships globally; Shopee SG covers Singapore & ASEAN.
The pattern I keep seeing in V4 discussion threads: people anchor on “13B active parameters” and assume 13B-class hardware. That is the most expensive misconception in local AI right now, and this guide is the math that corrects it. MiniMax M3 catches people the same way — 427B resident against a much smaller active count. If you want a card for the older, smaller DeepSeek models, our DeepSeek GPU guide covers R1 and Coder — those still fit on one 24GB card.
VRAM capacity memory bandwidth Specs are manufacturer figures. Bar lengths are scaled independently per metric.
V4-Pro is not a consumer decision
Quick reality check so we can move on. DeepSeek V4-Pro is a 1.6-trillion-parameter MoE with 49B active parameters per token. Even at Q4, the weights alone land around 800GB — ten H100s before you allocate a single byte of KV cache. That is a datacenter deployment, and no quality-preserving quant changes it in 2026.
So for local purposes, “best GPU for DeepSeek V4” really means “best hardware for V4-Flash.” Everything below is about Flash.
V4-Flash: the quant math that matters
V4-Flash is 284B total parameters with 13B active. The community converted it fast — GGUF, AWQ, and GPTQ builds all appeared within days of the release, and llama.cpp and LM Studio both run the GGUFs without drama. What the quant sizes actually look like:
| Quant level | Approx. weights | Fits on | Quality verdict |
|---|---|---|---|
| Smallest working (~2-bit) | ~81GB | 96GB rig (4x 24GB) | Noticeably degraded, still coherent |
| Low-to-mid (~3-bit) | ~105-115GB | 128GB Mac Studio | The practical unified-memory sweet spot |
| Q4_K_M (community default) | ~158GB | 2x H200-class | Where Flash stops feeling quantized |
| Q8 and above | 280GB+ | Datacenter | Diminishing returns |
Then add the part almost everyone forgets: KV cache. At long context, budget roughly 10GB on top of the weights. That is why a comfortable Q4_K_M deployment totals about 170GB — and why a 96GB rig running the ~81GB quant has only ~15GB left for context and overhead. It runs. It just isn’t roomy, and you’ll feel it the first time you paste a large codebase into the prompt.
My honest read on the aggressive quants: 2-bit Flash still beats any 70B dense model I can run in the same footprint, because those 284B total parameters retain a lot of knowledge even when brutally compressed. But if your work is code generation or anything where subtle correctness matters, the gap between ~2-bit and Q4_K_M is real.
Check NVIDIA GeForce RTX 5090 on Amazon→Buy on Shopee SG→Mac unified memory vs. multi-GPU
The 128GB Mac Studio is the sleeper option here, and it’s a genuinely different tradeoff rather than a worse one.
The Mac case: one silent box, no 1600W power supply, and about 115GB actually allocatable to the model. Because Flash only activates 13B parameters per token, generation speed on Apple Silicon is respectable — MoE models are far kinder to unified memory bandwidth than dense ones. The pain is prompt processing: feeding in a long document takes several times longer than on NVIDIA hardware. We covered the general pattern in our Mac hardware for LLMs breakdown.
The multi-GPU case: 4x RTX 3090 gives you 96GB with vastly faster prefill and the full CUDA ecosystem. The cost is complexity — a server board with enough PCIe lanes, a big PSU, heat, noise, and llama.cpp layer-splitting configuration. Our multi-GPU setup guide walks through the actual build; read it before ordering parts, because the motherboard is the part everyone gets wrong.
Speed favors NVIDIA. Sanity favors the Mac. Budget is roughly a wash — four used 3090s plus a platform to host them lands near a 128GB Studio.
Which setup should you build?
- You own a single 24GB card: don’t build anything for V4. Run DeepSeek-R1 32B or a 70B at low quant — our 70B on a single GPU guide covers that path — and hit the API when you genuinely need V4.
- You want the cheapest real V4-Flash box: 4x used RTX 3090 (~$2,800-3,600 in cards) for 96GB. Accept the ~2-bit quant and short-ish context.
- You want V4-Flash without a server in your office: 128GB Mac Studio. Mid quants, quiet, one power cable.
- You want Q4_K_M quality: rent. 2x H200 on-demand covers the ~170GB footprint for a few dollars an hour, which buys a lot of sessions before matching workstation money.
Common mistakes to avoid
- Buying 2x 4090s expecting V4-Flash comfort. 48GB is not close. The smallest working quant is ~81GB — a dual-card build strands you $3,000+ deep with no path to running the model at all.
- Confusing 13B active with 13B VRAM. MoE routing reduces compute per token, not memory. All 284B parameters must sit in memory because any expert can be selected at any step.
- Ignoring KV cache in the budget. Weights-only math says 81GB fits in 96GB “with room to spare.” Long-context KV eats ~10GB, and suddenly your 32K session is crashing.
- Provisioning for V4-Pro because it benchmarks higher. Pro is ~800GB at Q4. If someone quotes you hardware for it, they’re quoting a datacenter.
Our verdict
| Your situation | Best move | Approx. cost |
|---|---|---|
| Cheapest working V4-Flash | 4x used RTX 3090 (96GB) | ~$3,280 in cards |
| Cleanest 96GB, two slots | 2x RTX 6000 Ada 48GB | ~$12,000 |
| Quiet single box | Mac Studio 128GB | ~$4,800 |
| Best quality per dollar | Rent 2x H200, run Q4_K_M | ~$7/hr |
| Already own one 24GB GPU | Run R1 32B locally, API for V4 | $0 |
NVIDIA RTX A6000 48GB
48GB GDDR6A pair of 48GB workstation cards hits V4-Flash's entry threshold without the quad-GPU wiring circus.
Affiliate links — we may earn a commission at no extra cost to you. Amazon ships globally; Shopee SG covers Singapore & ASEAN.
DeepSeek V4-Flash draws a hard line at roughly 81GB, and no amount of optimism moves it. Build to 96GB, buy 128GB unified, or rent 282GB — those are the three doors, and pretending a 48GB rig is a fourth one is how people waste real money.
DeepSeek V4 VRAM questions
How much VRAM does DeepSeek V4-Flash need?
As of July 2026, the smallest working quant of V4-Flash occupies roughly 81GB, so about 96GB of total VRAM is the realistic entry point once you account for KV cache and overhead. The community-default Q4_K_M build is much larger — roughly 158GB of weights plus around 10GB of KV cache at long context, or about 170GB total.
Can DeepSeek V4 run on a single RTX 5090?
No. The RTX 5090’s 32GB is far below the roughly 81GB that V4-Flash’s smallest usable quant requires, and no foreseeable quantization closes that gap. A single 5090 is still an excellent card for DeepSeek-R1 32B and other dense models in the 30-70B range — just not for anything in the V4 family.
Is a Mac Studio good for DeepSeek V4?
A 128GB Mac Studio is a legitimate single-box option for V4-Flash at low-to-mid quants, with roughly 115GB allocatable to the model. Because Flash activates only 13B parameters per token, generation speed is reasonable on Apple Silicon. The tradeoff is prompt processing, which runs several times slower than on comparable NVIDIA multi-GPU setups.
What is the hardware difference between V4-Pro and V4-Flash?
V4-Pro is 1.6T total parameters and needs roughly 800GB even at Q4 — strictly datacenter or API territory. V4-Flash is 284B total and spans roughly 81GB at its smallest quant to about 170GB at Q4_K_M with long-context KV cache, which puts it within reach of 96GB multi-GPU rigs, 128GB Macs, and rented H200 pairs.