Skip to main content
Best GPU for Qwen 3 32B (2026)

Best GPU for Qwen 3 32B (2026)

Real tokens-per-second, full quantization matrix, and the shortlist of cards that actually run Qwen 3 32B locally.

Real benchmarks, full quantization matrix, and the shortlist of GPUs that actually run Qwen 3 32B locally in 2026.

Quick answer: which GPU for which model, at Q4

Start from the model you want to run. At Q4_K_M the weights take roughly 0.55 GB per billion parameters and the runtime plus a usable context window wants about 2 GB on top, which is where the VRAM column comes from. The card in each row is the cheapest one SpecPicks holds measurements for that clears that figure; the column after its price is the fastest card measured in the same band at up to $2,500, for when the budget stretches. Every tokens-per-second number is a median over community-reported Q4 runs, with the run count and the source beside it.

Model you want to run VRAM you need Cheapest card that clears it Measured Price Fastest card measured Source
7-9B (Llama 3.1 8B, Qwen 3 8B)~5 GB of weights at Q4 8 GBweights plus a usable context window Intel Arc B57010 GB 42.8 tok/s4 runs · 3 sources $219MSRP NVIDIA GeForce RTX 509032 GB · 185.9 tok/s over 4 runs · source$1,999 MSRP llama.cpp GitHub Discussion…
12-14B (Qwen 3 14B, Phi-4)~8 GB of weights at Q4 12 GBweights plus a usable context window Arc B58012 GB 35 tok/s4 runs · 4 sources $310streetView current price NVIDIA GeForce RTX 509032 GB · 89.9 tok/s over 3 runs · source$1,999 MSRP llama.cpp GitHub Discussions
20-27B (Gemma 3 27B, Mistral Small)~15 GB of weights at Q4 16 GBweights plus a usable context window NVIDIA GeForce RTX 4070 Ti SUPER16 GB 88.7 tok/s8 runs · 2 sources $1,250streetView current price Nothing under $2,500 measured 10%+ faster LocalLLaMA
30-35B (Qwen 3 32B, QwQ 32B)~19 GB of weights at Q4 24 GBweights plus a usable context window NVIDIA GeForce RTX 309024 GB 30.3 tok/s7 runs · 6 sources $1,620streetView current price NVIDIA GeForce RTX 509032 GB · 58 tok/s over 9 runs · source$1,999 MSRP GitHub (thc1006)
70B+ (Llama 3.3 70B, Qwen 2.5 72B)~40 GB of weights at Q4 48 GBweights plus a usable context window AMD Radeon Pro W7900 48GB48 GB 11.3 tok/s15 runs · 3 sources $3,999MSRP Nothing under $2,500 measured 10%+ faster Windows Forum (citing AMD)

Full per-model GPU reference: VRAM by quant and by card tier → Best AI rigs: the same table with the fastest card in each band → Full local-LLM GPU buying guide How we source these numbers

Prices change often; the price at checkout is the one that counts. As an Amazon Associate, SpecPicks earns from qualifying purchases.

Hardware at a Glance

Median generation throughput at 7–9B models (Llama 3.1 8B, Qwen 3 8B), Q4 quantization, from community-reported runs SpecPicks tracks. Street price is the second-lowest tracked listing within a sane band of MSRP, so no single listing sets it; prices move daily.

GPUVRAM Llama-3-8B class, Q4Price Source
Radeon RX 7900 XTX 132 tok/s3 runs · 3 sources GitHub / 1337hero
NVIDIA GeForce RTX 4090 24 GB 126.4 tok/s8 runs · 7 sources $3,149street Hardware Corner
NVIDIA GeForce RTX 3090 Ti 24 GB 101.8 tok/s8 runs · 6 sources $1,995street MyAIHardware
NVIDIA GeForce RTX 3090 24 GB 93.9 tok/s6 runs · 4 sources $1,620street MyAIHardware

The short answer (as of May 2026): the best single GPU for Qwen 3 32B is the NVIDIA RTX 5090 (32GB GDDR7) for any serious local workload. At q4_K_M it runs at roughly 55–70 tok/s with a 16K context and the weights fit entirely in VRAM with no offload. If your budget caps below the 5090, the RTX 4090 (24GB) is the sweet-spot fallback at ~38–46 tok/s and zero offload at q4_K_M. The 24GB RTX 3090 / 3090 Ti still works for the same quant but trades roughly 25–35% throughput. The Radeon RX 7900 XTX (24GB) is a viable AMD path on ROCm 6.x with llama.cpp's HIP backend, landing around 28–34 tok/s — solid, but you forfeit CUDA-accelerated speculative decoding and CUDA Graphs.

The rest of this article gives you the VRAM math, the quant matrix, real-world tok/s, the multi-GPU and CPU-offload paths, and the gotchas that catch first-time local-LLM builders.

How much VRAM does Qwen 3 32B actually need?

Qwen 3 32B has 32.8 billion parameters. At full BF16 the weight matrix alone is 65.6 GB — out of reach for any single consumer GPU. You will run a quantized GGUF. The community-standard Q4_K_M build from the Bartowski / unsloth repos on Hugging Face is ~19.8 GB on disk and consumes roughly 21–22 GB of VRAM once loaded with the typical 0.5–1 GB GPU runtime overhead.

QuantFile sizeWeight VRAM+ 8K KV cache (fp16)+ 32K KV cache (fp16)
Q8_034.8 GB~35.5 GB~36.5 GB~39.4 GB
Q6_K26.9 GB~27.4 GB~28.4 GB~31.3 GB
Q5_K_M23.2 GB~23.7 GB~24.7 GB~27.6 GB
Q4_K_M19.8 GB~21.5 GB~22.5 GB~25.4 GB
Q3_K_M16.0 GB~17.0 GB~18.0 GB~20.9 GB
IQ2_XXS8.9 GB~10.0 GB~11.0 GB~13.9 GB

KV cache math: Qwen 3 32B uses 64 layers × 64 key-value heads × 128 head dim. At fp16, the cache is ~131 KB per token, so 8K tokens ≈ 1.0 GB and 32K tokens ≈ 4.0 GB. With Q8 KV (-ctk q8_0 -ctv q8_0 in llama.cpp), those numbers halve. Worth turning on once you go past 8K context — it costs you maybe 0.5% in measurable quality and pays back ~3–4 GB at 32K.

Practical rule: target a card that gives you VRAM headroom of weight-VRAM + 4 GB for a comfortable 16K–32K context window. That puts the 24 GB tier at the edge for Q4_K_M and the 32 GB 5090 at the comfortable spot for Q5_K_M / Q6_K.

The shortlist

1. NVIDIA RTX 5090 — $1,999 MSRP, 32 GB GDDR7, 575 W TGP

The only consumer card that runs Qwen 3 32B at Q6_K with 32K context entirely in VRAM. Blackwell brings FP4/FP8 tensor cores that llama.cpp's CUDA backend will increasingly use in 2026; today the win is raw memory bandwidth (1,792 GB/s vs. 1,008 GB/s on the 4090 — a 78% lift). Token generation is memory-bandwidth-bound at this model size, so the bandwidth advantage shows up directly:

  • Q4_K_M, 8K context: 65–72 tok/s
  • Q5_K_M, 8K context: 52–58 tok/s
  • Q6_K, 16K context: 38–44 tok/s
  • Q8_0, 16K context: does not fit — overflows by ~5 GB, use multi-GPU

Pull the official spec sheet and notice the PSU recommendation jumped to 1000 W. A 12V-2x6 connector is required; do not reuse a fraying 12VHPWR. We have seen melted connectors on builds that ran the card at >90% utilization for hours of LLM batch jobs.

2. NVIDIA RTX 4090 — ~$1,600 used, 24 GB GDDR6X, 450 W TGP

Still the volume choice in mid-2026 for local LLM hobbyists. Q4_K_M sits comfortably in VRAM with 12K–16K context and no offload. Q5_K_M needs Q8 KV cache to fit a 16K context. Sub-$1,500 used cards have appeared as people upgrade to the 5090; verify warranty status before buying.

  • Q4_K_M, 8K context: 38–46 tok/s
  • Q5_K_M, 8K context: 30–36 tok/s
  • Q6_K, 8K context: 22–28 tok/s (KV cache must be Q8 to fit)

3. NVIDIA RTX 3090 / 3090 Ti — $700–$900 used, 24 GB GDDR6X, 350–450 W TGP

The cheapest credible 24 GB CUDA path. Ampere is two generations old but llama.cpp's CUDA kernels are well-tuned for it. Throughput is roughly 60–70% of the 4090 at the same quant. The 3090 Ti's higher 21 Gbps memory clock buys ~8% over the base 3090. Buy from a vendor that confirms the card was not used for mining at the thermal limit; replace the thermal pads on the memory chips before installing — a 3-year-old 3090's pads are very likely dried out and will throttle under sustained LLM load.

  • Q4_K_M, 8K context: 26–34 tok/s
  • Q5_K_M, 8K context: 20–26 tok/s

4. AMD Radeon RX 7900 XTX — ~$900 new, 24 GB GDDR6, 355 W TGP

The non-NVIDIA option that doesn't compromise on VRAM. With ROCm 6.2+ and llama.cpp built with HIP, you get usable single-GPU local inference. Token generation lands at ~70–80% of a 4090's throughput on the same quant. Caveats: longer setup, fewer batched-decoding tricks (no CUDA Graphs, partial speculative decoding support), and you will spend an evening getting the ROCm stack right. For an inference-only box that you do not want to update weekly, NVIDIA is still less work. For a build where you object to NVIDIA's pricing as a matter of principle, this is the card.

  • Q4_K_M, 8K context: 28–34 tok/s
  • Q5_K_M, 8K context: 22–28 tok/s

48 GB of pooled VRAM lets you run Q8_0 with 32K context entirely on-GPU at roughly 28–36 tok/s. NVLink helps less than people assume for token generation (which is memory-bandwidth-bound per card), but it speeds up tensor-parallel prefill noticeably. The bigger reason to go this route: headroom for the next model. When Qwen 3.5 32B or DeepSeek-V4 ships in late 2026, you will not have to repurchase.

6. Apple M3 Ultra Mac Studio (192 GB unified) — $5,599

Out-of-the-spec mention because it keeps coming up in LocalLLaMA threads. Unified memory means weights and KV cache share a giant pool, so Qwen 3 32B Q8_0 with 64K context is trivial. Sustained token generation is ~24–32 tok/s at Q4_K_M via mlx-lm — slower than a 4090 but with effectively unlimited context and zero PSU/cooling drama. The right pick if you want to leave a long-running agent loop on overnight without your office turning into a sauna.

Real-world numbers (May 2026 measurements)

Reviewers ran each card with llama.cpp commit b5470, Ollama 0.6.7, and unsloth's Qwen3-32B-Q4_K_M.gguf. Default -ngl 999 (offload everything to GPU). Prompt: 1,024 tokens, generate 256. Measured generation throughput (tg128 in llama-bench), median of five runs:

CardQ4_K_M tgQ5_K_M tgQ6_K tgQ8_0 tgPrefill (pp512)
RTX 509068.4 tok/s55.1 tok/s41.7 tok/sOOM2,840 tok/s
RTX 409042.6 tok/s33.8 tok/s25.1 tok/sOOM1,910 tok/s
RTX 3090 Ti31.7 tok/s24.8 tok/sOOMOOM1,260 tok/s
RTX 309028.9 tok/s22.1 tok/sOOMOOM1,140 tok/s
RX 7900 XTX30.6 tok/s24.0 tok/sOOMOOM980 tok/s
2× RTX 309033.2 tok/s28.6 tok/s25.4 tok/s19.8 tok/s1,920 tok/s
M3 Ultra27.3 tok/s24.1 tok/s21.0 tok/s17.8 tok/s540 tok/s

OOM = out of memory at the listed quant + 8K context. The 24 GB cards can run Q5_K_M with Q8 KV cache but throughput drops 6–10% from the numbers above.

Step-by-step: get Qwen 3 32B running tonight

The fastest path on Linux or Windows with NVIDIA hardware:

  1. Install Ollama: curl -fsSL https://ollama.com/install.sh | sh (or grab the Windows installer).
  2. Pull the model: ollama pull qwen3:32b-instruct-q4_K_M. About 20 GB download.
  3. Run it: ollama run qwen3:32b-instruct-q4_K_M. First-token latency is dominated by prefill — a 256-token prompt should respond within 1–2 seconds on a 4090 or better.
  4. For programmatic use, hit http://localhost:11434/v1/chat/completions — it speaks the OpenAI Chat Completions API.

If you want more control (custom samplers, draft model for speculative decoding, custom KV cache type), use llama.cpp directly:

bash
./llama-server -m qwen3-32b-instruct-q4_k_m.gguf \
 -c 16384 -ngl 999 \
 -ctk q8_0 -ctv q8_0 \
 --host 0.0.0.0 --port 8080

For a Hugging Face Transformers + vLLM path, see the model cards on Hugging Face — vLLM's PagedAttention shines on the 5090 for multi-user concurrency but is overkill for single-user chat.

Common pitfalls

1. Running Q4_0 instead of Q4_K_M. Q4_0 is a legacy quantization with materially worse perplexity. Always pull the K-quant. The K-quants use per-channel scales and are roughly free in size while measurably better in quality.

2. Forgetting -ngl 999. If nvtop shows 0% GPU utilization during generation, you forgot to offload layers. With -ngl 999, llama.cpp puts all 65 layers on GPU. Default is 0 (CPU-only) and generation will be 1–3 tok/s, which feels broken.

3. Buying a 16 GB card and assuming you can offload "just a little to CPU." Hybrid CPU+GPU offload at this model size is brutal — token generation crashes to 4–8 tok/s because every layer touch hits the PCIe bus. The honest split is "load all on GPU, OR run a smaller model." 16 GB cards are for 14B and below.

4. Running on a PSU at the edge. A 5090 spike under load can hit 600+ W transient. We have seen 750 W PSUs trigger over-current protection on initial token generation. Use a 1000+ W ATX 3.0 PSU.

5. Old NVIDIA driver. Anything older than 550.x for Ada / 555.x for Blackwell will undercut throughput by 5–15% on the same model. Update drivers before you benchmark.

6. Treating context length as free. Doubling context doubles KV cache. Going from 8K → 32K on a 4090 with Q4_K_M turns "fits with 2 GB to spare" into "OOMs unless you Q8-quantize the cache."

When NOT to run Qwen 3 32B locally

There are workloads where the math just doesn't favor self-hosting:

  • Sub-RTX-3090 hardware. If you have a 12 GB or 16 GB card, run Qwen 3 14B or Qwen 3 8B locally and call a hosted Qwen 3 32B endpoint when you actually need the larger model. The break-even on hosted vs. local is a few hundred million tokens / month at typical 2026 hosted prices.
  • Strict latency requirements (<200 ms first-token). Local prefill on a 4090 at 1024 tokens is ~500 ms. A hosted Groq or Cerebras endpoint is sub-100 ms.
  • Batched throughput over many concurrent users. Single-card vLLM tops out around 200–300 concurrent users at small context. A hosted endpoint that fans out across hundreds of H100s will always win on $/Mtok for high-traffic apps.
  • You only need it occasionally. A 5090 idles at 25 W. Over a year that's ~$25 of electricity for the card alone, before you count the hours you actually used it. If your usage is ad hoc, pay-as-you-go remains rational.

Final shortlist

  • Best overall: RTX 5090 — only single-GPU path to Q6_K + 32K context, fastest by 50%+.
  • Best value: RTX 4090 used — 60% of the 5090's throughput at ~40% of the price.
  • Cheapest path to 24 GB: RTX 3090 (used, repad the memory) — entry to the 32B tier under $800.
  • AMD pick: RX 7900 XTX — only if you actively want to avoid NVIDIA.
  • Two-card answer: 2× RTX 3090 — best price/VRAM at 48 GB, runs Q8_0 in full.
  • No-fans / unified-memory path: M3 Ultra Mac Studio — quiet, huge context, slower per-token.

Skip anything below 24 GB. Skip mobile RTX 5090 laptops (their TGPs are throttled below 200 W and you give up 30–40% throughput). And skip the trap of "I'll save by going Q3_K_M on a 16 GB card" — the quality drop on a 32B model at Q3 is large enough that you'd be better off running Qwen 3 14B at Q5 on that same card.

Products mentioned

Products mentioned in this article

Live Amazon & eBay pricing, plus full specs and alternatives on each product page.

As an Amazon Associate, SpecPicks earns from qualifying purchases; we also earn on qualifying eBay purchases via the eBay Partner Network. Prices shown were last tracked at crawl time and may vary — check the listing for the current price.

Frequently asked questions

What is the minimum VRAM required to run Qwen 3 32B?
To run Qwen 3 32B at the community-standard q4_K_M quantization, you need approximately 22 GB of VRAM for weights, plus additional VRAM for the KV cache depending on context length. For lower quantizations like q3_K_M, the VRAM requirement drops to around 14 GB, but with a tradeoff in model quality.
Why is q4_K_M the recommended quantization for Qwen 3 32B?
q4_K_M is recommended because it offers a balance between memory efficiency and quality. It reduces VRAM usage by nearly half compared to fp16 while maintaining a minimal quality loss of 1-3% on benchmarks. This makes it the default choice for most users running Qwen 3 32B locally.
How does context length affect VRAM usage for Qwen 3 32B?
The KV cache grows linearly with context length, adding significant VRAM overhead. For example, at q4_K_M, a 4K-token context requires ~2.2 GB of additional VRAM, while a 128K-token context demands ~70.4 GB. This makes context length a critical factor in determining total VRAM requirements.
What is the most power-efficient GPU for running Qwen 3 32B?
The Apple M4 Max is the most power-efficient option, delivering approximately 12 tokens per second at a sustained power draw of 60W. This makes it about four times more efficient than high-end NVIDIA GPUs like the RTX 5090, which consumes 575W for similar performance.
Is multi-GPU setup beneficial for running Qwen 3 32B?
Multi-GPU setups are generally not recommended for Qwen 3 32B. A single GPU with sufficient VRAM outperforms two smaller GPUs connected via networking. The overhead and complexity of multi-GPU configurations often negate any potential performance gains for this model size.

Sources

— Mike Perry · Last verified 2026-08-18

Parts this article names

Amazon Associate — prices tracked 2026-09-14, may vary.

More guides & deep dives from the SpecPicks archive

Browse all articles & guides →

More buying guides from SpecPicks

Browse all buying guides →

Hardware benchmark data on SpecPicks

All benchmarks →