Can I run Qwen 3.6 35B-A3B?
Qwen 3.6 35B-A3B by Alibaba needs around 32 GB of RAM at the recommended 4-bit quantization (21.2 GB download). Your hardware is checked below — instantly, nothing leaves your browser. Expect roughly ~192 tok/s on a Apple M-series Max.
Reading your hardware signals…
Real-world notes
Qwen 3.6 35B-A3B is a mixture-of-experts model, and that is the whole story of who it is for. It carries 35B total parameters but only activates 3B per token, so it runs at the speed of a tiny model while needing the memory of a big one. At a 4-bit quant the weights land around 21.2 GB, but the model still needs roughly 32 GB of RAM minimum to hold the full set of experts. That rules out a 12 GB card like the RTX 3060, where it does not fit. The natural homes are a 24 GB RTX 4090 or an Apple Silicon Mac with plenty of unified memory.
In daily use the active-3B math pays off: on a 4090 you can see around 471 tokens per second, and on an M-series Max around 192, which is faster than most dense models a third of this size. Even CPU inference on DDR5 manages about 28 tokens per second, usable for batch work. It handles chat, reasoning, coding, and vision, so it earns its keep as a single do-everything local model. The 256K context window is generous, but memory is the catch: filling just 128K already pushes total footprint to about 53.8 GB, so long-context work wants a 64 GB machine, not a 24 GB card.
Against the dense Command R 35B in its related lineup, this MoE generally feels much faster at the same nominal size, since you pay for 35B of memory but compute like a 3B. The tradeoff is the usual MoE one: a dense 35B can sometimes hold an edge on the hardest single-shot reasoning, though for most work the speed wins. Its standout trait is that speed-to-capability ratio plus native vision in one package. License is Apache 2.0, so you are free to use it commercially and in production with no provider strings attached.
Specifications
Size by quantization
| Quantization | Bits/weight | Download | Min RAM | Quality |
|---|---|---|---|---|
| Q2_K | 3.35 | 14.7 GB | 24 GB | Noticeable loss |
| Q4_K_MRecommended | 4.85 | 21.2 GB | 32 GB | Recommended |
| Q5_K_M | 5.65 | 24.7 GB | 48 GB | High |
| Q8_0 | 8.5 | 37.2 GB | 48 GB | Near-original |
| F16 | 16 | 70.0 GB | 96 GB | Original |
Sizes are estimates from parameter count × bits per weight; real GGUF builds vary slightly. · Data updated: 2026-06-11 · How we calculate these numbers →
Memory needed by context length
| Context | KV cache (est.) | Total memory (Q4) |
|---|---|---|
| 4K tokens | ~1.0 GB | ~22.2 GB |
| 8K tokens | ~2.0 GB | ~23.2 GB |
| 32K tokens | ~8.1 GB | ~29.3 GB |
| 128K tokens | ~32.6 GB | ~53.8 GB |
The KV cache grows with context length — a model that fits at 4K can run out of memory at 32K. Estimates assume an FP16 cache with grouped-query attention; actual usage varies by runtime.
Estimated speed by hardware
| Hardware | Bandwidth | ~Speed |
|---|---|---|
| NVIDIA RTX 3060 12GB | 360 GB/s | Won't fit in VRAM |
| NVIDIA RTX 4090 24GB | 1008 GB/s | ~471 tok/s |
| Apple M-series (base) | 100 GB/s | ~47 tok/s |
| Apple M-series Pro | 270 GB/s | ~126 tok/s |
| Apple M-series Max | 410 GB/s | ~192 tok/s |
| CPU only (dual-channel DDR5) | 60 GB/s | ~28 tok/s |
Token generation is memory-bandwidth bound: tok/s ≈ bandwidth × 0.85 ÷ model size at Q4. Real-world numbers vary by runtime and context length.
Run it locally
The easiest path is Ollama — one command and you're chatting:
ollama run qwen3.6:35bSources & downloads