If you want a massive MacBook anyway then it's great. They are decent for local LLMs, awesome for local image models and it's a MacBook so AppleCare+ has your back. IMO it's a no brainer if you wanted a MacBook anyway but it's a poor choice if your reason to buy it is to run LLMs.
I agree. To run an acceptable model (e.g. Qwen/Qwen3.6-27B or google/gemma-4-31B) with a good quantization (minimum Q5) with a good context size (min 64k) you could buy 2 or even 3 GTX 5060 16GiB VRAM for ~550$ each. Fyi the much faster MoE models were useless for my usecases - e.g not able to correctly identify me/I/you, endless thinking loops, etc.
I'm currently running those models using an RTX 5070 12GiB + RTX 5060 16GiB + RTX 3060 12GiB with a 96k context size with MTP/speculative decoding and I'm quite happy (the 5070 is about 4x faster than the 3060, the 5060 is inbetween them so about 2x faster than a 3060).
I asked a few of my friends that are ML engineers this question and all of them said to run the LLMs in the cloud with their infrastructure because it was going to be way faster.
If you just want to tinker around I would look at @JSR_FDD's comment.
Around February or march I started looking into hardware options to help me start learning about training models and working with them. My budget was limited and an apple refurbished 32 gb Mac mini was far and away the best option for my budget. I wish it was faster but I can let it run 24/7 with no noise and minimal power draw. I just arrange long running tasks for when am asleep or at work. Then as a huge plus I have an awesome daily driver machine for whatever else I want to do
This is my opinion too. Even if you buy hardware like a cluster of 8xGB10s or 4 A100s, they'll still be slow and a little dumber than what you're used to. We need to wait a little for better hardware. Lots of companies are pushing the frontier, so hopefully it'll come very soon.
Competition and innovation will hopefully make the bubble pop, and we'll get reasonably priced local hardware to run very intelligent models. Something like Talaas with GLM 5.2 would be pretty cool. Or Apple printing the latest model onto hardware—it would give a new reason to buy a new Mac every year (a new ai model with every new version).
The hardware is here today for people prepared to tolerate mild amounts of latency. It’s easy to forget that computing tasks used to often take major amounts of time - rendering an audio file, rendering a video, transcoding – all kinds of tasks took minutes or even hours of the computer spinning its fans on maximum just to deliver the result. AI and agentic AI and diffusion is the next round of that - trading a small bit of your waiting time for phenomenal power. The datacentre builders trying to get you hooked on instant responses on the LLM platforms have made you think that a “good” AI responds instantly and completely interactively - they can still be brilliant with a bit of delay. And having a competent agent doing things on my local machine, it doesn’t really matter if it takes ten minutes or an hour or six hours to complete a task while I’m out doing other things.
Hmm, I have access to A100s and a GB10, but if I use the models hosted there to code, I waste a lot of time waiting for answers and correcting errors. The amount of work I get done thanks to the quality and speed of frontier hosted models let me be insanely productive and have a lot of free time. I could use the slow local setup, but at what price?
Well if all that was taken away from you and you had to go to the bank to ask for the money to rebuild so you could become as productive as you are now, what would that cost and would the bank loan you the money?
Macbook M5 64GB - can run gemma-4-26b-a4b-it-4bit and Qwen3.6-35B-A3B-4bit at about 1500 tps prefix and 45 tps decode on contexts up to 100K tokens using MLX. It's faster than Claude. I was really surprised, chat quality is also similar to Claude for gemma4. Agentic works but does not compare to cloud models, you can still make agents where top level is code.
sorry but asking again: how much memory is actually useable by gpu in macbook? as it is shared(os and apps also have to use same memory)?
and it is different than dedicated gpu memory?
It’s completely shared so the OS and everything else takes up maybe 8GB of the RAM. On a 64GB machine you can run models about 45GB in size and still have space for those models run other tasks which themselves might need ram. To a user, the GPU appears to just use the RAM as much as it needs same as any other process running on the system. You can see what space your LLMs are taking up in Activity Monitor (or htop) and how much GPU capacity they’re using (all of it)
Idk why you’re being downvoted for asking a question. Pending specs they _could_ provide more headroom for a larger model but they would still be limited by the CPU and it’s associated bus speeds.
It’s kind of amazing how steadily this question is asked in every forum where it can be asked. Kind of amazing that the answers previously given can’t reach the next person who’s going to ask it.
Local LLMs running in LM Studio on a MacBook Pro work great, if you’re prepared to wait for the answers because using an LLM locally is much much slower than having the instant results appear when using an online LLM like ChatGPT or Claude. You can also run OpenClaw on the MacBook and have that act as the front end for the LLM, to get full interactivity and have it install command line tools on your Mac to perform whatever tasks you’ve set it.
If you don’t already have a MacBook, then there’s a bit of a sweet-spot for the AI experimenter right now, which is to buy a second-hand 16” MBP with an M1 Max chip and 64GB of shared ram. Because these are about 5 years old now, they have depreciated to the point where they can be had for around £1100 / €1300 / $1500 and make a phenomenal platform for learning because the 64Gb of shared memory means you can host models up to about 48GB in size, and then task them to do interesting things with coding without ever having to worry about token burn.
The downside is that they’re slow, and prone to having to be nudged to keep them on track, but that’s part of the fun too. The “latency” is atrocious granted - you ask something and the machine thinks for a few minutes before saying anything which is a different experience to using Claude. But… it does work. You can think of yourself more like a manager with a junior member of staff and set the machine running and leave it to do its thing for a couple of hours which can be actually useful work, but this approach will likely be shouted down by some commenters here who treat Claude like some kind of expensive and quick-fire dopamine pump. Can also use a Mac like this for running diffusion models for image generation and suchlike in ComfyUI, even though, again, results will be slow. Spending more money on a more recent MBP with as much RAM as you can afford will deliver the same results more expensively in a quicker and quicker time.
To get the same kind of size of model you’d have to combine a couple of Nvidia 3090 24GB cards in a decent workstation with the PCI capacity to handle them, or hack some kind of solution to hang GPUs off the back of a motherboard on ribbon cables with the GPUs running on their own PSU, which is what I’m building next… the difference is those cards have 24GB of vram and cost about $1000 each second-hand, but will operate much much faster than the M1 Max MBP, or even the most recent M5 because they have so much more bandwidth (because they’re burning 350 watts on GPU compute rather than 140 watts total which is what a super efficient MBP has for the cpu/gpu/screen/everything).
So say you had $6000 to spend today, you could buy a second hand workstation and craft a solution with external GPUs which would completely smoke any Mac in existence, even though macs have the edge in the size of model you’d can run (slowly) due to their shared memory. External GPUs and access to the Nvidia frameworks and general CUDA ecosystem wins out on the performance front though. A real sweet spot is to buy an M1 Max MBP and have that as your front end to a Linux workstation full of GPUs.
But any apple silicon MBP is a totally competent gateway drug to local agentic computing.
Google Gemini could give you an in-depth and useful discussion about this exact question.
If you want a massive MacBook anyway then it's great. They are decent for local LLMs, awesome for local image models and it's a MacBook so AppleCare+ has your back. IMO it's a no brainer if you wanted a MacBook anyway but it's a poor choice if your reason to buy it is to run LLMs.
I agree. To run an acceptable model (e.g. Qwen/Qwen3.6-27B or google/gemma-4-31B) with a good quantization (minimum Q5) with a good context size (min 64k) you could buy 2 or even 3 GTX 5060 16GiB VRAM for ~550$ each. Fyi the much faster MoE models were useless for my usecases - e.g not able to correctly identify me/I/you, endless thinking loops, etc.
I'm currently running those models using an RTX 5070 12GiB + RTX 5060 16GiB + RTX 3060 12GiB with a 96k context size with MTP/speculative decoding and I'm quite happy (the 5070 is about 4x faster than the 3060, the 5060 is inbetween them so about 2x faster than a 3060).
are you saying because of speed or it just cant run them?
I asked a few of my friends that are ML engineers this question and all of them said to run the LLMs in the cloud with their infrastructure because it was going to be way faster. If you just want to tinker around I would look at @JSR_FDD's comment.
Around February or march I started looking into hardware options to help me start learning about training models and working with them. My budget was limited and an apple refurbished 32 gb Mac mini was far and away the best option for my budget. I wish it was faster but I can let it run 24/7 with no noise and minimal power draw. I just arrange long running tasks for when am asleep or at work. Then as a huge plus I have an awesome daily driver machine for whatever else I want to do
My opinion is that you should wait for 6-12 months before making a purchase either way.
Open weight models are getting good. With GLM 5.2 now chasing Opus, I'm very excited to see a smaller model's distillation.
Plus, the OLED MacBook Pro should be released by then.
This is my opinion too. Even if you buy hardware like a cluster of 8xGB10s or 4 A100s, they'll still be slow and a little dumber than what you're used to. We need to wait a little for better hardware. Lots of companies are pushing the frontier, so hopefully it'll come very soon.
Competition and innovation will hopefully make the bubble pop, and we'll get reasonably priced local hardware to run very intelligent models. Something like Talaas with GLM 5.2 would be pretty cool. Or Apple printing the latest model onto hardware—it would give a new reason to buy a new Mac every year (a new ai model with every new version).
The hardware is here today for people prepared to tolerate mild amounts of latency. It’s easy to forget that computing tasks used to often take major amounts of time - rendering an audio file, rendering a video, transcoding – all kinds of tasks took minutes or even hours of the computer spinning its fans on maximum just to deliver the result. AI and agentic AI and diffusion is the next round of that - trading a small bit of your waiting time for phenomenal power. The datacentre builders trying to get you hooked on instant responses on the LLM platforms have made you think that a “good” AI responds instantly and completely interactively - they can still be brilliant with a bit of delay. And having a competent agent doing things on my local machine, it doesn’t really matter if it takes ten minutes or an hour or six hours to complete a task while I’m out doing other things.
Hmm, I have access to A100s and a GB10, but if I use the models hosted there to code, I waste a lot of time waiting for answers and correcting errors. The amount of work I get done thanks to the quality and speed of frontier hosted models let me be insanely productive and have a lot of free time. I could use the slow local setup, but at what price?
Well if all that was taken away from you and you had to go to the bank to ask for the money to rebuild so you could become as productive as you are now, what would that cost and would the bank loan you the money?
The racks we're deploying are effectively GB300 NVL72s: 72 Blackwell Ultra GPUs 36 Grace CPUs, 20.7TB of unified HBM3e.
Works out to about 1.1exaflops of fp4. Networking is 800gbps.
120kW per rack.
That’s a majorly impressive computer. What’s the price of that per rack? Deploying for what?
MacBooks with their unified memory behave like a slow GPU with enormous amount of video RAM. So you can run large smart models slowly.
Dedicated GPUs have less video RAM so can run smaller less smart models quickly.
Macbook M5 64GB - can run gemma-4-26b-a4b-it-4bit and Qwen3.6-35B-A3B-4bit at about 1500 tps prefix and 45 tps decode on contexts up to 100K tokens using MLX. It's faster than Claude. I was really surprised, chat quality is also similar to Claude for gemma4. Agentic works but does not compare to cloud models, you can still make agents where top level is code.
sorry but asking again: how much memory is actually useable by gpu in macbook? as it is shared(os and apps also have to use same memory)? and it is different than dedicated gpu memory?
It’s completely shared so the OS and everything else takes up maybe 8GB of the RAM. On a 64GB machine you can run models about 45GB in size and still have space for those models run other tasks which themselves might need ram. To a user, the GPU appears to just use the RAM as much as it needs same as any other process running on the system. You can see what space your LLMs are taking up in Activity Monitor (or htop) and how much GPU capacity they’re using (all of it)
You can adjust the percentage available both on the MacOS side and how much the model uses.
Do Mac Pros provide more headroom? noob here, noob questions
In what sense? Headroom for what?
Idk why you’re being downvoted for asking a question. Pending specs they _could_ provide more headroom for a larger model but they would still be limited by the CPU and it’s associated bus speeds.
how much memory is actually useable by gpu in macbook? as it is shared?
roughly ~50–56GB, although this is somewhat configurable with iogpu.wired_limit_mb. By default, macOS reserves ~25% of memory for the system.
Both are going to be super super slow and low payback.
You gotta really want it right now.
It's still early!
It’s kind of amazing how steadily this question is asked in every forum where it can be asked. Kind of amazing that the answers previously given can’t reach the next person who’s going to ask it.
Dual 3090 >>> Any Apple product.
Doesn't the 3090 cap out at 24GB VRAM? That's not a lot to run a local model
but still it can run handsome models
> Dual 3090 >>> Any Apple product.
Dual 3090s are terrible airpods
I snorted
Local LLMs running in LM Studio on a MacBook Pro work great, if you’re prepared to wait for the answers because using an LLM locally is much much slower than having the instant results appear when using an online LLM like ChatGPT or Claude. You can also run OpenClaw on the MacBook and have that act as the front end for the LLM, to get full interactivity and have it install command line tools on your Mac to perform whatever tasks you’ve set it.
If you don’t already have a MacBook, then there’s a bit of a sweet-spot for the AI experimenter right now, which is to buy a second-hand 16” MBP with an M1 Max chip and 64GB of shared ram. Because these are about 5 years old now, they have depreciated to the point where they can be had for around £1100 / €1300 / $1500 and make a phenomenal platform for learning because the 64Gb of shared memory means you can host models up to about 48GB in size, and then task them to do interesting things with coding without ever having to worry about token burn.
The downside is that they’re slow, and prone to having to be nudged to keep them on track, but that’s part of the fun too. The “latency” is atrocious granted - you ask something and the machine thinks for a few minutes before saying anything which is a different experience to using Claude. But… it does work. You can think of yourself more like a manager with a junior member of staff and set the machine running and leave it to do its thing for a couple of hours which can be actually useful work, but this approach will likely be shouted down by some commenters here who treat Claude like some kind of expensive and quick-fire dopamine pump. Can also use a Mac like this for running diffusion models for image generation and suchlike in ComfyUI, even though, again, results will be slow. Spending more money on a more recent MBP with as much RAM as you can afford will deliver the same results more expensively in a quicker and quicker time.
To get the same kind of size of model you’d have to combine a couple of Nvidia 3090 24GB cards in a decent workstation with the PCI capacity to handle them, or hack some kind of solution to hang GPUs off the back of a motherboard on ribbon cables with the GPUs running on their own PSU, which is what I’m building next… the difference is those cards have 24GB of vram and cost about $1000 each second-hand, but will operate much much faster than the M1 Max MBP, or even the most recent M5 because they have so much more bandwidth (because they’re burning 350 watts on GPU compute rather than 140 watts total which is what a super efficient MBP has for the cpu/gpu/screen/everything).
So say you had $6000 to spend today, you could buy a second hand workstation and craft a solution with external GPUs which would completely smoke any Mac in existence, even though macs have the edge in the size of model you’d can run (slowly) due to their shared memory. External GPUs and access to the Nvidia frameworks and general CUDA ecosystem wins out on the performance front though. A real sweet spot is to buy an M1 Max MBP and have that as your front end to a Linux workstation full of GPUs.
But any apple silicon MBP is a totally competent gateway drug to local agentic computing.
Google Gemini could give you an in-depth and useful discussion about this exact question.