LLMBOTTLENECK.COM
Qwen / qwen3_moe

Qwen3-30B-A3B

30.5 billion parameters, routing 8 of 128 experts per token.

Open in the calculator →

Architecturepublished data
Quick answer
Qwen3-30B-A3B needs about 20.2 GB at Q4_K_M — the format most people download — with 8,192 tokens of context. It fits entirely on 12 of 18 common devices, starting with the NVIDIA GeForce RTX 4090 (24 GB). What else fits in 24 GB. No hardware for it? Rent a GPU that runs it, priced live.

Sized at 8,192 tokens of context with the whole model in device memory, across 18 common devices. Speeds are estimates, not benchmarks.

Weight-file size by format

FormatSizeRangeBasis
FP1661.1 GB60.5 GB – 61.4 GBreconstructed size
Q8_032.5 GBexactpublished data
Q6_K25.1 GBexactpublished data
Q5_K_M21.7 GBexactpublished data
Q5_021.1 GBexactpublished data
Q4_K_M18.6 GBexactpublished data
Q4_017.3 GB17.0 GB – 17.4 GBreconstructed size
Q3_K_M15.2 GB14.1 GB – 16.3 GBreconstructed size
Q2_K11.2 GB10.8 GB – 11.7 GBreconstructed size

5 of these are published files. Open the pinned GGUF repository ↗

A file size is not the memory a run needs: the KV cache and the runtime reserve come on top, and the calculator adds both.

What the labels mean
published data
Read from a published source — a file's byte count, a model's configuration or a manufacturer's specification — or exact arithmetic on such values. Not a measurement on a machine.
reconstructed size
Weight size reconstructed from the pinned architecture, because no published file exists.
size range
Only a lower and an upper bound are claimed for this weight size.

Hardware ladder

Q4_K_M at 8,192 tokens · 12 of 18 devices hold it entirely
DeviceMemoryVerdictDecodeCalculator
NVIDIA GeForce RTX 507020.2 GB of 12 GB22 layers on system RAM~53 tok/s with offloadOpen →
AMD Radeon™ RX 9070 XT20.2 GB of 16 GB11 layers on system RAM~84 tok/s with offloadOpen →
NVIDIA GeForce RTX 408020.2 GB of 16 GB11 layers on system RAM~83 tok/s with offloadOpen →
NVIDIA GeForce RTX 508020.2 GB of 16 GB11 layers on system RAM~92 tok/s with offloadOpen →
NVIDIA GeForce RTX 5070 Ti20.2 GB of 16 GB11 layers on system RAM~90 tok/s with offloadOpen →
NVIDIA GeForce RTX 5060 Ti 16GB20.2 GB of 16 GB11 layers on system RAM~67 tok/s with offloadOpen →
NVIDIA GeForce RTX 409020.2 GB of 24 GBfits~251 tok/sOpen →
AMD Radeon™ RX 7900 XTX20.2 GB of 24 GBfits~274 tok/sOpen →
NVIDIA GeForce RTX 309020.2 GB of 24 GBfits~233 tok/sOpen →
NVIDIA GeForce RTX 509020.2 GB of 32 GBfits~447 tok/sOpen →
NVIDIA RTX 6000 Ada Generation20.2 GB of 48 GBfits~239 tok/sOpen →
Apple M4 Pro20.2 GB of 64 GBfits~61 tok/sOpen →
Apple M5 Pro20.2 GB of 64 GBfits~66 tok/sOpen →
AMD Ryzen AI Max+ 395 with Radeon 8060S20.2 GB of 128 GBfits~73 tok/sOpen →
Apple M3 Max20.2 GB of 128 GBfits~77 tok/sOpen →
Apple M4 Max20.2 GB of 128 GBfits~91 tok/sOpen →
NVIDIA DGX Spark20.2 GB of 128 GBfits~68 tok/sOpen →
Apple M2 Ultra20.2 GB of 192 GBfits~107 tok/sOpen →

Decode is a calibrated estimate from the published calibration; capacity is the manufacturer's published ceiling, not guaranteed free memory. Fitting in memory is not the same as loading: whether the runtime and version you have supports this architecture and format on that machine has not been tested here. Offloaded rows assume there is enough system RAM for the overflow — the calculator checks that against the RAM you declare. Each “Open” link keeps this model, format and context.

Run it in the cloud

Rent a GPU that runs Qwen3-30B-A3B

Every rentable machine that holds the whole model, from Vast.ai and RunPod, with this site's speed estimate for each and the provider's own price, read live. Cheapest first; sort by cost per token or speed instead, or switch the format.

Prices · 18:30 UTC, 22 Sept
26 configurations in stock · 7 out of stock
MachineSpeedPer hourPer M tokensWhereRent
2× RTX 306024 GBcheapest~179 tok/sFaster than you read$0.11$0.17Vast.aiMarketplace · 98.0% reliableRent on Vast.ai
1× RTX 309024 GBrecommendedbest value~233 tok/sFaster than you read$0.12$0.15Vast.aiMarketplace · 99.5% reliableRunPod $0.50/h Rent on Vast.ai
1× RTX 3090 Ti24 GB~251 tok/sFaster than you read$0.19$0.21Vast.aiMarketplace · 99.6% reliableRunPod $0.27/h Rent on Vast.ai
2× RTX 407024 GB~251 tok/sFaster than you read$0.19$0.21Vast.aiMarketplace · 99.8% reliableRent on Vast.ai
2× RTX 4060 Ti 16GB32 GB~143 tok/sFaster than you read$0.22$0.43Vast.aiMarketplace · 99.7% reliableRent on Vast.ai
1× L424 GB~74 tok/sFaster than you read$0.26$0.95Vast.aiMarketplace · 98.9% reliableRunPod $0.49/h Rent on Vast.ai
2× RTX 5060 Ti 16GB32 GB~223 tok/sFaster than you read$0.26$0.32Vast.aiMarketplace · 99.5% reliableRent on Vast.ai
1× RTX 6000 Ada48 GB~239 tok/sFaster than you read$0.26$0.30Vast.aiMarketplace · 99.9% reliableRunPod $0.84/h Rent on Vast.ai

No GPU at all

Use Qwen3-30B-A3B by the token

Here the rented card is as cheap as the API or cheaper per token ($0.15 per million), and it keeps your data on a machine you control. The API is still the easier start: nothing to set up and nothing to switch off.

First time renting a GPU? How it works, in four steps
  1. Create an account and add credit. Both providers are prepaid: $10 is enough to try any card on this page for hours. A new RunPod account that arrives through a referral link gets a one-time $5 credit when it first adds $10.
  2. Pick the card and the count shown here, and a template: llama.cpp or vLLM for an OpenAI-compatible API, or one with a web chat if you only want to talk to the model. “How to launch it” below gives the exact image and command.
  3. Wait for the download. The weights are fetched on the machine; tens of gigabytes take a few minutes on a data-centre connection. You pay by the second from the moment it starts.
  4. Stop it when you are done. A running machine bills even when idle. A stopped one costs nothing per hour, though its disk is usually still billed until you delete it.
How to launch Q4_K_M on it (llama.cpp)
Container image
ghcr.io/ggml-org/llama.cpp:server-cuda
Start command / arguments
-hf Qwen/Qwen3-30B-A3B-GGUF:Q4_K_M -c 8192 -ngl 999 --host 0.0.0.0 --port 8080
Expose port
8080 — an OpenAI-compatible API at /v1

Starting from a saved llama.cpp template instead? Leave the arguments empty and set these variables — only the first two change between models:

LLAMA_ARG_HF_REPO=Qwen/Qwen3-30B-A3B-GGUF:Q4_K_M
LLAMA_ARG_CTX_SIZE=8192
LLAMA_ARG_N_GPU_LAYERS=999
LLAMA_ARG_HOST=0.0.0.0
LLAMA_ARG_PORT=8080

Already have the runtime? llama-server -hf Qwen/Qwen3-30B-A3B-GGUF:Q4_K_M -c 8192 -ngl 999 --host 0.0.0.0 --port 8080. Weights: Qwen/Qwen3-30B-A3B-GGUF. The CUDA image is for NVIDIA cards; an AMD machine needs llama.cpp's ROCm build.

Every machine holds the whole model at Q4_K_M and 8,192 tokens of context, no offload. Speeds are this site’s single-stream decode estimates; prices are what each provider’s own API quoted, on-demand, for the whole machine. Vast hosts below 98% measured reliability are left out.

Referral links Vast.ai, RunPod and Novita pay us a share of what you spend if you sign up through these buttons. It costs you nothing, and it never decides an order or a recommendation: both are computed from the live price and the speed, and options that pay us nothing are listed and recommended on the same terms. How we rank

Buying a card instead, or paying by the token? Compare a year of Qwen3-30B-A3B three ways →

Under the hood

Architecture, read from the publisher’s file

The numbers every figure above is computed from, with the file they came from.

Architecture

✓ Architecture read from the published config.json

Retrieved 2026-09-01 at pinned commit ad44e777bcd1; parameter count from the safetensors index at the same revision.

Architecture
qwen3_moe
Layers
48
Hidden size
2,048
Attention heads
32
KV heads
4
Head dimension
128
Feed-forward width
6,144
Vocabulary
151,936
Context ceiling
40,960
RoPE theta
1,000,000
Experts
128
Experts / token
8
Expert width
768

Where the memory goes

tokenembedding× 48 decoder blocksGrouped-query attention32 query · 4 KV headsfull contextRouted experts8 of 128 per tokenall residentoutputprojectiongrows with contextcapacity ≠ traffic

Grouped-query attention shares each key/value head across 8 query heads, so the KV cache is 13% of what multi-head attention would need at the same context.

Qwen3-30B-A3B, card by card

More from Qwen

Use this answer in your own product

As JSON, from the API
curl -s https://llmbottleneck.com/v1/analyze \
  -H "Authorization: Bearer $LLMB_KEY" -H "content-type: application/json" \
  -d '{"model":"qwen-qwen3-30b-a3b","quantization":"Q4_K_M","context":8192,"hardware":"nvidia-geforce-rtx-4090"}'

Same engine, same evidence, every field sourced. Free key in one step →

On your page, as a widget
<script src="https://llmbottleneck.com/widget.js"
  data-model="qwen-qwen3-30b-a3b" data-quantization="Q4_K_M"
  data-hardware="nvidia-geforce-rtx-4090" data-context="8192"></script>

No key needed. Unbranded, with your own buy button, on Pro and Business →

Citing this page

LLM Bottleneck. “Qwen3-30B-A3B VRAM and hardware requirements.” Architecture from Qwen/Qwen3-30B-A3B at revision ad44e777bcd1, retrieved 2026-09-01. https://llmbottleneck.com/models/qwen-qwen3-30b-a3b

Every figure above is either the published value or a reconstruction whose measured error is on the accuracy page.

llmbottleneck
catalogue 2026-10-03models 327devices 135