z-lab · text

Qwen3-Coder-Next-DFlash

z-lab/Qwen3-Coder-Next-DFlash

Qwen3-Coder-Next-DFlash at Q4_K_M is exactly 286,754,016 bytes (0.27 GiB / 0.29 GB) — an effective 4.840 bits per weight, not the nominal 4. Its KV cache at 32K is 0.50 GiB.

From the file· summed from 1 file(s)From the file· KV per layer
Parameters
474M
Architecture
dflash
8 layers
Context
262,144
native (config.json)
License

Shipped quantizations

exact bytes, summed from published files
QuantSizeExact bytesEffective bpwTensorsPublisher
Q4_00.25 GiB272,696,5444.603transmutator
Q4_K_M0.27 GiB286,754,0164.840transmutator
Q5_K_M0.32 GiB339,182,8165.725transmutator
Q6_K0.37 GiB394,888,4166.665transmutator
Q8_00.47 GiB509,674,7208.602transmutator
Q8_00.47 GiB509,674,7208.602AtomicChat
BF160.89 GiB954,008,80016.102transmutator

KV cache by context

computed per layer
ContextKV cache (f16)Flat formulaOverstated byFull / windowed / recurrent
4,0960.06 GiB0.06 GiB8 / 0 / 0
8,1920.13 GiB0.13 GiB8 / 0 / 0
16,3840.25 GiB0.25 GiB8 / 0 / 0
32,7680.50 GiB0.50 GiB8 / 0 / 0
65,5361.00 GiB1.00 GiB8 / 0 / 0
131,0722.00 GiB2.00 GiB8 / 0 / 0

Compare with

same modality, comparable size

Will it run on your card?

full quant x context sweep

Why other calculators give a different number

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

Architecture

from config.json
Layers
8
Attention heads
32
KV heads
4
Head dim
128
Hidden size
2048
Vocab
151,936
Sliding window
none
SWA period
MLA
no
Experts
Experts per token
use_sliding_window
false

Questions people ask

How much VRAM does Qwen3-Coder-Next-DFlash need?
Q4_K_M is exactly 286,754,016 bytes (0.27 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
How large is Qwen3-Coder-Next-DFlash's KV cache?
0.50 GiB at 32K context with an f16 cache, computed per layer. Quantizing the cache to q8_0 roughly halves it, which is often the difference between a context length fitting and not.
Which quantization of Qwen3-Coder-Next-DFlash 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.