aliteq.

How much VRAM DeepSeek V4.1 Flash (MoE) needs, and what it costs to run

Some links on this page are referral links: we may earn a commission, at no cost to you.

Trying to decide what to buy? The best GPU for DeepSeek V4.1 Flash (MoE) →

763.2B paramsMoE · 384 experts, 6 active1024k max contextmit

Just want to use it? Per-token API

$0.30in·$1.20out

per 1M tokens · DeepSeek V4.1 Flash on Novita AI · read Oct 29, 2026

No GPU to manage: you pay per token, which suits occasional use. Your prompts run on Novita's servers, not your own machine.

Price as listed on Novita's pricing page on Oct 29, 2026; it may have changed.

Memory needed, by quantisation

At 16k context. Weights + KV cache + ~0.8 GB overhead. DeepSeek V4.1 Flash (MoE) ships in FP4 + FP8, so its own release leads and no bigger copy is listed: it would only store the same numbers in more bytes. Memory is in binary GB (1,024³ bytes), the unit GPU memory is sold in; Hugging Face and Ollama list downloads in decimal GB, about 7% more.

QuantWeightsKV cacheTotalQuality
FP4 + FP8official475.3 GB0.0 GB476.0 GBThe model's own release (FP4 + FP8, a 510.3 GB download): the best quality there is. A bigger copy only stores the same numbers in more bytes. Its 4-bit GGUF builds keep the 4-bit experts as they are, so they come out about this size too.

Cards that can run it

Best quantisation each card fits at 16k context, with live rental price where we track one.

GPUVRAMBest fitUses~tok/sRent from
Apple M3 Ultra512 GBFP4 + FP8tight476 GB——
Apple M5 Ultra512 GBFP4 + FP8tight476 GB——

How these numbers are produced

  • Model shape comes from the model's own config.json — 40 layers, 64 attention heads, 1 KV heads.
  • Weight size is parameters × effective bits-per-weight. Those constants are checked against real published quantised file sizes — median error 0.7% across 40 measurements.
  • KV cache is 2 × layers × KV-heads × head-dim × context × 2 bytes. Using KV-heads rather than attention heads is what makes this correct for grouped-query attention; treating a GQA model as multi-head overstates the cache by up to 8×.
  • Tokens/sec is an estimate, not a benchmark. Generation is memory-bandwidth-bound, so this is bandwidth ÷ weight-bytes derated to 75%. Real throughput depends on your runtime, batch size and kernels. We don't run our own hardware tests — see our editorial policy.
  • This is a mixture-of-experts model. Generation reads only the experts active for each token (6 of 384), so throughput is scored on ~16.0B active parameters, not the full 763B. Memory is the opposite: every expert must still be resident in VRAM, so the figures above use the full weight set.Causal encoder-decoder (20 + 20 layers) with CSA2 sparse attention and FP4 main KV caching: the model card states the global KV cache is 890 bytes per token. Mapped so the engine's fp16 formula gives about that: 40 layers x 1 KV head x head_dim 6 x 2 x 2 B = 960 B/token (~1 GB at 1M context); the bounded sliding-window replay state is extra and small. head_dim 6 is a mapping, not the model's 512; a q8/q4 KV setting in the calculator would understate it. Active = 16B per token while decoding (8B during prefill), vendor figure. params = HF safetensors total (~763B) = 552B backbone + Engram conditional-memory tables (196B, token lookups) + vision encoder, all of which have to be stored somewhere. HF also lists a 1017 revision; Novita serves both at the same price. HF config.json + model card read 29 Oct 2026.
  • Some memory-bandwidth figures are not yet independently verified.Where that's the case we show no tokens/sec at all rather than a number we can't stand behind.
  • Rental prices are pulled hourly from provider APIs (last updated Thu, 12 Nov 2026 22:20:09 GMT). Spot/interruptible pricing can change or vanish without notice.

Try it interactively

Drag the context slider and watch the KV cache fill the card

Worth reading before you buy

Other models