Will It Run AI

Can Aya Expanse 32B run on MacBook Pro M3 24GB?

YES — With Q2_K

D40Poor
Estimated from fit model

Aya Expanse 32B needs ~18.4 GB VRAM. MacBook Pro M3 24GB has 17.3 GB. With Q2_K quantization, expect ~5 tok/s.

Runtime: llama.cppCapacity: OffloadBandwidth: Very lowStack: StandardBottleneck: Host offload
Share:

Operating mode

Choose the run profile you care about

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.

Aya Expanse 32B at Q4_K_M needs 25.5 GB — too much for MacBook Pro M3 24GB (17.3 GB). Runs at Q2_K (18.4 GB) with low quality.
Capabilities:

Select quantization to explore

Q4_K_M (Medium quality) 25.5 GB, exceeds 17.3 GB available
25.5 GB required17.3 GB available
147% VRAM needed

8.2 GB over capacity — needs offload or smaller quantization

Fit status

Too heavy

Decode

2.3 tok/s

TTFT

85603 ms

Safe context

4K

Memory

25.5 GB / 17.3 GB

Offload

30%

Memory breakdown

Weights19.5 GB
KV Cache2.4 GB
Runtime0.9 GB
Headroom2.6 GB

See how fast it feels

With memory offload — actual speed may be lower
See how fast it feelsAya Expanse 32B on MacBook Pro M3 24GB
1st promptCold start — includes initialization
>What is local AI inference?
Local AI inference means running an AI language model directly on your own hardware — your laptop, desktop, or server — instead of sending requests to a remote cloud API. When you run inference locally the model weights are loaded into your GPU or unified memory. Each token you generate requires reading those weights from memory, so memory bandwidth is the main bottleneck for decode speed. Key benefits of running locally: - Full privacy: your prompts never leave your machine - No per-token cost or rate limits - Works offline once the model is downloaded - Latency depends only on your hardware
2nd promptWarm — model ready, no init overhead
>How much VRAM do I need?
It depends on the model size and quantization level. A rough rule of thumb: Model size Q4 (4-bit) Q8 (8-bit) FP16 7B params ~4.3 GB ~7.5 GB ~14 GB 13B params ~7.9 GB ~13.9 GB ~26 GB 70B params ~42.7 GB ~74.9 GB ~140 GB Most people use 4-bit quantization (Q4_K_M) which gives 90-95% of full quality at a fraction of the memory. A 24 GB GPU can comfortably run most 7B-13B models.
Estimated: 2.3 tok/s decode · 85.6s TTFT (warm) · 6 tok/s prefill

What limits this setup

It fits through host-memory offload, and offload is the main reason performance drops.

CPU or host-memory offload is active

About 10% of the working set spills out of accelerator memory, which usually hurts latency and sustained decode throughput.

Very little memory headroom

You can run the model, but there is not much room left for longer context, bigger batches, extra apps, or future model updates.

Shared-memory contention still exists

The OS, browser, and inference runtime all compete for the same physical memory pool, so real-world headroom is less forgiving than raw capacity suggests.

Best improvement path

Remove offload with more accelerator memory

Prioritize a GPU or unified-memory tier that fits the whole model natively. Removing offload usually helps more than small compute gains.

Buy headroom, not only minimum fit

A slightly larger memory tier gives you safer context growth and makes the recommendation more future-proof.

Increase host RAM if you keep offloading

This setup may need roughly 0.8 GB of extra host RAM just for the offloaded portion, before OS and other tools.

Performance by workload

WorkloadGradeFitDecodeTTFTContext
ChatFToo heavy2.2 tok/s47987 ms4K
CodingFToo heavy2.1 tok/s93093 ms4K
Agentic CodingFToo heavy2.0 tok/s140800 ms4K
ReasoningFToo heavy2.1 tok/s110019 ms4K
RAGFToo heavy2.0 tok/s176000 ms4K

Quantization options

How Aya Expanse 32B (32B params) fits at each quantization level on MacBook Pro M3 24GB (17.3 GB usable).

QuantBitsVRAMQualityFit
Q2_KBest for your GPU
2
12.5 GB
LowB56
Q3_K_S
3
15.7 GB
LowF0
NVFP4
4
17.9 GB
MediumF0
Q4_K_M
4
19.5 GB
MediumF0
Q5_K_M
5
23.0 GB
HighF0
Q6_K
6
26.2 GB
HighF0
Q8_0
8
34.2 GB
Very HighF0
F16
16
65.6 GB
MaximumF0

Get started

Copy-paste commands to run Aya Expanse 32B on your machine.

Run

ollama run aya-expanse:32b

Opciones de mejora

Hardware que ejecuta bien Aya Expanse 32B

Frequently asked questions

Can MacBook Pro M3 24GB run Aya Expanse 32B?

Yes, MacBook Pro M3 24GB can run Aya Expanse 32B at Q2_K quantization (Runs with offload (needs ~0.8 GB host RAM)). The recommended Q4_K_M requires 25.5 GB which exceeds available memory, but at Q2_K it needs only 18.4 GB. Expected decode speed: 4.5 tok/s.

How much VRAM does Aya Expanse 32B need?

Aya Expanse 32B (32B parameters) requires approximately 25.5 GB at Q4_K_M quantization. On MacBook Pro M3 24GB, it fits at Q2_K using 18.4 GB.

What is the best quantization for Aya Expanse 32B?

The recommended quantization is Q4_K_M, but on MacBook Pro M3 24GB the best fitting quantization is Q2_K, which uses 18.4 GB.

What speed will Aya Expanse 32B run at on MacBook Pro M3 24GB?

On MacBook Pro M3 24GB, Aya Expanse 32B achieves approximately 4.5 tokens per second decode speed with a time-to-first-token of 43068ms using Q2_K quantization.

Can MacBook Pro M3 24GB run Aya Expanse 32B for coding?

For coding workloads, Aya Expanse 32B on MacBook Pro M3 24GB receives a F grade with 2.1 tok/s and 4K context.

What context window can Aya Expanse 32B use on MacBook Pro M3 24GB?

On MacBook Pro M3 24GB, Aya Expanse 32B can safely use up to 8K tokens of context at Q2_K quantization. The model's official context limit is 8K, but available memory constrains the safe maximum.

What should I upgrade first if Aya Expanse 32B feels slow on MacBook Pro M3 24GB?

Remove offload with more accelerator memory. Prioritize a GPU or unified-memory tier that fits the whole model natively. Removing offload usually helps more than small compute gains.

Is unified memory on MacBook Pro M3 24GB as fast as VRAM for Aya Expanse 32B?

Not always. MacBook Pro M3 24GB 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.

See all results for MacBook Pro M3 24GBSee all hardware for Aya Expanse 32B
Embed this result

Paste this snippet into any page to show a live fit card.

<iframe src="https://willitrunai.com/embed/aya-expanse-32b-on-m3-24gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>

Preview: