How to Safely Clean Up System Storage on a Mac

The safe order for freeing space on a Mac is: look at System Settings, General, Storage first, empty every trash can, uninstall the apps you no longer use, and only then go near cache folders. Nothing in that sequence can break your Mac. Most people recover what they need in the first two steps.

The dreaded gray bar labeled "System Data" is where the panic usually starts, so we will deal with what that actually is along the way.

Step 1: Find out where the space went

Open System Settings, then General, then Storage. Give it a minute, because the figures lag while macOS finishes calculating. Two parts matter:

• The colored bar at the top, which breaks usage down by category. Hover any segment for the size.
• The list underneath, which includes Applications, Documents and, at the bottom, a File Browser that lets you drill into folders by size without leaving Settings.

The Recommendations at the top are worth reading rather than clicking straight away. Store in iCloud genuinely frees local space, but it does it by keeping files only in the cloud, which means you need a connection to open them and enough iCloud storage to hold them. Optimize Storage removes watched films and old mail attachments, which are re-downloadable. Empty Trash Automatically deletes items after 30 days and is not reversible once it has run.

Step 2: Empty every trash can, not just the obvious one

Files sit in more holding pens than most people realize, and each one is real disk space:

• The Trash in the Dock. Emptying it is permanent.
• Each external drive has its own hidden trash. Connect the drive and empty the Trash again with it mounted.
• Photos keeps deleted images in Recently Deleted for 30 days. In Photos, open that album and choose Delete All.
• Notes and Messages have their own Recently Deleted areas.
• Mail holds deleted messages and, more importantly, downloaded attachments. In Mail, use Mailbox, then Erase Deleted Items.
• Downloads is not a trash can, but it behaves like one. Sort it by size and be honest about what you will open again.

What is System Data, and can I delete it?

System Data is not a folder. It is what the Storage screen calls everything that does not fit another category, and it typically contains:

• Application caches and logs
• Local Time Machine snapshots
• Swap and virtual memory files in /private/var/vm
• iPhone and iPad backups
• Downloaded mail attachments and browser data
• Xcode and other developer artifacts

There is no button that empties it, and no folder to drag to the Trash. You shrink it by removing the things that feed it.

Local snapshots are the most common surprise. If Time Machine is enabled, macOS keeps hourly snapshots on the internal drive so you can roll back without the backup disk attached. List them with tmutil listlocalsnapshots /, which only reads and changes nothing. They expire on their own, and macOS deletes them automatically when the disk comes under pressure, which is why the space is reported as purgeable. You can delete them manually with tmutil, but that is not reversible and you give up the ability to restore from those points. Waiting is almost always the better call.

Device backups live in ~/Library/Application Support/MobileSync/Backup and can run to tens of gigabytes. Before deleting one, be certain the phone is also backed up to iCloud or elsewhere, because for some people this folder is the only copy.

Swap files in /private/var/vm are managed by macOS. Leave them alone.

Step 3: Uninstall apps properly

Dragging an app from Applications to the Trash removes the bundle and leaves its support files behind, scattered across ~/Library/Application Support, ~/Library/Caches, ~/Library/Preferences, ~/Library/Containers and ~/Library/Logs. Individually small, collectively gigabytes on an old machine.

Two ways to do it properly:

1. Use the app's own uninstaller if it has one. Adobe apps, antivirus tools, VPN clients and anything that installed a driver or system extension should always be removed this way, because they place files outside your home folder that a generic tool will not find.
2. Use a free uninstaller such as AppCleaner for everything else. Drag the app onto it, review the list of associated files, and delete. It runs nothing in the background when closed, which is the same philosophy we described in lightweight Mac apps that respect resources.

One warning that matters: review the file list before confirming. Uninstallers occasionally match on a shared prefix and offer to delete support files belonging to an app you still use. And never delete a Containers folder for an app you intend to keep, because for sandboxed apps that folder holds your actual documents, not just cache.

Step 4: Caches, and exactly where the line is

This is the step where people get into trouble, so here is the rule. Deleting a subfolder of ~/Library/Caches is generally safe. Deleting the folder itself, or anything at the system level, is not.

To do it safely:

1. Quit the app whose cache you are clearing.
2. In Finder press Shift + ⌘ + G and go to ~/Library/Caches.
3. Switch to list view, sort by size, and look only at the largest few folders.
4. Delete the contents of a subfolder rather than the subfolder itself.
5. Restart the Mac so applications can rebuild what they need.

The cost is real if small: apps relaunch more slowly, some sign you out, and a few lose local state such as thumbnails or search indexes. For browsers, use the browser's own clearing tools instead. They know what is safe to drop and what is a stored login.

Step 5: Developer and creative bloat

• Xcode DerivedData at ~/Library/Developer/Xcode/DerivedData is intermediate build output. Deleting it is safe and it rebuilds on your next compile, at the cost of one slow build.
• Xcode Archives are not the same thing. You need them to symbolicate crash reports from released builds. Keep the archives for anything you have shipped.
• Unused simulators can be cleared with xcrun simctl delete unavailable, which removes only simulators tied to runtimes you no longer have.
• Docker is often the single largest offender. Start with docker system prune, which removes stopped containers, unused networks and dangling images. Only add -a --volumes once you understand it: the volumes flag permanently deletes named volumes, which is where database data lives. That is not recoverable.
• node_modules folders accumulate across every project you have ever touched. List them before deleting anything with find ~ -name node_modules -type d -prune. Removing them is reversible with a reinstall, but only if you have a network connection and the packages still exist.

Things not to delete

Short list, worth reading once:

• /System and anything inside it. System Integrity Protection blocks this anyway, which is the point.
• /Library/Caches at the root level, as opposed to the one in your home folder.
• ~/Library/Containers and ~/Library/Group Containers, which hold real documents for sandboxed apps.
• /private/var/vm, the swap files.
• Anything in /Library/LaunchDaemons you cannot identify. Search the file name before touching it.
• Files inside an iCloud Drive folder that show no download cloud icon, if you are not certain a copy exists elsewhere.

Do you need a paid cleaning app?

For most people, no. The categories that actually hold the space, large media, unused apps, device backups and developer artifacts, are all reachable with the built-in Storage tools and a free uninstaller. Paid cleaners bundle those functions with background agents that run constantly, and some of the space they report reclaiming is purgeable cache that macOS would have released on its own.

Where they earn their keep is convenience and duplicate detection. If that is worth a recurring fee to you, that is a fair trade. Just make the choice knowingly rather than because a full disk warning frightened you into it.

Keeping it clean without thinking about it

The maintenance version of this is a Smart Folder that shows every file over 500MB, pinned to your Finder sidebar. Check it once a month and the annual panic never arrives. Our guide to macOS Smart Folders has the exact rules.

If a tidy-up has left the Dock behaving oddly, duplicate icons or unresponsive stacks, that is usually a preferences file rather than a storage problem, and our guide on resetting the Mac Dock to default fixes it in one command. And if you would rather not rely on the Dock at all, ShortcutDock puts your apps in a menu bar panel instead, uses under 20MB of RAM and needs no account or network connection, which is the same restraint we look for in any app that stays open all day, as covered in why Apple Silicon native apps matter.