Mac Studio M2 Ultra

A Mac Studio M2 Ultra runs 34 of the 34 open models tracked here at Q4_K_M with 8k context, computed on 16 October 2026. The largest is Mistral Small 4 119B (MoE), needing 72.5 GB and generating at most 149 tokens per second.

Updated

Memory
192 GB unified
For the GPU
144 GB
Bandwidth
800 GB/s
Released
2023
Availability
Apple unified memory
What it runs
34 of 34 models
At Q4_K_M with 8k context. The largest it holds is Mistral Small 4 119B (MoE): 72.5 GB, at most 149 tokens per second.
Computed 16 October 2026
Best model to run
Muse Glimmer 30B
18.7 GB of 144 GB, about 32 tokens per second: comfortable for chat. Picked as the biggest class of model that fits with room to spare and answers at 25 tokens per second or faster, then the newest release in it.
Computed 16 October 2026

Open the Mac Studio M2 Ultra in the LLM checker

What a Mac Studio M2 Ultra runs, model by model

Mac Studio M2 Ultra (192 GB) addresses 144 GB (75% of its 192 GB of unified memory, the share macOS is observed to hand the GPU by default) at 800 GB/s. Every model below is at Q4_K_M with 8k of context, the setting most people actually use. Once the 5% safety margin comes off, the card has 136.8 GB to spend: memory decides what loads, bandwidth how fast it answers. Both are estimates from stated formulas, and the VRAM calculator shows the working.

On this card a model fits at or under 136.8 GB, and above 122.4 GB it is tight: it loads, but there is little left for the conversation, and a desktop on the same 192 GB can push it over. Tokens per second are single-stream estimates from memory bandwidth; ≤ marks a ceiling real runtimes fall well below.

Computed 16 October 2026

One caveat specific to Apple silicon: these tokens-per-second figures describe generation, which unified memory handles well. Prompt processing (reading what you send before the first token comes back) is markedly slower than on an equivalent Nvidia card, and that is what you feel when you paste in a long document. Short prompts feel fast on this machine; 30,000-token ones do not.

The model to actually run on it

Muse Glimmer 30B is the best use of this card: 18.7 GB of the 144 GB available, an estimated 32 tokens per second, comfortable for chat, and 131,072 tokens of context still available.

How this is chosen, since no benchmark is quoted: models are compared by size, a mixture-of-experts model counting at the geometric mean of its total and active parameters (a rule of thumb, not a measurement). The pick is the biggest class that fits with memory to spare and answers at 25 tokens per second or better, and within that class the most recent general-purpose release; coding and reasoning specialists are listed above but not recommended by default.

Mistral Small 4 119B (MoE) is the largest model the card will hold, at 72.5 GB, with room for 131,072 tokens of context. It is a mixture-of-experts model reading only 6.5B parameters per token, so it is the faster of the two at an estimated 149 tokens per second; what it gives up is the depth of a dense model that reads all of its weights for every token.

If quality matters more than parameter count, Llama 3.3 70B fits at Q8_0 in about 81 GB. Q8 is near-lossless; a smaller model at Q8 often beats a larger one squeezed into Q3.

How much context actually fits

Model size is the question people ask; context is the one that bites. The KV cache grows linearly with the conversation, so a model that loads comfortably can still run out of memory halfway through a long document. On 144 GB, the context you get is whatever the weights leave behind, which is why two cards that run the same model can feel completely different in use. These are the largest contexts this card holds, at Q4_K_M weights.

ModelMax context, FP16 KVWith Q8 KV cache
Muse Glimmer 30B 131,072 tokens 131,072 tokens
Llama 3.3 70B 131,072 tokens 131,072 tokens
Qwen3 32B 40,960 tokens · model limit 40,960 tokens · model limit
Gemma 4 31B 131,072 tokens 131,072 tokens

Every model in this table already reaches its limit at FP16, so quantising the KV cache buys nothing here. Capped at 128k tokens, or at the model's own native window where that is smaller, marked "model limit": free memory beyond that point buys nothing. Rows that hold far more context than their size suggests are hybrid, sliding-window or latent-attention models, which cache only a fraction of what a standard transformer does; each model page shows the working.

Computed 16 October 2026

Where this card stops

Nothing in this list is out of reach. Every model tracked here fits at Q4_K_M with 8k of context, so the ceiling you will meet is context length and batch size, not parameter count.

Buy or rent

A genuine alternative to a multi-GPU build if you want silence, low power and very large models, and you do not need CUDA. If you need CUDA, the question is settled for you.

What matters is the memory upgrade rather than the machine, and Apple prices that differently in every configuration. Put the figure you are actually looking at, with your electricity rate and your real monthly hours, into the build vs rent calculator. It returns the month owning becomes cheaper, or tells you it never does. Hours per month decides it far more often than the price does.

The honest take

The quiet way to hold a very large model, as long as you are patient with long prompts.

Unified memory means the GPU can address most of the machine's RAM, so a fully specified M2 Ultra holds models that need a rack of Nvidia hardware. Generation is respectable at 800 GB/s, a little under a 3090's 936 GB/s, but prompt processing is markedly slower than on Nvidia, so long documents take a visible pause before the first token. For chat with a big model, it is excellent; for feeding it 30,000 tokens at a time, less so.

What it is good at

  • Up to 192 GB of unified memory: 70B models at Q8, or 120B mixture-of-experts models, on a desktop machine.
  • 800 GB/s with near-silent operation and a fraction of the power of an equivalent Nvidia build.
  • MLX and llama.cpp are both well supported on Apple silicon.

What it is not

  • Prompt processing is much slower than Nvidia. Long-context work feels different, not just slower.
  • CUDA-only tooling does not run, which rules out a good deal of the fine-tuning and image-generation ecosystem.
  • Memory is fixed at purchase; there is no upgrade path.

The thing people get wrong: You do not get all 192 GB. macOS caps GPU-addressable memory at roughly 75% of system RAM by default, so plan around about 144 GB unless you raise the limit yourself. Every fit calculation on this page uses the 75% figure.

Compared with the alternatives

  • MacBook Pro M4 Max: 96 GB · 546 GB/s · best fit Nemotron 3.5 Bolt 74B-A9B (MoE) at ~73 tok/s. A laptop that runs models a desktop GPU cannot hold.
  • RTX PRO 6000 Blackwell: 96 GB · 1,792 GB/s · best fit Llama 3.3 70B at ~31 tok/s. Ninety-six gigabytes and 5090-class bandwidth on one card.
  • RTX 6000 Ada: 48 GB · 960 GB/s · best fit Muse Glimmer 30B at ~39 tok/s. Forty-eight gigabytes in a normal computer, at 300 watts, without the noise.

All 39 cards are compared side by side on the GPU index, and the same numbers from the model's point of view are on each model fit table. To check one specific pairing rather than read a table, use the can-I-run-it checker.

Questions

Can a Mac Studio M2 Ultra run a 70B model?
Yes. Llama 3.3 70B at Q4_K_M with 8k of context needs about 45.8 GB, inside the 144 GB this card can address, and it generates an estimated 14 tokens per second, which is usable, a little slow.
What is the best model to run on a Mac Studio M2 Ultra?
Muse Glimmer 30B. At Q4_K_M and 8k context it needs about 18.7 GB of the 144 GB available and generates an estimated 32 tokens per second, which is comfortable for chat. If quality matters more than size, Llama 3.3 70B fits at Q8 in about 81 GB.
How many tokens per second does a Mac Studio M2 Ultra generate?
It depends entirely on the size of the model, because generating a token means reading every active weight out of memory. At 800 GB/s and 70% efficiency, this card produces an estimated 121 tokens per second on an 8B model at Q4, and about 149 on the largest model it holds, Mistral Small 4 119B (MoE). Reading speed is roughly 5 to 8 words per second, so anything above 25 feels immediate. Treat 121 as a ceiling on 800 GB/s rather than a measurement; the higher a figure, the further real runtimes fall below it.
Is 144 GB enough for running LLMs locally?
It runs 34 of the 34 models tracked here at Q4_K_M with 8k of context, up to 119B parameters. The honest test is not the model list but the context: Muse Glimmer 30B on this card holds about 131,072 tokens before memory runs out.
Mac Studio M2 Ultra or MacBook Pro M4 Max for local models?
This card holds more: 144 GB against 96 GB, but both run all 34 of these models at Q4_K_M with 8k of context, so the extra memory goes to longer context and higher precision. On speed, this card is faster: 800 GB/s against 546 GB/s, and bandwidth is what sets chat speed.
How much of a 192 GB Mac Studio can the GPU actually use?
About 75% by default, so roughly 144 GB, because macOS reserves the rest for the system. The limit can be raised with the iogpu.wired_limit_mb setting, at the risk of starving the operating system. Every figure on this page uses the 75% default.
Mac Studio or an Nvidia build for local LLMs?
The Mac holds far larger models for the money and does it silently at low power. The Nvidia build processes long prompts much faster and runs the CUDA-only half of the ecosystem, which includes most fine-tuning and image tooling. If you chat with big models, the Mac is excellent; if you feed them long documents or train anything, it is not.
  • Memory: weights (parameters × bytes per parameter) + KV cache (2 × layers × KV heads × head dim × context × bytes for a standard transformer; sliding-window, hybrid and latent-attention models counted as they actually cache) + 0.5 GB runtime + 4% of weights. Full derivation in the VRAM calculator.
  • Speed: 70% × bandwidth ÷ active weight bytes, single stream, no batching, prompt processing excluded. A ceiling, not a measurement: the 15 of 34 figures marked ≤ are where real runtimes fall furthest below the number, because so few weights are read per token. See the tokens-per-second estimator.
  • Card specification (manufacturer figures): 192 GB, 800 GB/s; see Apple's own page for this machine. Apple unified memory: Apple publishes no GPU share; macOS's Metal limit is observed at about 75% of RAM on large-memory Macs, and every figure here uses that share.
  • Model architecture values come from each model's published config; the self-hosted LLM guide explains what each one changes.