Can I run Qwen 2.5 Coder 32B?
Qwen 2.5 Coder 32B by Alibaba needs around 32 GB of RAM at the recommended 4-bit quantization (19.9 GB download). Your hardware is checked below β instantly, nothing leaves your browser. Expect roughly ~18 tok/s on a Apple M-series Max.
Reading your hardware signalsβ¦
Real-world notes
Qwen 2.5 Coder 32B is Alibaba's purpose-built coding model, and it is the one people reach for when they want a local assistant that actually competes with hosted tools on real programming work. At 32.8B parameters it is not a casual download: a 4-bit quant lands around 19.9 GB, and you need at least 32 GB of RAM to load it. That rules out a 12 GB RTX 3060 entirely, where it simply does not fit. The realistic homes for it are a 24 GB card or an Apple Silicon Mac with plenty of unified memory.
In daily use it feels deliberate rather than snappy, and the hardware gap shows. On an RTX 4090 you can expect roughly 43 tokens per second at 4-bit, quick enough that code streams comfortably as you read. An M-series Max sits closer to 18 tokens per second, usable but noticeably more patient work, and a DDR5 CPU fallback at about 3 tokens per second is really only for overnight batch jobs. The 128K context is genuinely useful for feeding whole files, but it is not free: pushing to the full window drives total memory toward 51.6 GB, so keep working context modest unless you have the headroom.
Against DeepSeek R1 32B, which sits at the same 32.8B size, the split is about intent: R1 is a reasoning model that thinks out loud, while Qwen 2.5 Coder generally feels more direct and to-the-point on straight code generation and completion. Its standout trait is exactly that coding focus at a size you can still self-host on one good GPU. And the license is the easy part: Apache 2.0 means you can use it freely, including commercially and in production, with no provider-specific strings attached.
Specifications
Size by quantization
| Quantization | Bits/weight | Download | Min RAM | Quality |
|---|---|---|---|---|
| Q2_K | 3.35 | 13.7 GB | 24 GB | Noticeable loss |
| Q4_K_MRecommended | 4.85 | 19.9 GB | 32 GB | Recommended |
| Q5_K_M | 5.65 | 23.2 GB | 32 GB | High |
| Q8_0 | 8.5 | 34.8 GB | 48 GB | Near-original |
| F16 | 16 | 65.6 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 | ~20.9 GB |
| 8K tokens | ~2.0 GB | ~21.9 GB |
| 32K tokens | ~7.9 GB | ~27.8 GB |
| 128K tokens | ~31.7 GB | ~51.6 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 | ~43 tok/s |
| Apple M-series (base) | 100 GB/s | ~4 tok/s |
| Apple M-series Pro | 270 GB/s | ~12 tok/s |
| Apple M-series Max | 410 GB/s | ~18 tok/s |
| CPU only (dual-channel DDR5) | 60 GB/s | ~3 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 qwen2.5-coder:32bSources & downloads