DeepSeek-V4-Pro

This model declares a 128-token sliding window, but we could not establish which layers use it. Its architecture publishes the layout as a per-layer array inside the model file rather than as a period in config.json, and we have not yet ingested that array.

A flat context × layers × heads figure would be substantially too high, so we are not showing one. This is tracked as a known gap rather than filled with a guess.

A parameters × bits ÷ 8 estimate puts Q4_K_M at roughly 837.58 GiB. The real file is 885.58 GiB, because a quantization is a mixture and some tensors are always kept at higher precision.

How much VRAM does DeepSeek-V4-Pro need?

Q4_K_M is exactly 950,879,579,072 bytes (885.58 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.

Is DeepSeek-V4-Pro a mixture-of-experts model?

Yes — 384 experts, 6 routed per token. Every expert must be resident, but only the routed ones are read per token, which is why its memory requirement and its speed behave very differently.

Which quantization of DeepSeek-V4-Pro should I use?

Q4_K_M is the usual default. Pick the largest quantization that fits your card at the context you actually need — the table above gives exact sizes for every one published.