Can Codestral 22B run on MacBook Pro M2 Max 96GB?

YES — Runs Great

B55Good

Estimated from fit model

Codestral 22B needs ~27.1 GB VRAM. MacBook Pro M2 Max 96GB has 69.1 GB. With Q4_K_M quantization, expect ~19 tok/s.

Runtime: llama.cppCapacity: RoomyBandwidth: LowStack: StandardBottleneck: Balanced

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) — 27.1 GB, 18.6 tok/s, Runs well

27.1 GB required69.1 GB available

39% VRAM used

Fit status

Runs well

Decode

18.6 tok/s

TTFT

10417 ms

Safe context

33K

Memory

27.1 GB / 69.1 GB

Memory breakdown

Weights13.4 GB

KV Cache2.4 GB

Runtime0.9 GB

Headroom10.4 GB

See how fast it feels

See how fast it feelsCodestral 22B on MacBook Pro M2 Max 96GB
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: 18.6 tok/s decode · 10.4s TTFT (warm) · 47 tok/s prefill

What limits this setup

This setup is broadly balanced for this model.

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

Performance by workload

Workload	Grade	Fit	Decode	TTFT	Context
Chat	C	Runs well	18.6 tok/s	5682 ms	33K
Coding	B	Runs well	18.6 tok/s	10417 ms	33K
Agentic Coding	B	Runs well	18.6 tok/s	15153 ms	33K
Reasoning	B	Runs well	18.6 tok/s	12312 ms	33K
RAG	B	Runs well	18.6 tok/s	18941 ms	33K

Quantization options

How Codestral 22B (22B params) fits at each quantization level on MacBook Pro M2 Max 96GB (69.1 GB usable).

Quant	Bits	VRAM	Quality	Fit
Q2_K	2	8.6 GB	Low	C51
Q3_K_S	3	10.8 GB	Low	C51
NVFP4	4	12.3 GB	Medium	C51
Q4_K_M	4	13.4 GB	Medium	C52
Q5_K_M	5	15.8 GB	High	C52
Q6_K	6	18.0 GB	High	C52
Q8_0	8	23.5 GB	Very High	C54
F16Best for your GPU	16	45.1 GB	Maximum	B58

Get started

Copy-paste commands to run Codestral 22B on your machine.

Run

ollama run codestral

Upgrade options

Hardware that runs Codestral 22B well

Mac Studio M2 Ultra 128GBBudget pick

128 GB Unified (+32)800 GB/s (+400)

Raises estimated decode speed by about 100%.37.2 tok/s decode

Raises estimated decode speed by about 100%.

Adds memory headroom for longer context windows and future model growth.

~$3,999 MSRP

Mac Studio M1 Ultra 128GBBest value

128 GB Unified (+32)800 GB/s (+400)

Raises estimated decode speed by about 89%.35.2 tok/s decode

Raises estimated decode speed by about 89%.

Adds memory headroom for longer context windows and future model growth.

~$3,999 MSRP

MacBook Pro M4 Max 128GBApple upgrade

128 GB Unified (+32)546 GB/s (+146)

Raises estimated decode speed by about 101%.37.4 tok/s decode

Raises estimated decode speed by about 101%.

Adds memory headroom for longer context windows and future model growth.

~$4,999 MSRP

Frequently asked questions

Can MacBook Pro M2 Max 96GB run Codestral 22B?

Yes, MacBook Pro M2 Max 96GB can run Codestral 22B with a B grade (Runs well). Expected decode speed: 18.6 tok/s.

How much VRAM does Codestral 22B need?

Codestral 22B (22B parameters) requires approximately 27.1 GB of memory with Q4_K_M quantization.

What is the best quantization for Codestral 22B?

The recommended quantization for Codestral 22B is Q4_K_M, which balances quality and memory efficiency.

What speed will Codestral 22B run at on MacBook Pro M2 Max 96GB?

On MacBook Pro M2 Max 96GB, Codestral 22B achieves approximately 18.6 tokens per second decode speed with a time-to-first-token of 10417ms using Q4_K_M quantization.

Can MacBook Pro M2 Max 96GB run Codestral 22B for coding?

For coding workloads, Codestral 22B on MacBook Pro M2 Max 96GB receives a B grade with 18.6 tok/s and 33K context.

What context window can Codestral 22B use on MacBook Pro M2 Max 96GB?

On MacBook Pro M2 Max 96GB, Codestral 22B can safely use up to 33K tokens of context. The model's official context limit is 33K, but available memory constrains the safe maximum.

Is unified memory on MacBook Pro M2 Max 96GB as fast as VRAM for Codestral 22B?

Not always. MacBook Pro M2 Max 96GB 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 M2 Max 96GB See all hardware for Codestral 22B

Embed this result▼

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

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

Preview:

Workload

Grade

Fit

Decode

TTFT

Context

Chat

Runs well

18.6 tok/s

5682 ms

33K

Coding

Runs well

18.6 tok/s

10417 ms

33K

Agentic Coding

Runs well

18.6 tok/s

15153 ms

33K

Reasoning

Runs well

18.6 tok/s

12312 ms

33K

RAG

Runs well

18.6 tok/s

18941 ms

33K

Quantization options

How Codestral 22B (22B params) fits at each quantization level on MacBook Pro M2 Max 96GB (69.1 GB usable).

Quant	Bits	VRAM	Quality	Fit
Q2_K	2	8.6 GB	Low	C51
Q3_K_S	3	10.8 GB	Low	C51
NVFP4	4	12.3 GB	Medium	C51
Q4_K_M	4	13.4 GB	Medium	C52
Q5_K_M	5	15.8 GB	High	C52
Q6_K	6	18.0 GB	High	C52
Q8_0	8	23.5 GB	Very High	C54
F16Best for your GPU	16	45.1 GB	Maximum	B58

Frequently asked questions

Can MacBook Pro M2 Max 96GB run Codestral 22B?

Yes, MacBook Pro M2 Max 96GB can run Codestral 22B with a B grade (Runs well). Expected decode speed: 18.6 tok/s.

How much VRAM does Codestral 22B need?

Codestral 22B (22B parameters) requires approximately 27.1 GB of memory with Q4_K_M quantization.

What is the best quantization for Codestral 22B?

The recommended quantization for Codestral 22B is Q4_K_M, which balances quality and memory efficiency.

What speed will Codestral 22B run at on MacBook Pro M2 Max 96GB?

On MacBook Pro M2 Max 96GB, Codestral 22B achieves approximately 18.6 tokens per second decode speed with a time-to-first-token of 10417ms using Q4_K_M quantization.

Can MacBook Pro M2 Max 96GB run Codestral 22B for coding?

For coding workloads, Codestral 22B on MacBook Pro M2 Max 96GB receives a B grade with 18.6 tok/s and 33K context.

What context window can Codestral 22B use on MacBook Pro M2 Max 96GB?

On MacBook Pro M2 Max 96GB, Codestral 22B can safely use up to 33K tokens of context. The model's official context limit is 33K, but available memory constrains the safe maximum.

Is unified memory on MacBook Pro M2 Max 96GB as fast as VRAM for Codestral 22B?