DeepSeek V4 Flash 0731: Is It Cheaper to Run It at Home or Pay Per Token?

A note from the reviewer. I re-ran every calculation in this post myself. The math now checks out end to end and uses one consistent blended API rate throughout (see section 4). I couldn't independently verify external claims like the model specs, API pricing, Unsloth's GGUF measurements, or August 2026 hardware street prices, so those are repeated from the cited sources (see section 7). The headline conclusion, that running V4 Flash locally never beats the API on pure token cost, still holds, and it actually comes out stronger once the numbers are consistent.<br>The short version<br>DeepSeek V4 Flash is a 284B-parameter Mixture-of-Experts model. Only 13B parameters are active per token, and it handles a native 1M-token context under an MIT license. But that "thin" active count is misleading: all 284B weights still have to sit in memory, so you need a machine with 128GB+ of unified memory . No consumer GPU comes close.<br>The key finding of the simulation: running V4 Flash locally basically never breaks even against DeepSeek's own API. The API is so cheap (about $0.13 per million blended tokens; $0.14/$0.28 in and out) that a home machine can't even generate enough tokens to cover its own electricity at API rates, let alone pay back the hardware. The best possible local setups use Q4 and Q8 quantization on 192GB machines (those are near-lossless and bit-identical to the April preview checkpoint), and they still lose on cost per token: the best home config spends 2.4× what the API costs on electricity alone , before you've even bought the machine.<br>Buying hardware only makes sense for privacy, data sovereignty, offline use, or fine-tuning . Not for saving money. Full break-even tables are below.<br>1. The model

Property<br>DeepSeek V4 Flash

Total parameters<br>284B

Active parameters per token<br>13B

Architecture<br>Mixture-of-Experts, CSA + HCA attention

Context window<br>1,000,000 tokens (native)

Native precision<br>FP4 expert weights, FP8 KV cache

Reasoning modes<br>Non-Think, Think High, Think Max

License<br>MIT (free to download, commercial use allowed)

API price<br>$0.14 / $0.28 per million input/output tokens

The 0731 build is V4 Flash's official release, with big agentic gains over the April preview (Terminal Bench 2.1: 82.7 vs 61.8). It even beats the far bigger V4-Pro preview at 72.1.<br>One important catch: as of the research date, the improved 0731 weights are API-only . The weights you can download are the April preview (same 284B/13B architecture, just slightly weaker agentic performance). Local means April preview; the API means 0731. The call-site is the same either way: deepseek-v4-flash. So the hardware simulation below runs the April-preview weights, and you should treat the local quality numbers as applying to that checkpoint.<br>2. What you need to run it: the full quantization ladder<br>Active parameters set how much compute each token needs, but total parameters set the memory bill . The router can send any token to any expert, so every expert has to stay loaded in memory.<br>Here's Unsloth's measured GGUF ladder (July 2026), showing file size and combined RAM+VRAM floor:

Build<br>File size<br>Memory floor<br>Measured quality

2-bit (UD-IQ2_XXS)<br>87 GB<br>92–102 GB<br>about 78% top-token agreement

3-bit (UD-IQ3_XXS)<br>103 GB<br>about 110 GB<br>Unsloth's pick for 128GB machines

4-bit (UD-Q4_K_XL)<br>155 GB<br>about 162 GB<br>about 96% top-token, near-lossless

8-bit (UD-Q8_K_XL)<br>162 GB<br>about 169 GB<br>Lossless, bit-identical to the April preview

Here's the surprising part of the ladder: being lossless costs almost nothing. V4 Flash was trained to be quantization-aware, and its expert weights already ship natively in MXFP4, so the 8-bit repack is only about 7 GB bigger than the 4-bit. That's the whole price of running the exact April preview checkpoint. On a 192GB machine, the Q8 vs Q4 memory difference hardly matters.<br>The official checkpoint (FP4+FP8) is about 156 GB. On 80GB-GPU datacenter nodes, that's a tight 2× A100 (80GB) fit (160GB total) or a comfortable 2× H200 (282GB). Note that a single 141GB H200 does not fit the roughly 156GB checkpoint without heavy offload. The original post listed "1× H200 (141GB)" as a valid config, but that was a math slip and is corrected here.<br>About context: the 1M window is aimed at datacenters. At home, plan on 8K–32K context , with room for the KV cache included in the memory floors above.<br>3. The candidate machines (street prices, August 2026)<br>The 2026 memory shortage has pushed unified-memory prices way up. NVIDIA raised the DGX Spark MSRP from $3,999 to $4,699 in February, and used M3 Ultra 512GB units have traded near $25K.

Machine<br>Price<br>Builds that fit<br>Est. tps*

Mini PC Ryzen AI Max+ 395 (128GB)<br>$2,600–3,200<br>Q2, Q3<br>about 8–9

NVIDIA DGX Spark (128GB)<br>$4,699<br>Q2, Q3<br>about 7–8

Mac Studio M2 Ultra 192GB (used)<br>about $4,000<br>Q2, Q3, Q4, Q8<br>Q4 about 18

Mac Studio M3 Ultra 192GB (used)<br>about $6,000<br>Q2, Q3, Q4, Q8<br>Q4 about 22

DeepSeek API<br>pay per...