Aya Expanse 32B needs ~24.6 GB but MacBook Air M2 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.1 GB over capacity — needs offload or smaller quantization
Fit status
Too heavy
Decode
2.0 tok/s
TTFT
96800 ms
Safe context
4K
Memory
24.6 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 24.6 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 | 2.0 tok/s | 52800 ms | 4K |
| Coding | F | Too heavy | 2.0 tok/s | 96800 ms | 4K |
| Agentic Coding | F | Too heavy | 2.0 tok/s | 140800 ms | 4K |
| Reasoning | F | Too heavy | 2.0 tok/s | 114400 ms | 4K |
| RAG | F | Too heavy | 2.0 tok/s | 176000 ms | 4K |
How Aya Expanse 32B (32B params) fits at each quantization level on MacBook Air M2 16GB (11.5 GB usable).
| Quant | Bits | VRAM | Quality | Fit |
|---|---|---|---|---|
Q2_K | 2 | 12.5 GB | Low | F0 |
Q3_K_S | 3 | 15.7 GB | Low | F0 |
NVFP4 | 4 | 17.9 GB | Medium | F0 |
Q4_K_M | 4 | 19.5 GB | Medium | F0 |
Q5_K_M | 5 | 23.0 GB | High | F0 |
Q6_K | 6 | 26.2 GB | High | F0 |
Q8_0 | 8 | 34.2 GB | Very High | F0 |
F16 | 16 | 65.6 GB | Maximum | F0 |
アップグレードオプション
Makes the model fit on the accelerator instead of staying completely out of reach.
Raises estimated decode speed by about 250%.
〜$799 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.
〜$1,099 MSRP
Makes the model fit on the accelerator instead of staying completely out of reach.
Raises estimated decode speed by about 250%.
〜$1,099 MSRP
NVIDIA A100 40GB最大の飛躍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.
〜$10,000 MSRP
No, Aya Expanse 32B requires more memory than MacBook Air M2 16GB provides.
Aya Expanse 32B (32B parameters) requires approximately 24.6 GB of memory with Q4_K_M quantization.
The recommended quantization for Aya Expanse 32B is Q4_K_M, which balances quality and memory efficiency.
On MacBook Air M2 16GB, Aya Expanse 32B achieves approximately 2.0 tokens per second decode speed with a time-to-first-token of 96800ms using Q4_K_M quantization.
For coding workloads, Aya Expanse 32B on MacBook Air M2 16GB receives a F grade with 2.0 tok/s and 4K context.
On MacBook Air M2 16GB, Aya Expanse 32B can safely use up to 4K tokens of context. The model's official context limit is 8K, 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 Air M2 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/aya-expanse-32b-on-m2-air-16gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>
Preview:
