Skip to content

Qwen3-Coder 30B-A3B VRAM Requirements

Alibaba, China · Released July 31, 2025

Qwen3-Coder 30B-A3B has 30.5B parameters (3.3B active per token). In BF16 its weights alone take 56.9 GiB; quantized to 4-bit, about 17.2 GiB. Each 32K-token request adds 3.00 GiB of KV cache. Cheapest way to run it today: 1 × GeForce RTX 3090 (24 GB) at $0.143 per hour.

Size your own setup in the calculator →

VRAM by precision and context length

Weights plus the KV cache of one request (BF16 cache), in GiB. Add 1 to 3 GiB for the inference engine itself.

Weights formatWeights only+ 8K context+ 32K context+ 128K context+ 256K context
BF16 / FP1656.957.659.968.980.9
FP8 / INT829.029.832.041.053.0
4-bit (GGUF Q4_K_M)17.218.020.229.241.2

Qwen3-Coder 30B-A3B GGUF files

Exact size of each quantization in unsloth/Qwen3-Coder-30B-A3B-Instruct-GGUF (opens in a new tab), and the smallest GPU that runs it with llama.cpp, Ollama or LM Studio and an 8K-token context.

QuantizationFile sizeSmallest GPU
BF1656.9 GiBRTX PRO 6000 Blackwell (96 GB)
UD-Q8_K_XL33.5 GiBRTX 6000 Ada (48 GB)
Q8_030.3 GiBRTX 6000 Ada (48 GB)
UD-Q6_K_XL24.5 GiBRTX 5090 (32 GB)
Q6_K23.4 GiBRTX 5090 (32 GB)
UD-Q5_K_XL20.2 GiBRTX 4090 (24 GB)
Q5_K_M20.2 GiBRTX 4090 (24 GB)
Q5_K_S19.6 GiBRTX 4090 (24 GB)
Q4_117.9 GiBRTX 4090 (24 GB)
Q4_K_M17.3 GiBRTX 4090 (24 GB)
UD-Q4_K_XL16.5 GiBRTX 4090 (24 GB)
Q4_K_S16.3 GiBRTX 4090 (24 GB)
Q4_016.2 GiBRTX 4090 (24 GB)
IQ4_NL16.1 GiBRTX 4090 (24 GB)
IQ4_XS15.3 GiBRTX 4090 (24 GB)
Q3_K_M13.7 GiBRTX 4090 (24 GB)
UD-Q3_K_XL12.9 GiBRTX 4080 / 4080 SUPER (16 GB)
Q3_K_S12.4 GiBRTX 4080 / 4080 SUPER (16 GB)
UD-IQ3_XXS12.0 GiBRTX 4080 / 4080 SUPER (16 GB)
UD-Q2_K_XL11.0 GiBRTX 4080 / 4080 SUPER (16 GB)
Q2_K_L10.6 GiBRTX 4080 / 4080 SUPER (16 GB)
Q2_K10.5 GiBRTX 4080 / 4080 SUPER (16 GB)
UD-IQ2_M10.1 GiBRTX 4080 / 4080 SUPER (16 GB)
UD-IQ2_XXS9.62 GiBRTX 4070 / 4070 SUPER (12 GB)
UD-IQ1_M8.97 GiBRTX 4070 / 4070 SUPER (12 GB)
UD-IQ1_S8.30 GiBRTX 4070 / 4070 SUPER (12 GB)
UD-TQ1_07.46 GiBRTX 4070 / 4070 SUPER (12 GB)

Read every day from Hugging Face. Split files are added together; vision projectors are left out.

How many GPUs to run Qwen3-Coder 30B-A3B

Fewest GPUs that fit the weights plus one 8K-token request. Data-center GPUs use vLLM (90% of memory usable), the others llama.cpp. Several GPUs split the model with tensor or pipeline parallelism.

GPUBF16 / FP16FP8 / INT84-bit (GGUF Q4_K_M)
GeForce RTX 4090 24 GB321
GeForce RTX 5090 32 GB211
RTX PRO 6000 Blackwell 96 GB111
Mac M5 Max 128 GB 96 GB usable111
NVIDIA H100 80 GB111
NVIDIA H200 141 GB111
NVIDIA B200 (HGX) 180 GB111

Cheapest way to run Qwen3-Coder 30B-A3B today

For each GPU: the fewest cards that fit Qwen3-Coder 30B-A3B with one 8K-token request, the most faithful weight format at that count, and the cheapest on-demand price (2026-10-10).

On-demand prices from RunPod, Vast.ai, Verda and Azure, checked every hour. Serving many users needs more KV cache, so more memory: size it in the calculator. Some links are affiliate links: StudioTV may earn a commission, at no extra cost to you.

KV cache: how memory grows with context

Architecture: MoE 128 experts · 48 layers, full attention (GQA, 4 KV heads × 128). Every layer keeps keys and values for every token (grouped-query attention), so the cache grows linearly with context. Only 3.3B parameters are active per token, but all 31B must sit in memory: VRAM depends on the total, speed on the active part.

Context per requestBF16 cacheFP8 cache
8K tokens0.75 GiB0.38 GiB
32K tokens3.00 GiB1.50 GiB
128K tokens12.0 GiB6.00 GiB
256K tokens24.0 GiB12.0 GiB

Qwen3-Coder 30B-A3B VRAM FAQ

How much VRAM does Qwen3-Coder 30B-A3B need?

In BF16 the weights alone take 56.9 GiB (61 GB). In FP8 that is 29.0 GiB, and about 17.2 GiB with 4-bit quantization (Q4_K_M). Each request then adds KV cache: 0.75 GiB at 8K tokens and 3.00 GiB at 32K (BF16 cache).

Can Qwen3-Coder 30B-A3B run on a single RTX 4090 (24 GB)?

Yes. In 4-bit (GGUF Q4_K_M) it fits on one RTX 4090 with an 8K-token context (18.0 GiB including the cache, with llama.cpp).

What is the cheapest way to run Qwen3-Coder 30B-A3B?

On 2026-10-10, the cheapest on-demand setup is 1 × GeForce RTX 3090 (24 GB) with 4-bit (GGUF Q4_K_M) weights on Vast.ai, at $0.143 per hour (about $104.39 per month). Next: 1 × GeForce RTX 4090 (24 GB) with 4-bit (GGUF Q4_K_M) weights on Vast.ai, at $0.348 per hour. Sized for one 8K-token request; prices are checked every hour.

How many H100 GPUs does Qwen3-Coder 30B-A3B need?

With one request and an 8K-token context: 1 in BF16, 1 in FP8 and 1 in 4-bit (vLLM, 90% of memory usable). Serving many users at once needs more memory for their KV caches: the calculator sizes that for you.

Qwen3-Coder 30B-A3B VRAM badge

For a model card or a README: the 4-bit size and the smallest GPU it fits on, linked to this page. Data as JSON: /api/models/qwen3-coder-30b-a3b.json.

Qwen3-Coder 30B-A3B VRAM badge

[![Qwen3-Coder 30B-A3B VRAM](https://studiotvai.com/badge/qwen3-coder-30b-a3b.svg)](https://studiotvai.com/vram-requirements/qwen3-coder-30b-a3b)

Other models

Same family (coding models): Qwen3-Coder-Next 80B-A3B · Qwen3-Coder 480B-A35B

All models: Llama 3.1 8B · Mistral Small 3.2 24B · Qwen3 32B · Llama 3.3 70B · Llama 3.1 405B · Qwen3.5 4B · Qwen3.5 9B · Qwen3.8 27B · Qwen3.6 35B-A3B · Qwen3.5 122B-A10B · Qwen3.8-Flash-Next · LFM2.5 8B-A1B · LFM2 24B-A2B · Gemma 4 12B · Gemma 4 31B · Gemma 4 26B-A4B · gpt-oss 20B · gpt-oss 120B · Llama 4 Scout 17B-16E · Llama 4 Maverick 17B-128E · Kolibri-1 · Nemotron 3 Nano 30B-A3B · Nemotron 3 Super 120B-A12B · MiniMax M2.7 · DeepSeek R1 · Kimi K2.6 · GLM-5.3 · GLM-5.3-Flash · DeepSeek V4 Flash · DeepSeek V4 Pro · DeepSeek V4.1 Flash · MiMo-V2.6 Pro · MiMo-V2.6 Flash · Kimi K3 · Mistral Large 4 · Qwen3-Coder-Next 80B-A3B · Qwen3-Coder 480B-A35B · DeepSeek V4 Flash Vision Exp · Qwen3.8 2.4T-A95B · Ornith 1.5 397B · Ornith 1.5 35B-A3B · Ornith 1.5 9B · Atria Dawn Preview · Intern S2 397B · Clef · Clef Flash · D1 3B · Humanizer · JEV 27B VL · Mellum2.1 12B-A2.5B · LightOnOCR-3 4B · Spark-X2.5 4B · Agnes-3.0-Qwen

Estimates, not guarantees: computed from the official config.json with the same engine as the LLM VRAM Calculator. Real usage depends on your engine version and settings.