Qwen3.8-Flash-Next VRAM requirements at Q4 and 256K context
Qwen3.8-Flash-Next needs about 119 GB in this Q4_K_M, 262,144 token, batch one scenario. Extending to 1M raises that to 143 GB.
Qwen3.8-Flash-Next is called 180B, but not all of that is a normal transformer. The count is 125B of backbone, 51B of n-gram embedding and a 4B speculative layer. Only 6B parameters are active per token, routed through 512 experts with 10 chosen at a time. This page keeps all 180B resident at Q4_K_M, which the calculator prices at 0.56 bytes per parameter. That's 101 GB of weights, 7.2 GB of cache at the native 262,144 tokens, 0.12 GB of fixed state and an 11 GB runtime allowance, for 119 GB. It's the open base of the Qwen3.8 Flash API, released under the Qwen community license, version 1.0.
By TechCompare · Updated
Calculator
Estimated VRAM required
119 GB
180B params at Q4_K_M, 262,144 token context, batch 1, inference.
Estimate accuracy: Planning estimate. Rounded model counts, tensor formats, cache packing, and workspace can change actual allocation. Confirm the exact checkpoint and serving engine with a load test.
Qwen3.8-Flash-Next has 36 fixed-state Gated DeltaNet layers and 12 sparse layers. The 180B total includes a 51B n-gram embedding, which is a candidate for offloading, and a 4B speculative layer. The native context is 262,144 tokens and it can extend to 1M.
Hybrid linear attention applied: 36 of 48 layers use fixed recurrent state, so only 12 sparse-attention layers contribute to the context-growing KV cache. The fixed state adds about 0.12 GB at batch 1 and does not grow with context length.
Hardware that fits
Apple entries show installed unified memory separately from a model budget based on an 8 GB reserve. That budget is a planning heuristic, not a fixed hardware limit.
How this is calculated
The 48 layers repeat one pattern 12 times: 3 Gated DeltaNet layers, then 1 Qwen Sparse Attention layer. That makes 36 fixed state layers and 12 sparse ones, with a hidden size of 2,560. The sparse layers use 2 KV heads at head dimension 256, and each also stores a 128 value index key per token. In FP16 that's 27,648 bytes per token, so 7.2 GB at 262,144 tokens. The DeltaNet layers keep a fixed state of 0.12 GB at batch one, whatever the context. Qwen says the native context can be extended to 1M. At 1M the cache grows to 29.0 GB and the total to 143 GB. At 32K the total is 112 GB. The n-gram table is the unusual part. It's 51B of the 180B, which is 29 GB if it's stored at the same Q4 factor as everything else. Without it, the backbone and speculative layer come to 72 GB of weights. Qwen's notes call the table a candidate for offloading to system memory.
Verdict
Decide about the n-gram table before you pick hardware. If it stays on the GPU, the 256K scenario needs 2 cards of 80 GB by capacity. A single 192 GB card holds the 256K total on paper. A 128 GB unified memory machine holds the 256K total on paper but not the 1M one, and the operating system needs its share too. If the table moves to host memory, the GPU budget falls by roughly the table's share, but the host needs room and you need to measure the cost of the lookups. This estimate leaves out the speculative layer's buffers, prefill workspace, communication between GPUs and any uneven split. Check the engine you plan to use, then test with your real prompts.
More Qwen scenarios
Related guides
Frequently asked questions
How much VRAM does Qwen3.8-Flash-Next need at Q4?
Why is it a 180B model with only 6B active parameters?
Can I move the n-gram embedding table to system memory?
How much more memory does 1M context take?
Is this the same model as the Qwen3.8 Flash API?
What does this estimate leave out?
Related tools
RAM Latency Calculator
Convert DDR3/DDR4/DDR5 timings (CL, tRCD, tRP, tRAS) into true latency in nanoseconds.
Use tool ➜Power Cost Estimator
Estimate annual electricity costs for your PC, Server, or TV.
Use tool ➜Data Transfer Calculator
Estimate transfer times for files over USB, WiFi, Ethernet, and more.
Use tool ➜Memory and Storage Throughput Visualizer
Visualize the massive speed difference between CPU cache, RAM, and storage.
Use tool ➜