Can I run Qwen3 Coder Next 80B-A3B?
Qwen3 Coder Next 80B-A3B by Alibaba needs around 64 GB of RAM at the recommended 4-bit quantization (48.5 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
Qwen3 Coder Next 80B-A3B is a coding specialist built as a Mixture-of-Experts, and that architecture is the whole story. It has 80B total parameters but only activates 3B per token, so it runs much faster than its size suggests while still needing memory for the full model. At 4-bit it lands around 48.5 GB, which rules out every consumer GPU: it does not fit on a 24 GB RTX 4090, let alone a 12 GB 3060. The realistic home for it is an Apple Silicon Mac with plenty of unified memory, or a workstation with 64 GB or more of system RAM. Plan around the minimum 64 GB figure, not the active 3B.
In daily use the MoE design pays off. On an Apple M Max it streams at roughly 192 tokens per second, which feels instant for code completion and refactoring, and even pure CPU inference on DDR5 manages about 28 tokens per second, slow but genuinely usable for a model this large. The 256K context window is the headline feature for working across whole repositories, but memory is the catch: at 128K context the total footprint climbs to about 95.8 GB. Keep that in mind before you load a massive codebase, because the KV cache, not the weights, is what will push you over the edge on a 64 GB machine.
Against the dense alternatives in its weight class, like Llama 3.1 70B, this model generally trades raw breadth for coding focus and speed: the MoE routing means it answers faster than a 70B dense model while specialising in code rather than general chat, where the smaller Qwen 3 chat variants are a better fit. Its standout trait is that speed-to-size ratio, getting near-instant generation from an 80B-class model. And the practical bonus is the license: Apache 2.0, so you can use it freely in commercial and production work with no provider-specific restrictions to read through first.
Specifications
Size by quantization
| Quantization | Bits/weight | Download | Min RAM | Quality |
|---|---|---|---|---|
| Q2_K | 3.35 | 33.5 GB | 48 GB | Noticeable loss |
| Q4_K_MRecommended | 4.85 | 48.5 GB | 64 GB | Recommended |
| Q5_K_M | 5.65 | 56.5 GB | 96 GB | High |
| Q8_0 | 8.5 | 85.0 GB | 128 GB | Near-original |
| F16 | 16 | 160.0 GB | 256 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.5 GB | ~50.0 GB |
| 8K tokens | ~3.0 GB | ~51.5 GB |
| 32K tokens | ~11.8 GB | ~60.3 GB |
| 128K tokens | ~47.3 GB | ~95.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 | Won't fit in VRAM |
| 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-coder-next