Qwen 3 30B-A3B VRAM Requirements

Qwen 3 30B-A3B needs about 18.8 GB of VRAM at Q4_K_M with an 8K context: 17.2 GB for weights, 0.8 GB for the KV cache and 0.8 GB of runtime overhead. At Q8_0 it needs 31.8 GB and at full FP16 precision 58.4 GB. The smallest GPU that runs it fully is the Radeon RX 7900 XT 20GB.

By Alibaba · Updated October 14, 2026 · Values from config.json on Hugging Face

18.8 GB VRAM

Qwen 3 30B-A3B at Q4_K_M with 8K context and the KV cache in FP16.

  • Weights 17.2 GB
  • KV cache 0.8 GB
  • Runtime overhead 0.8 GB

Mixture of experts: all 30.5B parameters need memory, but only 3.3B are read per token, so it runs at the speed of a much smaller model.

Which GPUs can run it

Qwen 3 30B-A3B VRAM by quantization

Total memory with an FP16 KV cache. "Smallest tier" is the smallest standard VRAM size with a 6% safety margin at 8K.

QuantizationBits/weightWeightsTotal at 8KTotal at 32KSmallest tier
Q4_K_M4.8517.2 GB18.8 GB21.0 GB20 GB
Q5_K_M5.6920.2 GB21.8 GB24.0 GB24 GB
Q6_K6.5923.4 GB25.0 GB27.2 GB32 GB
Q8_08.5030.2 GB31.8 GB34.0 GB48 GB
FP16 / BF1616.0056.8 GB58.4 GB60.6 GB64 GB
Q3_K_M3.9113.9 GB15.5 GB17.7 GB20 GB
Q2_K3.0010.7 GB12.2 GB14.5 GB16 GB

VRAM by context length

At Q4_K_M. The KV cache grows linearly with context: 0.09 GB per 1,000 tokens in FP16.

ContextKV cache (FP16)KV cache (Q8_0)Total, FP16 cacheTotal, Q8_0 cache
4K tokens0.4 GB0.2 GB18.4 GB18.2 GB
8K tokens0.8 GB0.4 GB18.8 GB18.4 GB
32K tokens3.0 GB1.6 GB21.0 GB19.6 GB
40K tokens3.8 GB2.0 GB21.8 GB20.0 GB

GPUs that can run Qwen 3 30B-A3B

At Q4_K_M with 8K context. "Best quant" is the highest-quality format that fits fully; "max context" is at Q4_K_M.

GPUUsable memoryStatusBest quantMax contextSpeed
Radeon RX 7900 XT 20GB20.0 GBFitsQ4_K_M8K~97 tok/s
Apple M5 32GB21.3 GBFitsQ4_K_M21K~35 tok/s
NVIDIA L4 24GB24.0 GBFitsQ5_K_M40K~58 tok/s
Tesla P40 24GB24.0 GBFitsQ5_K_M40K~57 tok/s
Apple M4 Max 36GB24.0 GBFitsQ5_K_M40K~72 tok/s
Intel Arc Pro B60 24GB24.0 GBFitsQ5_K_M40K~65 tok/s
RTX 3090 24GB24.0 GBFitsQ5_K_M40K~114 tok/s
Radeon RX 7900 XTX 24GB24.0 GBFitsQ5_K_M40K~107 tok/s
RTX 3090 Ti 24GB24.0 GBFitsQ5_K_M40K~118 tok/s
RTX 4090 24GB24.0 GBFitsQ5_K_M40K~118 tok/s
Radeon AI PRO R9700 32GB32.0 GBFitsQ6_K40K~86 tok/s
RTX 5090 32GB32.0 GBFitsQ6_K40K~146 tok/s
Apple M4 Pro 48GB36.0 GBFitsQ8_040K~55 tok/s
A100 40GB40.0 GBFitsQ8_040K~139 tok/s
RTX 4060 Ti 16GB16.0 GB80% on GPUQ2_K–~38 tok/s
RTX 4070 Ti Super 16GB16.0 GB80% on GPUQ2_K–~48 tok/s
RTX 4080 16GB16.0 GB80% on GPUQ2_K–~49 tok/s
RTX 4080 Super 16GB16.0 GB80% on GPUQ2_K–~49 tok/s
RTX 5060 Ti 16GB16.0 GB80% on GPUQ2_K–~44 tok/s
RTX 5070 Ti 16GB16.0 GB80% on GPUQ2_K–~51 tok/s

About Qwen 3 30B-A3B

A mixture-of-experts model with 128 experts, 8 active per token. It needs memory for all 30.5B parameters but generates text at the speed of a 3B model. With only 4 KV heads the cache is light at 96 KB per token in FP16. Because so little is read per token, it stays usable even with partial CPU offload.

SpecValue
Parameters30.5B total, 3.3B active (MoE)
Layers48
Hidden size2048
Attention heads / KV heads32 / 4
Head dimension128
Vocabulary151,936
Max context (used here)40K tokens
KV cache per token (FP16)96 KB
Released2025-04
LicenseApache 2.0

Qwen 3 30B-A3B VRAM: common questions

Why is Qwen 3 30B-A3B so fast?

Each token only reads the 3.3B active parameters, about 2 GB at Q4_K_M. Speed is limited by memory bandwidth, so it runs roughly as fast as a 3B dense model.

Can Qwen 3 30B-A3B run on 16GB VRAM?

With partial offload, yes. The weights are about 17 GB at Q4_K_M; keeping the expert layers on the CPU still gives usable speed because each token touches few experts.

How much VRAM does Qwen 3 30B-A3B need?

About 18.8 GB at Q4_K_M with an 8K context, 31.8 GB at Q8_0 and 58.4 GB at FP16. Longer contexts add 0.09 GB per 1,000 tokens with an FP16 cache.

What is the cheapest GPU that can run Qwen 3 30B-A3B?

The smallest listed device that fits it fully at Q4_K_M with 8K context is the Radeon RX 7900 XT 20GB (20.0 GB usable).

Does Qwen 3 30B-A3B need VRAM for all 30.5B parameters?

Yes. All experts must be loaded because any token can use any expert. Only 3.3B parameters are read per token, so it generates text about as fast as a 3B dense model.

Related