DeepSeek-V4-Flash Quietly Updated, Pro Imminent: Here's the Real Deal

If you’ve refreshed r/LocalLLaMA more than twice today, you already know the news: DeepSeek-V4-Flash got a silent backend update yesterday, and the devs confirmed in a buried GitHub issue comment that “The official release of DeepSeek-V4-Pro will follow soon.”

In AI land, “soon” usually means three months and a burned-out intern. But DeepSeek actually delivers, so we’re paying attention.

The V4-Flash Update: What Actually Changed? #

I ran the new V4-Flash weights through my usual gauntlet. It’s a refine, not an overhaul. Context coherency in long threads feels noticeably better, and the benchmark scores on HumanEval finally cracked the 82% mark on my rig.

One workflow that used to break is agentic chaining. The old Flash model kept hallucinating a closing function call if the prompt got too messy. This time, it looped and self-corrected. Small thing, huge headache saved.

The real draw is the speed. Flash lives up to its name on a standard Hetzner box. If you’re still throwing money at DigitalOcean for inference endpoints, stop. A Hetzner CCX23 with 32GB of dedicated RAM handles this model at ~65 tokens/second without breaking a sweat. Setup takes 15 minutes if you use Docker over Podman.

I love this model, but it has one fatal flaw: the tokenization is still aggressively greedy with system prompts. You’ll eat 1,200 tokens before you even pass your first payload if your system prompt isn’t perfectly tight.

The Pro Question: MoE is Coming for Your VRAM #

The community is genuinely split on the incoming Pro release.

User u/quantized_quokka dropped a comment in the main discussion thread that perfectly captures the local hoarder mindset: “I have 192GB of DDR5 and a dual 3090 rig. I am physically ready for V4-Pro. Let me run the full MoE locally or let me die.”

I appreciate the enthusiasm, but this is overkill for most people. DeepSeek-V4-Pro is almost guaranteed to be a massive Mixture-of-Experts architecture. We are looking at a model that will demand serious hardware. To run it without waiting ten seconds per token, you’re going to need at least 80GB of VRAM. Even going the Mac Studio route with unified memory, an M2 Ultra with 128GB might barely survive the 4-bit GGUF quantization before your swap memory starts crying.

Do You Actually Need It? #

Honestly, Flash is enough for 90% of us.

I haven’t tested the updated Flash on ARM SBCs yet, so your mileage may vary if you’re trying to squeeze it onto an Orange Pi. But on standard x86 hardware, it’s doing everything a local LLM should do. It codes decently, it parses messy local docs, and it doesn’t wander off into the weeds when the context window hits 16k tokens.

If you rely on LLMs for complex zero-shot math reasoning, sure, wait for Pro. The Pro line has always math-dominated the Flash line. But Pro is going to be a massive pain to host. If your daily driver is still a 16GB or 24GB consumer GPU, you aren’t running Pro anyway; you’re just renting API credits.

DeepSeek killed the API market time-to-first-token with Flash. Now they’re about to do the same thing to OpenAI’s premium tiers with Pro. Either way, keep your weights dry and exl2-v2 loaders updated. We’re in for a wild August.