Qwen3 30B-A3B VRAM requirements

Qwen3 30B-A3B needs about 20.2 GB of VRAM at Q4_K_M with 8K context, so it fits a 24 GB card such as the RTX 3090 or the RTX 4090. Qwen3 30B-A3B has 30.5B parameters, of which about 3.3B are used per token; all 128 experts still have to be in memory. With the same 8K context and one request it needs 32.6 GB at FP8 and 63.9 GB at FP16/BF16. The published weights take 56.9 GB (BF16). The smallest setup here that holds it at Q4_K_M with an 8K context is the RTX 3090 (24 GB), which runs it with up to 39K tokens of context.

20.2 GB at Q4_K_M, 8K context, one request

FP8
32.6 GB
FP16 / BF16
63.9 GB
Published weights
56.9 GB
Smallest setup, Q4_K_M
RTX 3090 (24 GB)
Open Qwen3 30B-A3B in the calculator

Worked example: Qwen3 30B-A3B with 32K tokens

Inputs: Qwen3 30B-A3B · Q4_K_M weights · 32,768 tokens of context · one request · FP16 KV cache

Weights (30.5B at Q4_K_M)
17.2 GB
KV cache (96 KB per token)
3.00 GB
Buffers and runtime (0.5 GB + 10%)
2.52 GB
Total
22.7 GB

The smallest setup here that holds it is the RTX 3090 (24 GB), with about 1.28 GB to spare. Change the inputs in the calculator

What makes Qwen3 30B-A3B's memory use different

Per token of context it adds 96 KB of FP16 cache; Granite 4.2 30B (29.3B), the nearest-sized model here with plain full attention, adds 256 KB, so Qwen3 30B-A3B needs 38% as much.

As a mixture-of-experts model it reads about 1.86 GB of its 17.2 GB Q4_K_M weights per generated token (11%), so it writes like a much smaller model while needing memory for all of them.

Running Qwen3 30B-A3B with experts in system RAM

llama.cpp's --n-cpu-moe N keeps the experts of the first N layers in RAM. For the measured Q4_K_M GGUF with 32K tokens of context, the smallest N that fits each card, and the speed with 89.6 GB/s of system RAM. Plan the offload for another GPU. The VRAM here can sit below the 22.7 GB of the worked example because it counts the file's measured bytes, keeps the input embedding (token_embd) in system RAM as llama.cpp does and adds a flat 1 GB of buffers, where the estimate above adds 0.5 GB plus 10% to the preset's weights.

GPU--n-cpu-moeVRAM usedIn system RAMTokens/s
RTX 5060 Ti 16GB 16 GB 15 15.9 GB 5.34 GB 20–34
RTX 4090 24 GB 0 (all on the GPU) 21.1 GB 167 MB 54–93
RTX 5090 32 GB 0 (all on the GPU) 21.1 GB 167 MB 90–160

In system RAM counts the offloaded experts plus the input embedding (token_embd), which stays in RAM even with --n-cpu-moe 0.

How much VRAM does Qwen3 30B-A3B need?

Qwen3 30B-A3B needs 20.2 GB at Q4_K_M, 34.6 GB at Q8_0 and 63.9 GB at FP16 with 8,192 tokens of context and one request. Each total below is the weights plus the FP16 KV cache and the runtime overhead (0.5 GB plus 10%), and each row opens the calculator with that setting. What the GGUF names mean.

PrecisionWeightsTotalSmallest setup
As published (BF16) 56.9 GB 63.9 GB A100 80GB
FP16 / BF16 56.9 GB 63.9 GB A100 80GB
FP8 / INT8 28.4 GB 32.6 GB M4 Pro Mac (64 GB, 48 GB usable)
INT4 (AWQ / GPTQ) 15.1 GB 17.9 GB RTX 3090 (24 GB)
GGUF Q8_0 30.2 GB 34.6 GB M4 Pro Mac (64 GB, 48 GB usable)
GGUF Q6_K 23.3 GB 27.0 GB RTX 5090 (32 GB)
GGUF Q5_K_M 20.2 GB 23.5 GB RTX 3090 (24 GB)
GGUF Q4_K_M 17.2 GB 20.2 GB RTX 3090 (24 GB)
GGUF IQ4_XS 15.5 GB 18.3 GB RTX 3090 (24 GB)
GGUF Q3_K_M 13.9 GB 16.6 GB RTX 3090 (24 GB)
GGUF IQ3_XXS 11.7 GB 14.2 GB RTX 4060 Ti 16GB
GGUF Q2_K 11.9 GB 14.4 GB RTX 4060 Ti 16GB

Fine-tuning Qwen3 30B-A3B? Qwen3 30B-A3B VRAM for LoRA, QLoRA and full training.

Qwen3 30B-A3B GGUF files on Hugging Face

The 8 GGUF files llama.cpp picks for Qwen3 30B-A3B with -hf <repo>:<QUANT>, with the bytes the Hugging Face file list reported on 2026-09-29. Each total is that file plus the FP16 KV cache and 0.5 GB + 10%, one request. "vs estimate" compares the file with the bits-per-weight size the table above uses.

QuantFileSizevs estimate 8K32K40K (full)
Q2_K unsloth/Qwen3-30B-A3B-GGUF 10.5 GB11,258,610,240 bytes −12% 12.9 GB15.3 GB16.2 GB
Q3_K_M unsloth/Qwen3-30B-A3B-GGUF 13.7 GB14,711,847,488 bytes −1% 16.4 GB18.9 GB19.7 GB
IQ4_XS unsloth/Qwen3-30B-A3B-GGUF 15.3 GB16,378,073,664 bytes −1% 18.1 GB20.6 GB21.4 GB
Q4_K_M ggml-org/Qwen3-30B-A3B-GGUF 17.3 GB18,556,686,240 bytes ±0% 20.3 GB22.8 GB23.6 GB
Q5_K_M unsloth/Qwen3-30B-A3B-GGUF 20.2 GB21,725,581,888 bytes ±0% 23.6 GB26.1 GB26.9 GB
Q6_K unsloth/Qwen3-30B-A3B-GGUF 23.4 GB25,092,532,800 bytes ±0% 27.0 GB29.5 GB30.3 GB
Q8_0 ggml-org/Qwen3-30B-A3B-GGUF 30.3 GB32,483,932,064 bytes ±0% 34.6 GB37.1 GB37.9 GB
BF16 unsloth/Qwen3-30B-A3B-GGUF2 parts 56.9 GB61,095,803,424 bytes ±0% 63.9 GB66.4 GB67.2 GB

GB here is GiB (1024³ bytes), as everywhere on this site; Hugging Face shows the Q4_K_M file as 18.6 GB, in 10⁹ bytes.

Which Qwen3 30B-A3B GGUF fits a 16, 24, 32, 48 or 80 GB GPU or a Mac

From the file sizes above: the largest file that fits each machine with an 8K context and 0.5 GB left free, the longest context it then has room for, and the longest context for Q4_K_M (17.3 GB). One request, FP16 KV cache. Where nothing fits, the --n-cpu-moe table above keeps experts in system RAM.

HardwareLargest GGUF, 8KIts longest contextQ4_K_M, longest context
RTX 5060 Ti 16GB Q2_K, 10.5 GB 33K No
RTX 4090 (24 GB) Q4_K_M, 17.3 GB 38K 38K
RTX 5090 (32 GB) Q6_K, 23.4 GB 40K (full) 40K (full)
L40S (48 GB) Q8_0, 30.3 GB 40K (full) 40K (full)
H100 SXM (80 GB) BF16, 56.9 GB 40K (full) 40K (full)
M4 Pro Mac (64 GB, 48 GB usable) Q8_0, 30.3 GB 40K (full) 40K (full)
M4 Max Mac (128 GB, 96 GB usable) BF16, 56.9 GB 40K (full) 40K (full)

Run Qwen3 30B-A3B with llama.cpp or Ollama

llama-server -hf ggml-org/Qwen3-30B-A3B-GGUF:Q4_K_M -c 38912

Qwen3-30B-A3B-Q4_K_M.gguf, 18.6 GB, from ggml-org/Qwen3-30B-A3B-GGUF (checked 2026-09-29). On a 24 GB RTX 3090 / 4090, Q4_K_M with -c 38912 takes 23.4 GB and leaves 584 MB.

ollama run qwen3:30b-a3b

Ollama library tag qwen3:30b-a3b; its quant is Ollama's choice. Same context: /set parameter num_ctx 38912.

Qwen3 30B-A3B at 8K, 32K and 40K (full) tokens of context

All 48 layers use full attention. Each extra token of context adds 96 KB of FP16 cache per request. The last column is the smallest setup here, one card or a group, that holds it at Q4_K_M. How the KV cache works.

ContextKV cache, FP16Total at Q4_K_MTotal at Q8_0Smallest setup, Q4_K_M
8K tokens 768 MB 20.2 GB 34.6 GB RTX 3090 (24 GB)
32K tokens 3.00 GB 22.7 GB 37.0 GB RTX 3090 (24 GB)
40K tokens 3.75 GB 23.5 GB 37.9 GB RTX 3090 (24 GB)

How fast Qwen3 30B-A3B writes

Tokens per second for one request with 8,192 tokens of context, estimated from memory bandwidth and the parameters read per token. A dash means it does not fit on one card. Try other settings in the speed calculator.

HardwareBandwidthQ4_K_MFP8
RTX 3060 12GB 360 GB/s ——
RTX 4090 1,008 GB/s 93–165—
RTX 5090 1,792 GB/s 149–276—
M4 Max Mac (128 GB) 546 GB/s 54–9338–64
M3 Ultra Mac Studio (512 GB) 819 GB/s 77–13655–95
H100 SXM 3,350 GB/s 233–460179–339
H200 4,800 GB/s 290–600230–452

Longest context on one GPU

How many tokens of context Qwen3 30B-A3B fits on a single card with one request, an FP16 KV cache and 0.5 GB left free. "Full" means the model's whole context window fits.

GPUMemoryQ4_K_MQ8_0FP8
RTX 3060 12 GB NoNoNo
RTX 4060 Ti 16GB 16 GB NoNoNo
RTX 3090 / 4090 24 GB 39KNoNo
RTX 5090 32 GB 40K (full)NoNo
A100 40GB 40 GB 40K (full)40K (full)40K (full)
Mac, 64 GB unified memory 48 GB 40K (full)40K (full)40K (full)
L40S / RTX 6000 Ada 48 GB 40K (full)40K (full)40K (full)
A100 / H100 80GB 80 GB 40K (full)40K (full)40K (full)
Mac, 128 GB unified memory 96 GB 40K (full)40K (full)40K (full)
H200 141 GB 40K (full)40K (full)40K (full)
B200 180 GB 40K (full)40K (full)40K (full)

Model details

Parameters
30.5B (30,532,122,624)
Experts
128 routed experts, all loaded
Active per token
3.3B
Layers
All 48 layers use full attention
Attention cache
4 KV heads × 128
Context length
40,960 tokens
Published weights
56.9 GB (BF16)
On Hugging Face
Qwen/Qwen3-30B-A3B
Reported benchmarks
None published in the model card for GPQA, MMLU-Pro or LiveCodeBench.

Why this estimate looks this way

At Q4_K_M and an 8K-token context, Qwen3 30B-A3B uses 17.2 GB for weights, 768 MB for its FP16 KV cache and 2.30 GB for estimated runtime overhead, totaling 20.2 GB. The overhead is a 0.5 GB base plus 10% of weights and cache.

This is a mixture-of-experts model: all 128 experts contribute to the 30.5B parameters held in memory, even though only about 3.3B parameters run per token. Using only active parameters would understate VRAM.

The architecture and published checkpoint size come from the model's config.json and weight files. These are estimates rather than measured peak memory; inference engines can reserve extra buffers or preallocate the full configured cache.

Qwen3 30B-A3B next to similar-sized models

The three models here closest to it in parameter count, at Q4_K_M with 8,192 tokens of context.

ModelParametersTotalKV per tokenSmallest setup
Qwen3 30B-A3B 30.5B, 3.3B active 20.2 GB 96 KB RTX 3090 (24 GB)
Qwen3-Coder 30B-A3B 30.5B, 3.3B active 20.2 GB 96 KB RTX 3090 (24 GB)
Xing 4.0 29B-A4B 31.2B, 4B active 20.2 GB 45 KB RTX 3090 (24 GB)
GLM-4.7 Flash 31.2B, 3B active 20.3 GB 53 KB RTX 3090 (24 GB)

Qwen3 30B-A3B VRAM questions

How much VRAM do I need to run Qwen3 30B-A3B locally?

About 20.2 GB at Q4_K_M with an 8K context and one request, by the bits-per-weight estimate, and 63.9 GB at BF16. The Q4_K_M GGUF Qwen3-30B-A3B-Q4_K_M.gguf in ggml-org/Qwen3-30B-A3B-GGUF is 18,556,686,240 bytes (17.3 GB); with an 8K context it needs 20.3 GB. The smallest setup listed here that holds Q4_K_M is the RTX 3090 (24 GB).

Can I run Qwen3 30B-A3B on a 24 GB GPU?

Yes. On the RTX 4090 (24 GB), the largest listed GGUF that fits with an 8K context and 0.5 GB free is Q4_K_M (17.3 GB), with up to 38K tokens of context.

Which quantization of Qwen3 30B-A3B fits in 16 GB of VRAM?

On the RTX 5060 Ti 16GB, the largest listed GGUF that fits with an 8K context and 0.5 GB free is Q2_K (10.5 GB), with up to 33K tokens of context.

Can I run Qwen3 30B-A3B on a Mac?

On the M4 Pro Mac (64 GB, 48 GB usable), the largest listed GGUF that fits with an 8K context and 0.5 GB free is Q8_0 (30.3 GB), with its full 40K-token context. On the M4 Max Mac (128 GB, 96 GB usable), the largest listed GGUF that fits with an 8K context and 0.5 GB free is BF16 (56.9 GB), with its full 40K-token context. By default macOS lets the GPU use about 75% of unified memory.

How much more VRAM does Qwen3 30B-A3B need for 32K or 40K tokens of context?

Its FP16 KV cache is 768 MB at 8K, 3.00 GB at 32K, 3.75 GB at 40K for one request, so 40K (its limit) adds 3.00 GB over 8K, plus 10% overhead. A q8_0 cache (-ctk q8_0 -ctv q8_0) takes 1.99 GB at 40K.

Why does Qwen3 30B-A3B use more VRAM than its GGUF file size?

The file holds only the weights. At Q4_K_M with an 8K context: 17.3 GB of weights (the file's 18,556,686,240 bytes) + 768 MB of FP16 KV cache + 2.30 GB of compute buffers and runtime (0.5 GB + 10%) = 20.3 GB.

Does Qwen3 30B-A3B need less VRAM because only 3.3B parameters are active?

No. All 128 experts stay loaded, so the Q4_K_M file takes 17.3 GB. The active parameters decide speed: each generated token reads about 1.86 GB of them.

Badge for your model card

Paste it into a Hugging Face or GitHub README; it shows the Q4_K_M total above and links to this page. Q8_0 and FP16 badges.

Qwen3 30B-A3B VRAM: 20.2 GB at Q4_K_M, 8K context

Numbers read from the model files on Hugging Face on . Compare it with other models in the reproducible model and GPU report.