Apple announced the new Mac Studio this morning — M5 Max and the first-ever M5 Ultra. Pre-orders are open, units ship September 22, and the headline for our corner of the world is this: up to 512GB of unified memory at 1.2TB/s, with Neural Accelerators in every GPU core.
I've spent the morning reading the spec sheet and the pricing page instead of working, so let me save you the trouble. This is not a review — nobody has benchmarked one yet. This is a "should you open your wallet" analysis, aimed squarely at developers who run models locally.
Skip the 8K ProRes stream counts. Three things matter if you run models: Neural Accelerators came to Ultra for the first time. The M5 generation puts dedicated matrix-multiply hardware inside each GPU core. The M5 Max shipped with this in the MacBook Pro; this is the first Ultra chip to get it. Apple claims up to 4.3x the peak AI compute of M3 Ultra, and up to 4x faster LLM prompt processing in LM Studio.
That prompt-processing number is the one to care about. Time-to-first-token on long contexts has been Apple silicon's most embarrassing weakness. You paste 60k tokens of codebase into a local model on an M3 Ultra and go make coffee. A 4x improvement there changes whether local agentic coding is usable versus a demo. Memory bandwidth went to 1.2TB/s — 50% up from M3 Ultra's ~819GB/s. For token generation, bandwidth is the speed limit. More on this below. It's a quad-die chip. M5 Ultra is two dual-die M5 Max chips fused with next-gen UltraFusion — over 4.4TB/s of inter-die bandwidth, four dies presenting as one processor. Up to 36 CPU cores (12 "super cores" + 24 performance cores) and an 80-core GPU.
Also new and genuinely relevant: Thunderbolt 5 clustering with RDMA. You can pool memory across multiple machines; Apple claims a four-Studio cluster hits 3x the inference throughput of a single box. And macOS 27 brings Core AI, a new framework for deploying full-scale LLMs locally, alongside MLX.
| Config | Price | |---|---| | M5 Max — 32-core GPU, 36GB, 512GB SSD | $2,499 | | M5 Max — 40-core GPU, 48GB | $3,099 | | M5 Ultra — 30-core CPU, 64-core GPU, 96GB, 1TB | $5,499 | | M5 Ultra — 36-core CPU, 80-core GPU, 96GB | $6,799 | | + 256GB unified memory | +$4,000 | | 512GB unified memory | Late October |
The $5,499 machine is not the M5 Ultra you read about in the headlines. It's a binned 30-core/64-core part. The full 36-core CPU / 80-core GPU chip starts at $6,799.
And if you want the memory — the entire reason to buy this machine for AI — 256GB is a $4,000 upgrade. That's a real config at $10,799 before you touch storage. Storage tops out at 16TB for another $4,000.
Some context on why: we're in the middle of a brutal DRAM shortage driven by AI datacenter demand. Apple removed the 512GB option from the M3 Ultra back in March and raised the 256GB upgrade from $1,600 to $2,000. Against that backdrop, the M5 Ultra Mac Studio starting at $5,499 (up from $3,999 for the M3 Ultra at launch, though that model was repriced to $5,299 in June) is less outrageous than it looks. Doesn't make it cheap.
For a dense model, "bytes read per token" is basically the whole model. So on a 1.2TB/s machine, back-of-envelope ceilings:
| Model | Size on disk (Q4) | Theoretical ceiling | Realistic guess | |---|---|---|---| | 70B dense | ~40GB | ~30 tok/s | ~20–25 tok/s | | 235B dense | ~130GB | ~9 tok/s | ~6–7 tok/s | | 671B MoE (~37B active) | ~380GB | high, but routing-bound | ~15–25 tok/s |
Treat these as estimates, not benchmarks. Real numbers depend on quantization, framework, and whether the model is dense or MoE. Wait for independent testing before you buy on the strength of a table — including mine.
The strategic takeaway: MoE models are the killer app for this machine. A big sparse model needs enormous memory to hold it but only reads its active parameters per token. The Mac Studio's weird superpower — huge memory pool, moderate bandwidth relative to a datacenter GPU — maps onto MoE architectures almost perfectly. And the open-weight frontier has been trending sharply toward MoE.
| Option | Memory | Price | The catch | |---|---|---|---| | NVIDIA DGX Spark | 128GB unified | ~$4,699 | ~273GB/s real bandwidth — dense 70B decode is slow | | RTX PRO 6000 Blackwell | 96GB GDDR7 | ~$8,565 | 1,792GB/s, actually trains things, needs a whole PC around it | | RTX 5090 | 32GB | ~$4,300+ | Fastest per dollar until your model doesn't fit. Then it's over. | | Mac Studio M5 Ultra | 96–512GB | $5,499–$10,799+ | CUDA is not here |
The honest summary: NVIDIA wins tokens per second, Apple wins gigabytes per dollar. Nothing else at any price puts 256GB — soon 512GB — of fast, coherent memory in a box that draws a few hundred watts and makes no noise on your desk.
That "no noise" thing is not a joke, by the way. A 4-GPU rig in a home office is a space heater with a jet engine attached. This is a small metal cube.
The CUDA tax is the real cost. Say it out loud before you buy: vLLM's continuous batching, TensorRT-LLM, most fine-tuning tutorials, most inference-server deployment guides, and half the research code on GitHub assume CUDA. MLX is genuinely good now and Core AI looks promising, but you will hit papers with reference implementations you can't run, and you'll be waiting on someone to port things. If your production target is an NVIDIA box, developing on Apple silicon means your dev environment and your deploy environment disagree.
And for serving concurrent users, it's not close — MLX doesn't match vLLM's batching efficiency. One developer? Great. Twenty concurrent users? Buy the NVIDIA hardware.