Twenty-nine gigabytes. That is what Apple Intelligence reportedly occupies in the Storage settings pane on a Mac, according to users comparing notes on Hacker News and the MacRumors forums. Delete the main model folder and that figure drops to roughly 3.07 GB. For anyone running a 256 GB SSD, that is over 11 percent of the drive handed to a feature they may never open.
AppleInsider published a walkthrough on removing those models, and the method is what you would expect: Terminal commands that purge hidden generative models and visual assets that do not show up anywhere in Finder. It works. It also tells us something about how AI features are now shipped, and that is the part I want to talk about.
Storage is a security question, not a housekeeping one
My day job is looking at how AI systems get attacked. When I read “29 GB of generative models installed on disk,” I do not primarily think about free space. I think about attack surface.
Local model weights and visual assets are files. Files that are large, binary, opaque to the user, and loaded by privileged system processes. You cannot read them. You cannot meaningfully audit them. You cannot tell by looking whether what is on disk matches what the vendor intended to put there. The only reason most people know these files exist at all is that a storage meter went red.
That is a category of component security teams usually insist on tracking. We maintain inventories of installed software. We fingerprint binaries. We alert when something unexpected lands in a system directory. On-device AI model bundles slot awkwardly into every one of those processes, because they arrive through OS update channels, they are not listed as applications, and they change size and shape between point releases.
None of that means Apple’s models are dangerous. It means they are an unmonitored blob on an endpoint, and unmonitored blobs on endpoints are how I earn a living.
The part that actually bothers me
Deleting files you do not want is fine. What concerns me is the direction of travel described in the sources: macOS 27 reportedly still downloads the data for EU users and removes options to disable the functionality. Which means users who reclaim space today may lose it again on upgrade.
Read that as a security control problem rather than a storage one. Being able to turn a feature off is a control. It is the simplest, most reliable control there is, and it is the one defenders reach for first when they cannot audit something. “We do not run that component” is a complete answer to an entire class of risk. Take the toggle away and you take the answer away with it.
The workaround in its place is a Terminal command that deletes files the operating system wants to have, on a system that may re-download them. That is not a control. That is a race condition. Any security posture built on “we deleted it last Tuesday” is a posture that quietly expires.
What this means for managed fleets
If you administer Macs for an organisation, the practical questions are worth writing down before the next upgrade cycle:
- Do you know how much disk the AI components consume across your fleet right now, and how that changes on upgrade?
- If you remove them with a script, what happens on the next OS update, and who notices if space disappears again?
- Do your endpoint monitoring rules understand model files, or will a deletion script trip alerts as though it were tampering?
- If a feature cannot be disabled through supported configuration, what is your actual answer when an auditor asks whether it is in use?
Those are not rhetorical. The AppleInsider method is a user tip, not a management policy, and the gap between the two is where fleets drift out of compliance without anyone making a decision.
Reclaim the space, but know what you are buying
So, yes: if you want the storage back, the approach exists and the numbers are real. Going from 29 GB to around 3.07 GB is a meaningful win on a small drive, and there is nothing improper about declining a feature you do not use.
Treat it as temporary. Assume a future update may reverse it. Script it if you must, document it, and keep an eye on the storage pane after every upgrade.
The wider lesson is the one I keep running into across every platform adding local inference. AI features are increasingly being shipped as non-optional system components, installed by default, measured in tens of gigabytes, and invisible to the tools we use to understand what runs on our machines. Storage is just the symptom that happens to be visible. The audit gap underneath it is the thing worth watching, and the thing vendors should be closing with supported off switches rather than leaving to Terminal commands traded on forums.
🕒 Published: