You’re mid-export on a video project when the warning slides in from the corner of the screen. Startup disk almost full. You open Storage settings, ready to hunt down the usual suspects — old installers, a bloated Xcode cache, that Docker volume you forgot about — and there it is, sitting near the top of the list like it pays rent: Apple Intelligence, 29 GB.
You didn’t download it. You didn’t ask for it. On some Macs running macOS 27, forum reports put it north of 30 GB. And if you’re working off a 256GB base-model MacBook Air, that’s more than a tenth of your entire machine handed over to features you may never touch.
What’s actually taking up the space
Apple Intelligence runs a good chunk of its work on-device, which is the whole pitch. Your requests don’t need to make a round trip to a data center, your data stays local, and latency drops. That architecture has a price, and the price is storage. Generative language models, visual assets, and supporting files all have to physically live on your SSD.
AppleInsider’s Andrew Orr walked through the removal process, and the short version is that the bulk of it sits in one main model folder. Delete that folder and you reclaim the majority of the footprint. The full cleanup involves Terminal commands to purge the hidden generative models and visual assets that don’t show up in a casual Finder browse. Reported result: that 29 GB drops to roughly 3.07 GB.
Call it about 26 GB back. On a base-model machine, that’s the difference between a disk warning every other day and a laptop you can actually work on.
Why this matters beyond Apple
I spend my time curating AI agents and tools that earn their place in a workflow. The pattern I keep seeing across the whole on-device AI push, Apple’s included, is that local inference gets sold purely as a privacy and speed win while the storage cost goes unmentioned until your disk fills up.
Local models are genuinely good. I’d rather run a small model on my own hardware than pipe everything through someone’s API, both for privacy and for the simple fact that it keeps working on a plane. But the deal only makes sense when you choose it. A model you actively use is an asset. A model sitting idle on your SSD because an OS update decided you wanted it is just a very large file.
That’s the real friction here. Every AI agent and tool I evaluate gets measured against a simple question: does what it gives me beat what it costs me in disk, memory, battery, and attention? Apple Intelligence can pass that test for plenty of people. Writing Tools, image cleanup, and the newer Siri work are legitimately useful if they fit how you work. The problem is that nobody ran the calculation on your behalf and then asked.
The catch worth knowing before you start
This isn’t a permanent fix, and that’s the part I’d want to know before spending twenty minutes in Terminal.
Reports indicate macOS 27 still downloads the data for EU users and removes options to disable the functionality. So the space you clear today can come back on your next upgrade. You’re not uninstalling a feature. You’re temporarily evicting it and hoping the next system update doesn’t let it back in.
That’s a frustrating place to land. Over on the MacRumors forums, users are asking Apple to make Apple Intelligence not just disableable but fully removable, with hopes pinned on 27.2 or a later point release. The fact that the request has traction tells you something about how many people are hitting this.
How I’d approach it
If you’re deciding whether this cleanup is worth your time, a few things to weigh:
- Check your actual number first. Open Storage settings and see what Apple Intelligence is reporting on your machine. Figures vary — 29 GB is what shows up in settings for many users, with some reports above 30 GB.
- Be honest about usage. If you’ve used Writing Tools three times since install, the math is easy. If Siri AI has become part of your daily routine, 29 GB may be a fair trade.
- Know that upgrades can undo it. Treat the reclaimed space as borrowed, not banked, especially if you’re in the EU where the download behavior persists.
- Follow a source that documents the exact commands. Terminal operations that remove system-adjacent files are not the place to improvise. AppleInsider’s writeup covers the specific paths and steps.
- Back up before you touch anything. Standard advice, routinely skipped, occasionally expensive.
The broader lesson I’d pull from this: as on-device AI spreads across operating systems, storage becomes a resource you negotiate over rather than one you simply own. Knowing where the models live, what they cost, and how to remove them is turning into basic maintenance literacy — the same way clearing caches and pruning old builds already is.
Twenty-six gigabytes is a real amount of disk. If you’re not using what’s sitting in it, go get it back. Just don’t be surprised when it knocks again.
đź•’ Published: