VOOZH about

URL: https://willitrunai.com/can-run/exaone-4-32b-on-m4-max-36gb


Can EXAONE 4.0 32B run on MacBook Pro M4 Max 36GB?

BARELY — Tight on Memory

A74Great
Estimated from fit model

EXAONE 4.0 32B needs ~28.2 GB VRAM. MacBook Pro M4 Max 36GB has 25.9 GB. With Q4_K_M quantization, expect ~23 tok/s.

Runtime: llama.cppCapacity: OffloadBandwidth: 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.

Capabilities:

Select quantization to explore

Q4_K_M (Medium quality) — 28.2 GB, 22.9 tok/s, Very compromised (needs ~1.6 GB host RAM)
28.2 GB required25.9 GB available
109% VRAM needed

2.3 GB over capacity — needs offload or smaller quantization

Fit status

Very compromised (needs ~1.6 GB host RAM)

Decode

22.9 tok/s

TTFT

8441 ms

Safe context

7K

Memory

28.2 GB / 25.9 GB

Offload

10%

Memory breakdown

Weights19.5 GB
KV Cache3.9 GB
Runtime0.9 GB
Headroom3.9 GB

See how fast it feels

See how fast it feelsEXAONE 4.0 32B on MacBook Pro M4 Max 36GB
1st promptCold start — includes initialization
>Write a Python function to sort a list
Here's a Python function that sorts a list using quicksort: def quicksort(arr): if len(arr) <= 1: return arr pivot = arr[len(arr) // 2] left = [x for x in arr if x < pivot] middle = [x for x in arr if x == pivot] right = [x for x in arr if x > pivot] return quicksort(left) + middle + quicksort(right) # Example usage numbers = [3, 6, 8, 10, 1, 2, 1] print(quicksort(numbers)) # [1, 1, 2, 3, 6, 8, 10] The algorithm picks a pivot, partitions the list into smaller, equal, and larger elements, then recursively sorts each partition and concatenates the results.
2nd promptWarm — model ready, no init overhead
>Now add type hints and a docstring
def quicksort(arr: list[int]) -> list[int]: """Sort a list using the quicksort algorithm. Args: arr: List of integers to sort. Returns: A new sorted list. """ if len(arr) <= 1: return arr pivot = arr[len(arr) // 2] left = [x for x in arr if x < pivot] middle = [x for x in arr if x == pivot] right = [x for x in arr if x > pivot] return quicksort(left) + middle + quicksort(right) Added type hints for the input and return type, plus a Google-style docstring.
Estimated: 22.9 tok/s decode · 8.4s TTFT (warm) · 57 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 1.6 GB of extra host RAM just for the offloaded portion, before OS and other tools.

Performance by workload

WorkloadGradeFitDecodeTTFTContext
ChatARuns with offload (needs ~0.3 GB host RAM)25.7 tok/s4113 ms7K
CodingAVery compromised (needs ~1.6 GB host RAM)22.9 tok/s8441 ms7K
Agentic CodingFToo heavy19.4 tok/s14524 ms7K
ReasoningAVery compromised (needs ~1.6 GB host RAM)22.9 tok/s9975 ms7K
RAGFToo heavy19.4 tok/s18155 ms

Quantization options

How EXAONE 4.0 32B (32B params) fits at each quantization level on MacBook Pro M4 Max 36GB (25.9 GB usable).

QuantBitsVRAMQualityFit
Q2_K
2
12.5 GB
LowS85
Q3_K_S
3
15.7 GB
LowA85
NVFP4
4

Get started

Copy-paste commands to run EXAONE 4.0 32B on your machine.

Run

ollama run exaone-4:32b

Your hardware

More models your MacBook Pro M4 Max 36GB can run

ModelParamsGradeDecodeCapabilities
👁 Alibaba
Qwen 3.6 35B A3B
35BA28.5 tok/s
👁 Alibaba

Frequently asked questions

See all results for MacBook Pro M4 Max 36GBSee all hardware for EXAONE 4.0 32B
7K
17.9 GB
Medium
A84
Q4_K_MBest for your GPU
4
19.5 GB
MediumA84
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
Qwen 3.5 35B A3B
35B
A
35.1 tok/s

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.