How to Deploy Qwen3 32B Locally
Qwen3 32B is the largest dense model in the April 2025 Qwen3 lineup, with both thinking and non-thinking modes. A 24GB card can hold its 4-bit version (about 23 GB at 8K), but context is heavy on VRAM: on an RTX 3090 it only reaches about 18K, which fills up as soon as thinking runs a little long. For a new setup, we recommend switching to Qwen3.8 27B: it also fits on one 24GB card, but its context goes up to about 122K.
Qwen3 32B details
- Min VRAM at 4-bit24 GB · 8K
- Parameters32.8B
- Max context40K
- Architecture
- Dense
- License
- Apache-2.0
- Launch date
- Apr 27, 2025
- Vendor
- Alibaba
- Hugging Face repo
- Qwen/Qwen3-32B
- GGUF repo
- Qwen/Qwen3-32B-GGUF
- NVFP4 repo (Blackwell)
- nvidia/Qwen3-32B-NVFP4
- MLX repo (Apple)
- Qwen/Qwen3-32B-MLX-4bit
- Ollama tag
- qwen3:32b
- Layers
- 64
- Hidden size
- 5,120
- KV heads
- 8
- Head dim
- 128
How much VRAM does Qwen3 32B need for local deployment?
| Quantization | WeightsGB | 8K contextGB | 32K contextGB | 40K context (max)GB |
|---|---|---|---|---|
| 1-bit | 8.3GGUF | 11.5 | 18 | 20.1 |
| 2-bit | 12.8GGUF | 16 | 22.5 | 24.6 |
| 3-bit | 16.4GGUF | 19.6 | 26.1 | 28.2 |
| 4-bit | 19.8GGUF | 23 | 29.5 | 31.6 |
| 5-bit | 23.2GGUF | 26.4 | 32.9 | 35 |
| 8-bit | 34.8GGUF | 38 | 44.5 | 46.6 |
| BF16/FP16 | 65.5GGUF | 68.7 | 75.2 | 77.3 |
Full calculation rules are on the Methodology page.
Can a single GPU run Qwen3 32B?
Yes, a single 24GB card runs 4-bit, but context is the catch. 4-bit with 8K of context takes about 23 GB, which leaves an RTX 3090, 4090 or RX 7900 XTX room for only about 18K. Every layer keeps its own copy of the full context, so memory use climbs quickly as the window grows, and one long stretch of reasoning in thinking mode can eat what's left. To use the full 40K window you need the 32GB RTX 5090, which runs 4-bit at about 60 tokens/s. 16GB cards are stuck at 2-bit with a cramped window, so we'd skip them. For a new setup, Qwen3.8 27B on the same 24GB card leaves far more room for context.
| Device | Price | Speed t/s | Max context |
|---|---|---|---|
| $37024 listings | 46.6 | 12K | |
| $86958 listings | 24 | 12K | |
| $89518 listings | 46.6 | 40K | |
| Radeon RX 7900 XTX24 GB | $1,25029 listings | 49.5 | 40K |
| $1,799107 listings | 48.3 | 40K | |
| $3,75868 listings | 51.7 | 40K | |
| Ryzen AI Max+ 395 128GBWhole system · 128 GB | $4,46420 listings | 13.9 | 40K |
| $4,89916 listings | 40.1 | 40K | |
| Mac Studio M5 Ultra 96GBWhole system · 96 GB | $7,27412 listings | 62.1 | 40K |
| MacBook Pro M5 Max 128GBWhole system · 128 GB | $7,54920 listings | 32.4 | 40K |
| $8,24022 listings | 14.8 | 40K | |
| $8,395123 listings | 87.1 | 40K | |
| $22,50011 listings | 87.1 | 40K |
| Device | Price | Speed t/s | Max context |
|---|---|---|---|
| $89518 listings | 31.6 | 40K | |
| Radeon RX 7900 XTX24 GB | $1,25029 listings | 33.6 | 18K |
| $1,799107 listings | 32.8 | 18K | |
| $3,75868 listings | 35.2 | 18K | |
| Ryzen AI Max+ 395 128GBWhole system · 128 GB | $4,46420 listings | 9.3 | 40K |
| $4,89916 listings | 27.2 | 40K | |
| Mac Studio M5 Ultra 96GBWhole system · 96 GB | $7,27412 listings | 42.5 | 40K |
| MacBook Pro M5 Max 128GBWhole system · 128 GB | $7,54920 listings | 21.9 | 40K |
| $8,24022 listings | 9.9 | 40K | |
| $8,395123 listings | 60.3 | 40K | |
| $22,50011 listings | 60.3 | 40K |
| Device | Price | Speed t/s | Max context |
|---|---|---|---|
| Ryzen AI Max+ 395 128GBWhole system · 128 GB | $4,46420 listings | 5.4 | 40K |
| $4,89916 listings | 16.1 | 40K | |
| Mac Studio M5 Ultra 96GBWhole system · 96 GB | $7,27412 listings | 25.3 | 40K |
| MacBook Pro M5 Max 128GBWhole system · 128 GB | $7,54920 listings | 12.9 | 40K |
| $8,24022 listings | 5.8 | 40K | |
| $22,50011 listings | 36.4 | 40K |
Only common GPUs and systems are listed, one set for models under 50B and another for larger ones, sorted by price from low to high.
What to know before running Qwen3 32B locally
Why context is so heavy on VRAM
All 64 of its layers store a full context cache, so every extra 1K of context adds about 0.27 GB: at 4-bit, going from 8K to 32K takes VRAM from about 23.0 GB to 29.5 GB, and the full 40K needs 31.6 GB. The 27B models from Qwen3.5 onward switched to having only 1 in every 4 layers see the full context, so going from 8K to 32K adds only about 1.6 GB. That's why the newer models can open long context on a 24GB card.
Trade-offs on a 24GB card
Thinking takes up context too, so for everyday Q&A, add /no_think to your prompt to turn thinking off and save a good amount of room. If you really need more, drop to 3-bit (about 19.6 GB at 8K); by this site's formula, a 24GB card then reaches about 30K.
Leave enough output length for thinking
Qwen recommends an output length of 32,768 tokens for most problems and 38,912 for competition-level ones; at 4-bit, that takes an RTX 5090 or a 48GB card to fit. Sampling parameters are the same as for Qwen3 8B:
temperature0.6,top_p0.95 andtop_k20 in thinking mode, and 0.7, 0.8 and 20 in non-thinking mode.Which framework to use
Qwen's official repository provides GGUFs, and the Ollama tag is qwen3:32b; vLLM needs 0.8.5 or later and SGLang 0.4.6.post1 or later.
Launch commands
Ollama
- Windows
- macOS
- Linux
ollama run qwen3:32bllama.cpp
- NVIDIA
- AMD
- Mac
- CPU
llama-server -hf Qwen/Qwen3-32B-GGUF:Q4_K_M -c 8192
vLLM
- Linux
- NVIDIA
- AMD
vllm serve Qwen/Qwen3-32BBlackwell GPUs (RTX 50 series, RTX PRO 6000, B200) run NVFP4 weights natively, at about 30% of the original size.
vllm serve nvidia/Qwen3-32B-NVFP4MLX
- Apple Silicon
On a Mac, pip install mlx-lm first; this command downloads the MLX weights from Hugging Face and starts an OpenAI-compatible server.
mlx_lm.server --model Qwen/Qwen3-32B-MLX-4bitFile names follow that week's model-library snapshot; the definitions are in the methodology. Methodology
Other models in the Qwen family
| Model | Total params | Active params | 4-bit size |
|---|---|---|---|
| 8.2B | 8.2B | 5 GB | |
| 9.7B | 9.7B | 5.7 GB | |
| 27.8B | 27.8B | 16.8 GB | |
| 27.8B | 27.8B | 16.5 GB | |
| 36B | 3B | 22.1 GB | |
| 176B | 6B | 111.3 GB | |
| 2,446B | 95B | 1,310.9 GB |