RemoveMacAI on macOS 27: Free Up Apple Intelligence Storage Safely

Hello HaWkers, updating your Mac can bring AI features you never use, along with model files that occupy storage. Apple says that Apple Intelligence features on macOS 27 may require up to 8 GB or up to 14 GB, depending on the hardware. That is a requirement published by the company, not a promise that every Mac can recover that much space. The open source RemoveMacAI project has attracted attention because it brings diagnosis, deactivation, and reversal together in one tool for this version of the system.

Do you know how much of that space is actually occupied on your computer and which functions would stop working if you removed the models? In this guide, we will separate measurement from estimates, read the utility's options before applying them, and prepare a way back. The decision remains yours: recovering storage only pays off when the affected features are not important to your everyday work.

What macOS 27 installs and why measuring comes first

Apple Intelligence spans features in several applications and services. Summaries in Mail and Messages, Writing Tools, and some image experiences may rely on different resources and models. As a result, switching off a visible setting does not necessarily delete files that have already been downloaded. Apple's support page describes individual controls in macOS 27; the RemoveMacAI repository says the models may remain on disk after the features are turned off.

Apple's documentation distinguishes eligible devices and storage ranges. It describes up to 14 GB for certain devices and up to 8 GB for others. Those figures express the storage required by the features, not the size of a single package. Actual usage varies with the Mac model, language, downloaded features, and update state. A number measured on your own Mac is more useful than someone else's screenshot.

Before running any utility, confirm the system version and available space. The commands below only inspect your system. sw_vers reports the installed version, while df shows the startup volume's free space in readable units. The df result does not separate Apple Intelligence from photos, applications, or caches, but it gives you a baseline for a later comparison.

# Confirm the macOS version before following this guide.
sw_vers

# Record the free space on the startup volume.
df -h /

Also note the figure under System Settings > General > Storage. If macOS is still calculating its categories, wait for the display to update. Do not treat a difference between two df readings as proof by itself that the tool deleted a particular model: snapshots, downloads, and background processes also change that total.

What RemoveMacAI actually does

According to the project README, the tool creates a configuration profile to disable AI features, requests model removal through Apple's asset service, and prevents those files from being downloaded again while the profile is active. The repository says the utility does not directly change files in /System and does not require you to disable System Integrity Protection. These are the maintainers' descriptions of how their tool works. If your computer is managed by an employer, check its internal policy before installing a profile as well.

The profile is the part that deserves particular attention. It does more than free storage at a single point in time: it keeps restrictions in place so the system will not download the removed models again. You confirm its installation in System Settings. If your Mac already uses another management profile, this change may be blocked or conflict with organizational rules. The tool does not replace your device administrator or Apple's official documentation.

The README lists features that may stop working: Siri, Writing Tools, Genmoji, Image Playground, summaries in applications, smart replies, photo cleanup, predictive editing in Xcode, and features that use local models through Apple's framework. The project itself clarifies that dictation has a separate setting. Do not assume that “turning off AI” affects only one switch. Its effects can appear throughout the Mac experience.

The tool also has explicit limits. The repository claims support for Apple silicon Macs running macOS 27, reports testing on version 27.0, and advises using version 0.2.3 or later on macOS 27.0.1. The project does not support version 26 or earlier. Since versions and compatibility can change, always check the README and the release notes for the version you intend to install when you use it.

Decide with a feature list, not just gigabytes

Before installing anything, make a simple inventory of the features you use. Anyone who relies on message summaries, Writing Tools, image features, or intelligent actions in the Shortcuts app has more functionality at stake. Someone who already keeps Apple Intelligence off and never uses those capabilities may prefer to reclaim the storage. This is not a universal performance question: the project documents model removal and feature restrictions, not a guaranteed speed improvement for every application.

One practical way to decide is to observe a normal week of work. Open your important apps, check whether your workflows use the functions listed by the project, and note what you would need to replace. If you use Xcode, pay special attention to the code completion mentioned in the README. If you automate tasks with Shortcuts, review actions that call local models. Do this before installing the profile so that an urgent deadline is not when you discover a dependency.

The discussion about Siri and AI across Apple's ecosystem also appears in our article on the Apple and Google partnership for Siri. These are different subjects, but the related article helps explain why it is useful to separate a feature's name from the infrastructure behind it. Here, the practical question is whether the local features on your Mac justify the storage they consume.

Install from a verifiable source and inspect the state

The project offers installation through Homebrew and a script published in its repository. For a process that changes system settings, read the documentation and identify the source before you run anything. The example below uses the formula specified by the maintainers and then inspects the current state. Installation itself requires Homebrew to be configured on your Mac. The status command is an inspection, not an instruction to remove models.

# Install the formula specified in the RemoveMacAI repository.
brew install omlahore/tap/removemacai

# See each feature and the size of the models the tool detects.
removemacai status

# Check the names accepted by the selective preservation option.
removemacai features

Save the status output so you can compare it later. The size reported there is specific to your Mac and the features installed on it. If the command says a component is absent, do not add an imaginary saving to your estimate. If Homebrew or the utility reports a version incompatible with your macOS installation, stop after reading the status and consult the updated README.

The repository also describes checksum verification and a provenance attestation for its release artifacts. Those controls can help verify the distribution, but they do not make a third party utility an official Apple feature. On a work computer, your IT policy and backups still matter. Never execute a command copied from a page without checking its address, version, and purpose.

Run a dry run and preserve what you use

The best step before making a change is to ask for a plan. The README's off --dry-run option shows what the tool intends to do without carrying out the deactivation. Read the entire list: it is the closest available summary of the actual impact on your installation. If it includes a feature you cannot give up, inspect the names returned by features and the --keep option, which the project also documents.

# Show the planned changes without applying them.
removemacai off --dry-run

# Inspect the state again if any line is unclear.
removemacai status

Do not interpret --dry-run as a complete reversal test. It does not install and remove the profile to prove that every application will keep working. Nor does it measure exactly how much space macOS will show immediately afterward. The value of this rehearsal is that it exposes the action list before you confirm anything, giving you time to stop.

If you decide to retain a feature, use only names printed by removemacai features. Do not invent a translated identifier. The documented syntax is removemacai off --keep <features>. Check what each name means in the documentation for your installed version, because preserving an option may also keep some of its associated models. That reduces the possible storage savings and may be exactly the balance you want.

Apply the change and check what happened

After your inspection and usual backup, execution is brief but includes a manual approval in macOS. The utility shows the current state and asks for confirmation. It opens System Settings for profile installation, a step that you control. Read the profile name and source shown on screen before accepting. The command below follows the basic documented flow; run it only if the dry run's action list matches your decision.

# Begin deactivation and review the confirmation request.
removemacai off

# Inspect the result after completing approval in macOS.
removemacai status

# Compare free space with your earlier measurement.
df -h /

The README notes that the Apple Intelligence category in Storage can continue displaying usage after the asset service releases the models. macOS removes the files on its own schedule. Therefore, a panel that takes time to update is not, by itself, proof that the command failed. Check the utility's status and inspect the system again later. For the same reason, avoid publishing a precise claim about gigabytes recovered unless you have measured it on your own device.

Now test the features you chose to keep and your critical applications. If a workflow stops, record the behavior before trying further changes. That makes it easier to tell whether the profile, an app that needs restarting, or a system update caused the problem. The project documentation says the profile persists across updates; at the same time, later macOS changes may alter how individual features work. Follow the utility's release notes if you decide to keep it installed.

How to undo the change and what limits remain

The way back is also in the README: revert removes the tool's changes. The project says that after the profile is removed, macOS may download the models again when a feature needs them. Reversible therefore does not mean instantaneous or free of network usage. If you need a feature while traveling or on a limited connection, revert ahead of time and confirm that it is available before leaving.

# Remove the restrictions applied by the tool.
removemacai revert

# Confirm the state after reversal.
removemacai status

# Optional: uninstall the formula if you do not plan to use it again.
brew uninstall removemacai

If you installed the utility through another method, consult that method's reversal instructions in the repository. Do not manually delete model files you find in system directories: the tool says it uses Apple's asset service precisely to avoid direct changes in protected areas. Do not disable System Integrity Protection to force a cleanup either. The documented path already offers a way to inspect, apply, and undo the operation.

There is an important distinction between turning off features in System Settings and adopting RemoveMacAI. Apple's official controls let you disable specific functions, including summaries and Siri, as described in Apple's help page. The utility adds an operation on downloaded models and a profile that blocks future downloads. If you only want to silence a feature, start with the official controls. If you need to recover measured storage and keep the models off the disk, weigh the cost of installing a third party profile.

Looking ahead: recovered space is useful when you stay in control

The RemoveMacAI case illustrates a change in how we have to think about storage. Local models offer latency and privacy benefits, but occupy resources even when their use is not obvious. macOS 27 spreads these features across several applications, so an informed decision requires looking at the whole set. The number of gigabytes on a support page is an upper requirement for certain devices. What matters is the actual usage on your Mac and what you would lose.

To make a repeatable choice, keep three records: the utility's initial status, the action list from the dry run, and the status after applying or reversing the change. Note which features you tested as well. That small history prevents a system update or a new habit from turning an old choice into an automatic rule. If an application begins to depend on local models, you will have a clear procedure for restoring the feature.

Finally, follow both Apple's and the project's documentation. The README consulted for this article declares specific support for macOS 27 on Apple silicon, while Apple describes its own controls and requirements. Neither source promises that every user will recover the same amount of space. Measure, read the changes, apply only what fits your workflow, and keep the reversal command handy.

Let's go! 🦅

📚 Want to Keep Up With What Is Coming?

This article covered RemoveMacAI and Apple Intelligence on macOS 27, but the ecosystem changes every week and not every development becomes a post here.

On X, I share what I am testing, the work behind my projects, and developments that surface before I write about them here.

Follow Me There

👉 Follow @jeffbruchado on X

💡 Daily content about development, careers, and the tools I actually use