Can I run Qwen 3.5 27B?
Qwen 3.5 27B by Alibaba needs around 24 GB of RAM at the recommended 4-bit quantization (16.4 GB download). Your hardware is checked below β instantly, nothing leaves your browser. Expect roughly ~21 tok/s on a Apple M-series Max.
Reading your hardware signalsβ¦
Real-world notes
Qwen 3.5 27B is the model you reach for when an 8B feels too thin and you have real hardware to spend. It is a dense 27B that handles chat, reasoning, coding, and vision, so it doubles as a local workhorse rather than a single-trick assistant. The footprint is the catch: at 4-bit it lands around 16.4 GB, and you want at least 24 GB of RAM to load it cleanly. That rules out a 12 GB card like an RTX 3060, where it simply does not fit, and points you at a 24 GB GPU or an Apple Silicon Mac with generous unified memory.
On an RTX 4090 you can expect around 52 tokens per second at 4-bit, which streams faster than you read and stays comfortable for interactive work. On an M-series Max it settles near 21 tokens per second, still fine for chat and coding but slower on long generations; pure CPU on DDR5 drops to roughly 3 tokens per second, which is patience territory. The 256K context is the headline number, but treat it as a ceiling: at 128K the total memory climbs to about 45.4 GB, so on a 24 GB card keep working context well below the maximum.
The natural comparison is Gemma 3 27B, the other open-weight 27B with vision in this size class. Gemma tends to be the safer pick if you are mainly after polished chat and image understanding, while Qwen 3.5 27B generally leans stronger on coding and structured reasoning, which is where its standout value sits for developers. The big practical win is licensing: it ships under Apache 2.0, so you can use it commercially and in production with no provider-specific strings attached, unlike the open-weight terms that come with Gemma.
Specifications
Size by quantization
| Quantization | Bits/weight | Download | Min RAM | Quality |
|---|---|---|---|---|
| Q2_K | 3.35 | 11.3 GB | 16 GB | Noticeable loss |
| Q4_K_MRecommended | 4.85 | 16.4 GB | 24 GB | Recommended |
| Q5_K_M | 5.65 | 19.1 GB | 32 GB | High |
| Q8_0 | 8.5 | 28.7 GB | 48 GB | Near-original |
| F16 | 16 | 54.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 | ~0.9 GB | ~17.3 GB |
| 8K tokens | ~1.8 GB | ~18.2 GB |
| 32K tokens | ~7.3 GB | ~23.7 GB |
| 128K tokens | ~29.0 GB | ~45.4 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 | ~52 tok/s |
| Apple M-series (base) | 100 GB/s | ~5 tok/s |
| Apple M-series Pro | 270 GB/s | ~14 tok/s |
| Apple M-series Max | 410 GB/s | ~21 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 qwen3.5:27bSources & downloads