How to Deploy Qwen3.6 35B A3B Locally
Qwen3.6 35B A3B is an MoE that Qwen released in April 2026, with about 36B parameters in total but only 3B used per token, so it runs fast. A single 24GB card holds its 4-bit version, at about 135 tokens/s on an RTX 3090, more than three times what the same card does with a 27B dense model. It understands images and video, and when VRAM runs short, you can move some of the experts into system RAM.
Qwen3.6 35B A3B details
- Min VRAM at 4-bit24 GB · 8K
- Parameters36B
- Active params3B
- Max context256K
- Architecture
- MoE
- Experts offloaded
- 4 GB VRAM + 21 GB RAM
- License
- Apache-2.0
- Launch date
- Apr 16, 2026
- Vendor
- Alibaba
- Hugging Face repo
- Qwen/Qwen3.6-35B-A3B
- GGUF repo
- unsloth/Qwen3.6-35B-A3B-GGUF
- NVFP4 repo (Blackwell)
- nvidia/Qwen3.6-35B-A3B-NVFP4
- MLX repo (Apple)
- mlx-community/Qwen3.6-35B-A3B-4bit
- Ollama tag
- qwen3.6:35b-a3b
- Layers
- 40
- Hidden size
- 2,048
- KV heads
- 2
- Head dim
- 256
How much VRAM does Qwen3.6 35B A3B need for local deployment?
| Quantization | WeightsGB | 8K contextGB | 32K contextGB | 128K contextGB | 256K context (max)GB |
|---|---|---|---|---|---|
| 1-bit | 10GGUF | 11.2 | 11.7 | 13.8 | 16.4 |
| 2-bit | 12.3GGUF | 13.5 | 14 | 16.1 | 18.7 |
| 3-bit | 16.8GGUF | 18 | 18.5 | 20.6 | 23.2 |
| 4-bit | 22.1GGUF | 23.3 | 23.8 | 25.9 | 28.5 |
| 5-bit | 26.5GGUF | 27.7 | 28.2 | 30.3 | 32.9 |
| 8-bit | 36.9GGUF | 38.1 | 38.6 | 40.7 | 43.3 |
| BF16/FP16 | 69.4GGUF | 70.6 | 71.1 | 73.2 | 75.8 |
Full calculation rules are on the Methodology page.
Can a single GPU run Qwen3.6 35B A3B?
Yes, and it's fast. It uses only about 3B parameters for each token, so a 24GB card running 4-bit turns out about 135 tokens/s. The hard part is size, not speed: 4-bit sits right at the edge of 24GB, so 16GB cards can't hold it. On 16GB you either run 2-bit entirely on the card or keep 4-bit and move some of the experts to system RAM. The 32GB RTX 5090 can open the full 256K window. 128GB unified-memory machines handle it well too, still doing about 50 tokens/s at 8-bit, because each step reads so little data that their lower bandwidth hardly matters.
| Device | Price | Speed t/s | Max context |
|---|---|---|---|
| $37024 listings | 158.6 | 181K | |
| $86958 listings | 126.1 | 181K | |
| $89518 listings | 158.6 | 256K | |
| Radeon RX 7900 XTX24 GB | $1,25029 listings | 161.1 | 256K |
| $1,799107 listings | 160.1 | 256K | |
| $3,75868 listings | 163 | 256K | |
| Ryzen AI Max+ 395 128GBWhole system · 128 GB | $4,46420 listings | 96.6 | 256K |
| $4,89916 listings | 151.9 | 256K | |
| Mac Studio M5 Ultra 96GBWhole system · 96 GB | $7,27412 listings | 170.2 | 256K |
| MacBook Pro M5 Max 128GBWhole system · 128 GB | $7,54920 listings | 141.7 | 256K |
| $8,24022 listings | 100 | 256K | |
| $8,395123 listings | 181.6 | 256K | |
| $22,50011 listings | 181.6 | 256K |
| Device | Price | Speed t/s | Max context |
|---|---|---|---|
| $89518 listings | 133.5 | 256K | |
| Radeon RX 7900 XTX24 GB | $1,25029 listings | 136.7 | 123K |
| $1,799107 listings | 135.4 | 123K | |
| $3,75868 listings | 139 | 123K | |
| Ryzen AI Max+ 395 128GBWhole system · 128 GB | $4,46420 listings | 68.9 | 256K |
| $4,89916 listings | 125.4 | 256K | |
| Mac Studio M5 Ultra 96GBWhole system · 96 GB | $7,27412 listings | 148.3 | 256K |
| MacBook Pro M5 Max 128GBWhole system · 128 GB | $7,54920 listings | 113.7 | 256K |
| $8,24022 listings | 71.9 | 256K | |
| $8,395123 listings | 163.9 | 256K | |
| $22,50011 listings | 163.9 | 256K |
| Device | Price | Speed t/s | Max context |
|---|---|---|---|
| Ryzen AI Max+ 395 128GBWhole system · 128 GB | $4,46420 listings | 48.1 | 256K |
| $4,89916 listings | 99.3 | 256K | |
| Mac Studio M5 Ultra 96GBWhole system · 96 GB | $7,27412 listings | 124.1 | 256K |
| MacBook Pro M5 Max 128GBWhole system · 128 GB | $7,54920 listings | 87.6 | 256K |
| $8,24022 listings | 50.5 | 256K | |
| $22,50011 listings | 142.8 | 256K |
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 PC or server build do you need to run Qwen3.6 35B A3B locally?
To run 4-bit on a 16GB card, move some of the experts into system RAM: a 16GB Tesla V100 holds the experts from 26 of the 40 layers, with the rest in RAM, giving about 76 tokens/s on a dual-channel DDR4 desktop and about 96 on DDR5. At 8-bit, a used 8-channel DDR4 server with an RTX 3090 does about 84 tokens/s. In llama.cpp, --n-cpu-moe N puts the experts from the first N layers in system RAM, while --cpu-moe puts all of them there.
GeForce RTX 5070 + Desktop DDR5
Home PC2 × GeForce RTX 5070 + Desktop DDR5
Home PCTesla V100 32GB + Dual Xeon E5 DDR4
BudgetGeForce RTX 3090 + Single EPYC DDR4
Best valueGeForce RTX 5090 + Single EPYC DDR5
FlagshipDetailed calculation rules are on the Methodology page.
As an eBay Partner, VRAMGlass may be compensated if you buy through the eBay links on this page. The price you pay stays the same.
What to know before running Qwen3.6 35B A3B locally
Sampling parameters differ from the 27B
For general tasks in thinking mode, Qwen recommends
temperature1.0,top_p0.95,top_k20 andpresence_penalty1.5 (the 27B of the same generation uses 0 here); for coding,temperature0.6 andpresence_penalty0; in non-thinking mode, 0.7, 0.8 and 20, withpresence_penalty1.5.Which quantization to pick
It reads only 3B parameters per token, so the quant level affects its speed less than a dense model's, but affects its size just as much. On a 24GB card, use 4-bit (about 22.1 GB); on cards with 48GB or more, or unified-memory machines, go straight to 8-bit (about 36.9 GB), which still runs at about 99 tokens/s on an RTX A6000.
MTP adds another step of speed
llama.cpp now supports MTP speculative decoding, and the MTP GGUF takes only about 1 GB more. Unsloth says this model runs at about 240 tokens/s with MTP on an “RTX 6000,” without saying which generation of card or which quant; that's Unsloth's number, and this site's speeds don't include MTP. The Ollama tag is qwen3.6:35b-a3b.
Leave enough context for thinking
Qwen recommends leaving at least 128K of context to preserve thinking quality. On a 24GB card, 4-bit tops out at about 123K, slightly under that recommendation; to leave the full amount, drop to 3-bit (about 20.6 GB at 128K) or switch to a 32GB card.
Launch commands
Ollama
- Windows
- macOS
- Linux
ollama run qwen3.6:35b-a3bllama.cpp
- NVIDIA
- AMD
- Mac
- CPU
llama-server -hf unsloth/Qwen3.6-35B-A3B-GGUF:Q4_K_M -c 8192Short on VRAM? Add --cpu-moe to keep the routed experts in system RAM (about 21 GB needed).
llama-server -hf unsloth/Qwen3.6-35B-A3B-GGUF:Q4_K_M -c 8192 -ngl 99 \ --cpu-moe
vLLM
- Linux
- NVIDIA
- AMD
vllm serve Qwen/Qwen3.6-35B-A3BBlackwell GPUs (RTX 50 series, RTX PRO 6000, B200) run NVFP4 weights natively, at about 30% of the original size.
vllm serve nvidia/Qwen3.6-35B-A3B-NVFP4MLX
- Apple Silicon
Vision models run on mlx-vlm: on a Mac, pip install mlx-vlm first; this command downloads the MLX weights from Hugging Face and starts a server.
mlx_vlm.server --model mlx-community/Qwen3.6-35B-A3B-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 | |
| 32.8B | 32.8B | 19.8 GB | |
| 176B | 6B | 111.3 GB | |
| 2,446B | 95B | 1,310.9 GB |