Best GPU for local AI

Which AI models can the Apple M1 Max run?

The Apple M1 Max has memory shared by its processor and graphics, read at 400 GB/s. In 64 GB of memory, 58 of the 88 open models here run in the share of memory its graphics can use, 56 of them writing faster than you read; the most capable it runs well is Qwen3 32B at Q4_K_M, 8.6–14 tokens/s. Macs are here for comparison: Bottleneck’s app runs on Windows.

Every figure is for an 8,192-token conversation (about 6,000 words), at the best compression that fits. Try it in the calculator with your own memory, conversation length and compression, or a second card.

Models that run entirely on its graphics

The fastest way to run a model: all of it in graphics memory. Most people read at 5 to 8 tokens a second, so anything above 10 feels quick.

Models the Apple M1 Max runs entirely on its graphics
ModelCompressionWritesNeeds
Qwen3.5 122B-A10BQ2_K41–65 tokens/s47 GB
Nemotron 3.5 Super 120B-A12BQ2_K35–56 tokens/s47 GB
Qwen3 Coder Next 80B-A3BQ3_K_M83–135 tokens/s39 GB
Nemotron 3.5 Bolt 74B-A9BQ4_K_M30–48 tokens/s45 GB
Qwen2.5 72BQ4_K_M4.0–6.4 tokens/s47 GB
Llama 3.3 70BQ4_K_M4.1–6.6 tokens/s45 GB
Flint 40B-A2.5BQ8_053–85 tokens/s43 GB
Qwen3.6 35B-A3BQ8_047–75 tokens/s38 GB
Qwen3 32BQ4_K_M8.6–14 tokens/s22 GB
Nemotron 3.5 Lightning 30B-A3BQ8_047–76 tokens/s34 GB
Gemma 4 31BQ5_K_M7.8–12 tokens/s23 GB
GLM-4.7 FlashQ8_045–72 tokens/s34 GB
Qwen3 30B-A3B 2507Q8_040–64 tokens/s33 GB
Qwen3 Coder 30B-A3BQ8_040–64 tokens/s33 GB
Muse Glimmer 30BQ5_K_M8.5–14 tokens/s21 GB
Granite 4.2 30BQ5_K_M8.3–13 tokens/s23 GB
Qwen3.6 27BQ6_K7.8–13 tokens/s23 GB
Qwen3.8 27BQ6_K7.8–13 tokens/s23 GB
Gemma 3 27BQ6_K7.8–12 tokens/s24 GB
Gemma 4 26B-A4BQ8_037–59 tokens/s28 GB
Mistral Small 3.2 24BQ6_K8.9–14 tokens/s21 GB
Devstral Small 2 24BQ6_K8.9–14 tokens/s21 GB
LFM2.5 24B-A2BQ8_055–88 tokens/s26 GB
gpt-oss 20BMXFP465–105 tokens/s12 GB
Qwen3 14BQ8_011–18 tokens/s17 GB
Phi-4Q8_011–18 tokens/s17 GB
Ministral 3 14BQ8_012–19 tokens/s16 GB
Gemma 3 12BQ8_013–21 tokens/s14 GB
Gemma 4 12BQ8_014–22 tokens/s13 GB
Qwen3.5 9BQ8_017–28 tokens/s11 GB
Ornith 1.5 9BQ8_017–28 tokens/s11 GB
Ministral 3 8BQ8_018–29 tokens/s11 GB
Granite 4.2 8BQ8_018–29 tokens/s11 GB
Qwen3 8BQ8_019–31 tokens/s9.9 GB
DeepSeek R1 0528 Qwen3 8BQ8_019–31 tokens/s9.9 GB
Llama 3.1 8BQ8_020–32 tokens/s9.6 GB
Gemma 4 E4BQ8_036–58 tokens/s8.7 GB
Qwen2.5 7BQ8_021–34 tokens/s8.6 GB
Mistral 7B v0.3Q8_022–35 tokens/s8.8 GB
Gemma 4 E2BQ8_069–110 tokens/s5.5 GB
Qwen3.5 4BQ8_035–56 tokens/s5.2 GB
Gemma 3 4BQ8_037–59 tokens/s4.9 GB
Qwen3 4B 2507Q8_036–58 tokens/s5.5 GB
Ministral 3 3BQ8_039–62 tokens/s5.0 GB
Phi-4-miniQ8_038–61 tokens/s5.2 GB
Granite 4.2 3BQ8_042–67 tokens/s4.6 GB
Llama 3.2 3BQ8_045–72 tokens/s4.4 GB
SmolLM3 3BQ8_049–78 tokens/s3.9 GB
Qwen3.5 2BQ8_070–110 tokens/s2.5 GB
Qwen3 1.7BQ8_066–105 tokens/s3.1 GB
LFM3 1.7BQ8_089–145 tokens/s1.9 GB
Llama 3.2 1BQ8_0115–180 tokens/s1.6 GB
Gemma 3 1BQ8_0145–235 tokens/s1.1 GB
Qwen3.5 0.8BQ8_0160–260 tokens/s1.0 GB
Qwen3 0.6BQ8_0130–205 tokens/s1.7 GB
SmolLM2 360MQ8_0260–420 tokens/s0.7 GB
LFM2.5 350MQ8_0320–515 tokens/s0.5 GB
Gemma 3 270MQ8_0400–645 tokens/s0.3 GB

The other 30 need more memory than 64 GB of memory has; the calculator shows what more memory, or a second card, would add.

Compared with similar graphics

Tokens per second writing Llama 3.1 8B at 4 bits, which every 8 GB card holds, and the most capable model each runs well in its share of memory. Every card ranked.

GraphicsMemoryLlama 3.1 8BMost capable it runs well
Apple M4 Max64 GB shared60Qwen3 32B
Apple M3 Max64 GB shared47Qwen3 32B
Apple M2 Max64 GB shared47Qwen3 32B
Apple M1 Max64 GB shared44Qwen3 32B
Apple M5 Pro32 GB shared41Gemma 4 31B
NVIDIA DGX Spark and other GB10 mini PCs, 128 GB128 GB shared41Llama 4 Scout 109B-A17B
Ryzen AI Max+ 395 (Radeon 8060S)128 GB shared37Llama 4 Scout 109B-A17B

Estimated tokens per second; a real figure is usually within a quarter either way. * Part of it in system memory. {CAPABLE_NOTE}

How it is worked out

Writing an answer is limited by memory rather than arithmetic: for every word-piece (token) a model writes, the computer reads every weight that token uses once. So the speed is how fast the memory holding the model can be read, divided by how much is read for each token: the model’s weights at the chosen compression, plus the conversation so far. How much of its memory speed each graphics card reaches is measured, not assumed: it comes from the card’s own result in llama.cpp’s benchmark, which LM Studio, Ollama and Jan are built on. A model that does not fit in the graphics card’s memory spills into system memory, five to fifteen times slower, and one that does not fit in memory at all can be read from the drive as it runs, slower again; the estimate counts each part at its own speed, and a processor with few threads cannot use all of fast memory. Graphics built into a processor use system memory, at its speed. Reading a prompt is limited by arithmetic, so it follows the measured prompt speed.

Already running a model? See if it runs at full speed

A model that is slower than it should be is nearly always partly on the processor rather than all on the graphics card, which is several times slower — and Ollama does that without a word when something else holds the card’s memory. Bottleneck’s free app checks a model run with Ollama, LM Studio, llama.cpp, KoboldCpp or Jan: where it really runs, how fast it writes, and what your PC should manage with it. Nothing leaves your PC. Or check and fix it by hand.

It reads your parts too: the graphics card and how much memory it really has free, how much system memory is installed, the speed it runs at and in how many channels. Memory left in one channel, or below its rated speed, halves how fast a model runs from it, and Bottleneck says so. Its AI models screen then lists what runs on this PC.

The free version shows where a model runs and how fast, with no time limit and no account. Pro, $9 once, explains why it is slower than it could be and how to fix it. Compare the versions