Makes the model fit on the accelerator instead of staying completely out of reach.
Removes host-memory offload, which is usually the single biggest latency and throughput win.
ca. $1,099 MSRP
Qwen 3.5 35B A3B needs ~25.3 GB but MacBook Pro M1 Pro 16GB only has 11.5 GB. Try a smaller quantization or lighter model.
Operating mode
Interactive favors responsiveness, while light API and scale-out lean harder on serving readiness. The fit stays the same, but the recommendation lens changes.
Current mode
Balanced
Balanced for general local use. Keeps the ranking neutral across personal and serving workflows.
Select quantization to explore
13.8 GB over capacity — needs offload or smaller quantization
Fit status
Too heavy
Decode
11.6 tok/s
TTFT
16746 ms
Safe context
4K
Memory
25.3 GB / 11.5 GB
Offload
50%
Usable shared or unified memory is the main blocker for this model.
Not enough usable memory
The model needs 25.3 GB, but this setup only exposes 11.5 GB of usable shared or unified memory.
Move to a larger memory pool
A larger unified-memory SKU or a discrete high-bandwidth GPU is the cleanest way to make this model practical.
| Workload | Grade | Fit | Decode | TTFT | Context |
|---|---|---|---|---|---|
| Chat | F | Too heavy | 11.6 tok/s | 9134 ms | 4K |
| Coding | F | Too heavy | 11.6 tok/s | 16746 ms | 4K |
| Agentic Coding | F | Too heavy | 11.6 tok/s | 24357 ms | 4K |
| Reasoning | F | Too heavy | 11.6 tok/s | 19790 ms | 4K |
| RAG | F | Too heavy | 11.6 tok/s | 30447 ms | 4K |
How Qwen 3.5 35B A3B (35B params) fits at each quantization level on MacBook Pro M1 Pro 16GB (11.5 GB usable).
| Quant | Bits | VRAM | Quality | Fit |
|---|---|---|---|---|
Q2_K | 2 | 13.7 GB | Low | F0 |
Q3_K_S | 3 | 17.2 GB | Low | F0 |
NVFP4 | 4 | 19.6 GB | Medium | F0 |
Q4_K_M | 4 | 21.3 GB | Medium | F0 |
Q5_K_M | 5 | 25.2 GB | High | F0 |
Q6_K | 6 | 28.7 GB | High | F0 |
Q8_0 | 8 | 37.5 GB | Very High | F0 |
F16 | 16 | 71.8 GB | Maximum | F0 |
Upgrade-Optionen
Makes the model fit on the accelerator instead of staying completely out of reach.
Removes host-memory offload, which is usually the single biggest latency and throughput win.
ca. $1,099 MSRP
Makes the model fit on the accelerator instead of staying completely out of reach.
Removes host-memory offload, which is usually the single biggest latency and throughput win.
ca. $1,599 MSRP
Makes the model fit on the accelerator instead of staying completely out of reach.
Removes host-memory offload, which is usually the single biggest latency and throughput win.
ca. $2,499 MSRP
No, Qwen 3.5 35B A3B requires more memory than MacBook Pro M1 Pro 16GB provides.
Qwen 3.5 35B A3B (35B parameters) requires approximately 25.3 GB of memory with Q4_K_M quantization.
The recommended quantization for Qwen 3.5 35B A3B is Q4_K_M, which balances quality and memory efficiency.
On MacBook Pro M1 Pro 16GB, Qwen 3.5 35B A3B achieves approximately 11.6 tokens per second decode speed with a time-to-first-token of 16746ms using Q4_K_M quantization.
For coding workloads, Qwen 3.5 35B A3B on MacBook Pro M1 Pro 16GB receives a F grade with 11.6 tok/s and 4K context.
On MacBook Pro M1 Pro 16GB, Qwen 3.5 35B A3B can safely use up to 4K tokens of context. The model's official context limit is 131K, but available memory constrains the safe maximum.
Move to a larger memory pool. A larger unified-memory SKU or a discrete high-bandwidth GPU is the cleanest way to make this model practical.
Not always. MacBook Pro M1 Pro 16GB can often fit larger models thanks to unified memory, but a discrete GPU with dedicated high-bandwidth VRAM may still decode faster once the model fits. For this combination, the important distinction is capacity versus sustained throughput.
Paste this snippet into any page to show a live fit card.
<iframe src="https://willitrunai.com/embed/qwen-3.5-35b-a3b-on-m1-pro-16gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>
Preview: