OPEN WEIGHTS AVAILABLEUPDATED JUL 19, 2026

Qwen3.6 VRAM requirements: 27B vs 35B-A3B

Short answer: use a 24GB GPU for Qwen3.6-27B Q4, or 32GB for a comfortable Qwen3.6-35B-A3B Q4 setup. A 16GB GPU can run either with a smaller quant or CPU offload, but it is not a clean full-GPU Q4 tier.

ANSWER BY HARDWARE
16GB GPU
Offload territory
27B Q3 is slightly over our safe full-offload budget. Use partial CPU offload with 32GB+ system RAM; 35B-A3B can keep experts in RAM.
24GB GPU
Best-value tier
27B Q4_K_M fits fully (~18.5GB). For 35B-A3B, use IQ4_XS for headroom; Q4_K_M is too close to the limit (~23.9GB).
32GB GPU
Both run well
27B Q6_K or 35B-A3B Q5_K_M fits with working headroom at short context. This is the comfortable single-GPU tier.
Apple Silicon
32GB minimum; 48GB better
32GB unified memory is a practical 27B Q4 starting point. Choose 48GB+ for 35B-A3B Q4, larger context, and normal macOS headroom.

Estimates, not benchmarks · 4K text context · working set includes loaded weights, architecture-aware KV cache and runtime · recommended tiers include 1.5GB allocation headroom

See every quant ↓How to run locally ↓27B or 35B-A3B? ↓

Which Qwen3.6 should you download?

Choose 27B when

Qwen 3.6 27B

You want dense-model consistency, vision/coding quality, and have a 24GB GPU or 32GB+ unified memory.

Q4_K_M · 16.8GB download · ~18.5GB working set
Choose 35B-A3B when

Qwen 3.6 35B-A3B

You value faster generation, coding agents, or need expert offload to system RAM. Prefer 32GB VRAM or 48GB+ unified memory.

Q4_K_M · 22.1GB download · ~23.9GB working set

Qwen3.6 download and memory by quant

Download size is not VRAM required. The working-set estimate adds loaded-weight overhead, the 4K text cache, and runtime memory; the safer tier also leaves 1.5GB for allocations. Vision inputs and longer context need more.

Qwen 3.6 27B

QuantDownloadEst. working set @4KSafer hardware tier
Q3_K_M13.6 GB~15.1 GB24 GB
IQ4_XS15.4 GB~17 GB24 GB
Q4_015.8 GB~17.4 GB24 GB
Q4_K_S15.9 GB~17.5 GB24 GB
Q4_K_M16.8 GB~18.5 GB24 GB
Q5_K_M19.5 GB~21.3 GB24 GB
Q6_K22.5 GB~24.5 GB32 GB
Q8_028.6 GB~30.9 GB48 GB

Qwen 3.6 35B-A3B

QuantDownloadEst. working set @4KSafer hardware tier
Q3_K_M16.6 GB~18.1 GB24 GB
IQ4_XS17.7 GB~19.3 GB24 GB
Q4_K_S20.9 GB~22.6 GB32 GB
MXFP421.7 GB~23.5 GB32 GB
Q4_K_M22.1 GB~23.9 GB32 GB
Q5_K_M26.5 GB~28.5 GB32 GB
Q6_K29.3 GB~31.4 GB48 GB
Q8_036.9 GB~39.4 GB48 GB

Best Qwen3.6 quant for your GPU

Largest tracked quant that fits at 4K text context while preserving 1.5GB headroom. “Offload” means the model can still run with enough system RAM, but not entirely in VRAM.

GPU VRAMQwen3.6-27BQwen3.6-35B-A3BSystem RAM guidance
8 GBCPU offloadExpert/CPU offload32–64GB RAM
12 GBCPU offloadExpert/CPU offload32–64GB RAM
16 GBCPU offloadExpert/CPU offload32–64GB RAM
24 GBQ5_K_MIQ4_XS32GB minimum; 64GB useful
32 GBQ6_KQ5_K_M32GB+ RAM
48 GBQ8_0Q8_032GB+ RAM
64 GBQ8_0Q8_032GB+ RAM
80 GBQ8_0Q8_032GB+ RAM

How context length changes memory

Qwen3.6 is not a conventional all-attention Transformer: three linear-attention layers are followed by one full-attention layer. The estimates below count the token-growing KV cache only on those full-attention layers, based on the official model configs. Runtime, cache precision, vision input and implementation still change real usage.

Context27B cache27B total (Q4_K_M)35B-A3B cache35B-A3B total (Q4_K_M)
4K~0.3 GB~18.5 GB~0.1 GB~23.9 GB
32K~2 GB~20.2 GB~0.6 GB~24.4 GB
128K~8 GB~26.2 GB~2.5 GB~26.3 GB
256K~16 GB~34.2 GB~5 GB~28.8 GB

Sources: official Qwen3.6 model configs and weights. These remain planning estimates—not measured peak allocation.

How to run Qwen3.6 locally

Pick the runtime that matches your hardware. Start at 4K or 8K context, confirm the model is stable, then increase context—advertised maximum context is not a sensible starting allocation.

RuntimeBest forRecommended path
llama.cppNVIDIA, AMD, CPU offloadDownload a trusted GGUF, start with -c 4096, and tune GPU layers to your VRAM.
LM StudioWindows/macOS GUIChoose the quant from the tables above; verify estimated memory before loading.
MLXApple SiliconUse an MLX conversion and leave macOS several GB of unified-memory headroom.
Transformers / vLLMServers and full precisionUse the official checkpoint; FP8/BF16 typically requires multi-GPU or data-center memory.

Official resources: Qwen3.6 repository, 27B weights, and 35B-A3B weights.

Can a phone run Qwen3.6?

Not usefully at the recommended Q4 quant. Three 24GB Android configurations in our database can memory-fit some smaller 27B quants, but estimated generation is below 3 tokens/s and the recommended Q4_K_M working set exceeds the usable-memory budget. Treat Qwen3.6 as a desktop or high-memory Mac model.

See the per-phone edge-case calculations →

Qwen3.6 FAQ

How much VRAM does Qwen3.6-27B need?

The Q4_K_M file is 16.8GB and its estimated 4K text working set is ~18.5GB. A 24GB GPU is the practical recommendation for full GPU offload with useful headroom. A 16GB GPU needs a smaller quant or partial CPU offload.

How much VRAM does Qwen3.6-35B-A3B need?

The Q4_K_M file is 22.1GB and its estimated 4K text working set is ~23.9GB. It can technically sit near a 24GB limit, but 32GB is safer. On smaller GPUs, llama.cpp can keep experts in system RAM; the full model still needs to exist across VRAM and RAM.

Can Qwen3.6 run on a 16GB GPU?

Yes, with compromises. Qwen3.6-27B Q3_K_M has a 13.6GB file but our estimated working set plus safety margin exceeds 16GB. Use a shorter context and partial CPU offload with 32GB+ system RAM. The MoE 35B-A3B is often the better offload candidate because only about 3B parameters are active per token.

Which is better: Qwen3.6 27B or 35B-A3B?

Choose 27B for predictable dense-model behavior and quality per stored GB. Choose 35B-A3B for faster local decoding, coding agents, and better tolerance of expert offload. On 24GB, 27B Q4_K_M is the simpler fit; on 32GB+, both are strong options.

How much system RAM do I need when the model does not fit in VRAM?

Use at least 32GB system RAM for a 16GB GPU setup and preferably 64GB when running Qwen3.6-35B-A3B or long context. CPU offload needs enough RAM for the portion outside VRAM plus the OS, runtime, cache, and file mapping.

Can a phone run Qwen3.6 locally?

A few 24GB Android configurations can technically load low-bit 27B quants, but estimated speed is below a comfortable chat threshold. No phone we track fits the recommended 27B Q4_K_M working set. Qwen3.6 is a desktop, workstation, or high-memory Mac model in practice.

NEXT RELEASE TRACKER
Qwen3.8 is not available locally yet. Follow the verified release, weights and VRAM tracker →