Why Is System Data Taking Up So Much Space on Mac?

Open System Settings → General → Storage and you get a tidy coloured bar: Applications, Documents, Photos, and so on. Then there's a grey segment labelled System Data, and sometimes it is enormous. It doesn't tell you what's inside, and there's no button to open it.

This guide explains what System Data is, why it grows, how to look inside it with tools you already have, and what is actually safe to shrink. It is written so you can stop at any point. The first few sections free up space with almost no risk; the later ones are for stubborn cases.

What System Data actually is#

The Storage screen sorts your files into categories it recognises: your apps, documents, photos, mail, and so on. System Data is the remainder. Older versions of macOS called it Other, which was just as unhelpful.

Because it is a catch-all, it contains very different kinds of things. Some are small and permanent, some are large and temporary, and some are large and yours.

• Applications
• Documents
• Photos
• macOS
• System Data
• Free

What lives inside it#

You'll see that most of the large items are things macOS creates and manages. That is why the instinct to hunt them down and delete them can backfire.

Before you delete anything#

A large System Data figure becomes a problem when you are running low on space, or when the number keeps climbing for no reason. Two quick checks save a lot of effort:

1. Restart your Mac. This clears temporary files and resets virtual memory. Then reopen Storage and wait: the figure can take a minute or more to settle after the window opens.
2. Check the "available" number first. macOS counts some space as purgeable, meaning it will reclaim it automatically when needed. A Mac showing 200 GB of System Data and 60 GB available is in a different situation from one showing 200 GB of System Data and 3 GB available.

Check for local Time Machine snapshots#

If you use Time Machine, macOS can keep local snapshots on your startup disk between backups. They let you restore files even when your backup drive isn't connected, and they show up in System Data.

Apple designs local snapshots to be released automatically when you need the space, so they are rarely the cause of a genuine "disk full" problem. But they explain why the number looks large. To see them, open Terminal and run:

tmutil listlocalsnapshots /

You'll get a short list with dates in the names. If you want to remove one, you can name its date:

sudo tmutil deletelocalsnapshots 2026-10-10-093045

Replace the date with one from your own list. This only removes the local copy; your backup on the external drive is not touched. If you don't have a recent backup elsewhere, skip this and make one first.

Find out what's big, with your own eyes#

Guessing is slow. A few commands in Terminal will show you which folders are large. Start with your own Library folder, where most of the growth happens:

du -xhd 1 ~/Library | sort -h | tail -n 10

This prints the ten biggest folders inside ~/Library, smallest to largest. Common culprits include:

• Caches — temporary data apps create to run faster.
• Application Support — data apps need to keep, including some that grow without limit.
• Containers and Group Containers — sandboxed app data. Docker and some virtual machine tools store their disk images here.
• Developer — Xcode build output and iOS simulators, if you develop software.
• Mail — large if you keep years of attachments locally.

Safe ways to reclaim space#

Work down this list from the top and stop when you have enough room.

1. Empty the Trash. Files in the Trash still count as used space. In Storage → Empty Trash Automatically, you can have macOS do this for you after 30 days.

2. Delete old device backups. If you've backed up an iPhone or iPad to your Mac in the past, those backups can be tens of gigabytes each. Look for them under the iOS Files category in Storage, or in Finder with your device selected.

3. Clear caches for one app at a time. Quit the app, open ~/Library/Caches, and remove the folder belonging to the app that is large. It will rebuild when the app next opens. Leave the Caches folder itself in place. The cache guide lists which caches are safe.

4. Remove developer leftovers. If you use Xcode, old simulator runtimes and derived data can be enormous. Xcode has a setting to manage these, and this command removes simulators that are no longer usable:

   xcrun simctl delete unavailable
   

5. Find duplicate files in Downloads and old project folders with our duplicate-finding guide.

6. Uninstall apps you no longer use, and remove their support folders from ~/Library/Application Support if they left any behind.

7. Let macOS help. Under Storage, review the recommendations such as Store in iCloud and Optimize Storage. These are Apple's own tools, and they are safe because the system knows what it can offload.

When the number keeps growing#

If System Data climbs back up soon after a cleanup, something is actively writing data. Look for these patterns:

• A process stuck in a loop. A misbehaving app can write logs or caches endlessly. Open Activity Monitor, switch to the Disk tab, and sort by Bytes Written. A single process with an unusually high value is your suspect. See our guide to why a MacBook runs slowly for how to read Activity Monitor.
• Heavy memory pressure. When RAM is full, macOS writes to swap files on disk. A Mac that is constantly short of memory will keep swap files large. Closing heavy apps, or adding memory on a Mac that allows it, is the fix.
• A stalled Spotlight index. If Spotlight is rebuilding repeatedly, its index can grow large. As a last resort you can rebuild it with sudo mdutil -E /, then wait for indexing to finish. Expect slowness while it runs.
• Sync or backup tools. Some sync clients keep a local cache that scales with your cloud library.

What about cleaner apps?#

Cleaning apps promise to find and remove System Data for you. Some of them do useful work: they surface large caches and leftover files in a friendlier way than Terminal does. But everything they delete, you can delete yourself, and they can't free space that macOS is managing (like purgeable snapshots) any faster than macOS will.

Treat any claim about "gigabytes recovered" with caution. Our Best Mac Cleaning Software guide compares the main options by the job they do, and the CleanMyMac vs DaisyDisk page covers the best-known pair. For a safe, step-by-step plan that needs no extra app, follow How to Reduce System Data Without Losing Files.

When to stop and ask for help#

If you've cleared the obvious items and System Data is still enormous, or the figure is wildly out of step with what Terminal reports, don't start deleting system files. Instead:

• Make a full backup first.
• Check Disk Utility → First Aid on your startup disk for errors.
• Consider reinstalling macOS from Recovery, which keeps your files and replaces system files only.
• Contact Apple Support if you suspect the Storage screen itself is miscalculating.

Frequently asked questions#

Is it safe to delete System Data?#

System Data is a label that covers many folders, so there is nothing to delete as a whole. You can safely remove specific contents you own, such as old device backups, caches belonging to a single app, and developer leftovers. Leave system folders alone.

Why did System Data jump after a macOS update?#

Updates download installers, create temporary files, and trigger re-indexing. This often settles after a restart and a few hours of idle time. If it doesn't, work through the checks above.

Does restarting reduce System Data?#

Often a little. A restart clears temporary files and resets virtual memory, and it forces the Storage screen to recalculate, which can make the number more accurate.

Will a cleaner app fix this?#

Maybe, but only for things you could also remove yourself. They can't override how macOS handles purgeable space. See the note above.