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

YES — With Offload

C50Usable

○Estimated from fit model

Aya Expanse 32B needs ~26.7 GB VRAM. MacBook Pro M3 Pro 36GB has 25.9 GB. With Q4_K_M quantization, expect ~5 tok/s.

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

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.

Capabilities:

Select quantization to explore

Q4_K_M (Medium quality) — 26.7 GB, 5.7 tok/s, Runs with offload (needs ~0.6 GB host RAM)

26.7 GB required25.9 GB available

103% VRAM needed

0.8 GB over capacity — needs offload or smaller quantization

Fit status

Runs with offload (needs ~0.6 GB host RAM)

Decode

5.7 tok/s

TTFT

33837 ms

Safe context

Memory

26.7 GB / 25.9 GB

Memory breakdown

Weights19.5 GB

KV Cache2.4 GB

Runtime0.9 GB

Headroom3.9 GB

See how fast it feels

See how fast it feelsAya Expanse 32B on MacBook Pro M3 Pro 36GB
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: 5.7 tok/s decode · 33.8s TTFT (warm) · 14 tok/s prefill

What limits this setup

The model fits in shared memory, but shared-memory bandwidth is now the real limiter.

Fit does not mean dedicated-VRAM speed

Unified or shared memory can make a model technically fit, but sustained tokens per second may still trail a discrete high-bandwidth GPU with less total memory.

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

Prioritize bandwidth, not only capacity

If this workload feels slow, the next useful step is often a GPU tier with materially faster memory bandwidth rather than only a small bump in capacity.

Buy headroom, not only minimum fit

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

Performance by workload

Workload	Grade	Fit	Decode	TTFT	Context
Chat	C	Runs with offload	5.6 tok/s	18825 ms	8K
Coding	C	Runs with offload	5.3 tok/s	36798 ms	8K
Agentic Coding	D	Very compromised	4.6 tok/s	60744 ms	8K
Reasoning	C	Runs with offload	5.3 tok/s	43488 ms	8K
RAG	D	Very compromised	4.6 tok/s	75930 ms	8K