DeepSeek DSpark Explained: 51–400% Faster V4 Inference with Speculative Decoding (2026)

On June 27, 2026, DeepSeek quietly published two new Hugging Face repos — DeepSeek-V4-Pro-DSpark and DeepSeek-V4-Flash-DSpark — alongside an open-source framework called DeepSpec. The r/LocalLLaMA threads hit a thousand upvotes within days, and the confusion started immediately: is this a new model? A DGX Spark thing? Neither. Here's what actually shipped.

What is DSpark?

DSpark is not a new model. DeepSeek says so in the first line of the model card: the DSpark repos contain the exact same V4-Pro (1.6T total / 49B active) and V4-Flash (284B / 13B active) checkpoints you already know, with one addition — a small draft model for speculative decoding attached to each.

DSpark is the name of that draft-model architecture and its training recipe. It ships inside DeepSpec, a full-stack MIT-licensed codebase covering the entire lifecycle: data preparation, draft-model training, and evaluation. DeepSpec also implements two competing algorithms — Eagle3 and DFlash — so you can benchmark all three under identical conditions.

How does speculative decoding make LLMs faster?

Autoregressive LLMs generate one token per forward pass, and each pass on a 1.6T-parameter MoE is expensive. Speculative decoding pairs the big "target" model with a tiny draft model: the draft cheaply proposes several tokens ahead, and the target verifies the whole batch in a single forward pass. Accepted tokens are free speedup; rejected ones fall back to normal decoding. The output distribution is mathematically unchanged — you get the same quality, just faster.

DeepSeek V4 already shipped with multi-token prediction (MTP) built in. DSpark replaces that single-MTP path with a stronger dedicated draft model — and the gap is large: 51% to 400% higher decoding throughput, depending on task and batch configuration, per DeepSeek's DSpark paper.

How does DSpark compare to Eagle3 and DFlash?

DeepSeek's paper benchmarks all three draft-model algorithms across gsm8k, math500, aime25, humaneval, mbpp, livecodebench, mt-bench, alpaca, and arena-hard-v2 — and DSpark comes out ahead on acceptance rate and end-to-end throughput. Notably, DeepSeek didn't just test on its own models. The released checkpoints cover four target models:

• Qwen3-4B, Qwen3-8B, Qwen3-14B — deepseek-ai/dspark_qwen3_*_block7
• Gemma-4-12B-it — deepseek-ai/dspark_gemma4_12b_block7

Each was trained on the open-perfectblend dataset with answers regenerated by its target model in non-thinking mode. That makes DSpark immediately useful to people who don't run DeepSeek at all — if you serve Qwen3 or Gemma 4 locally, you can plug in a ready-made draft checkpoint today.

How do you use DSpark?

Three paths, depending on what you run:

• Running V4-Pro or V4-Flash: pull the -DSpark variant of the checkpoint from Hugging Face. A minimal inference example lives in the repo's inference/ folder. Serving-engine integrations (vLLM, SGLang) typically follow within weeks for DeepSeek releases.
• Running Qwen3 or Gemma 4: grab the matching dspark_*_block7 draft checkpoint and point your speculative-decoding-capable engine at the target + draft pair.
• Running something else: DeepSpec's training pipeline lets you train a DSpark draft for any target model — with a caveat: the default configs assume an 8-GPU node, and the target-output cache is enormous (roughly 38 TB for even the small Qwen3-4B setting). Training your own draft is a serious infrastructure project; using the released ones is not.

Why does DSpark matter for self-hosters?

V4's headline economics were already about efficiency — the hybrid CSA/HCA attention needs only 27% of the FLOPs and 10% of the KV cache of V3.2 at 1M-token context. DSpark stacks a multiplicative speedup on top of that at decode time, which is exactly where long agentic sessions spend their money. If your agent burns an hour generating tokens, a 2–4× decode speedup is the difference between usable and not.

It also signals where the open-weights ecosystem is heading: labs now compete not just on model quality but on shipping the full inference-efficiency stack — open draft models, open training recipes, cross-vendor compatibility. Nobody else has released production-grade draft checkpoints for a competitor's models before.

Is DSpark related to NVIDIA DGX Spark?

No — the names just collide. NVIDIA's DGX Spark is a desktop AI computer (hardware); DeepSeek's DSpark is a speculative-decoding software module. If you're actually shopping for local-LLM hardware, see our DGX Spark vs RTX 5090 comparison.

FAQ

Does DSpark change DeepSeek V4's output quality?

No. Speculative decoding is lossless by construction — the target model verifies every proposed token, so the output distribution is identical to standard decoding. You get the same answers, faster.

Is DSpark free to use commercially?

Yes. The DeepSpec framework, the DSpark paper's released checkpoints, and the V4-DSpark model repos are all MIT-licensed.

Can I use DSpark with models other than DeepSeek V4?

Yes. DeepSeek released ready-trained DSpark draft checkpoints for Qwen3-4B/8B/14B and Gemma-4-12B-it, and the DeepSpec codebase can train drafts for other targets if you have the hardware.

How much faster is DSpark in practice?

DeepSeek reports 51% to 400% higher decoding throughput versus V4's built-in single-MTP path, varying by workload and batch size. Code-heavy and structured outputs tend to sit at the high end because draft acceptance rates are higher.

Do I need to retrain anything to use it with V4?

No. The V4-Pro-DSpark and V4-Flash-DSpark repos bundle the trained draft module with the unchanged base checkpoint — download and serve.

New to DeepSeek V4 itself — architecture, benchmarks, pricing, and deployment? Start with our DeepSeek V4 complete guide, then see how it stacks up in real coding work against GLM 5.2 and Kimi K2.7.