How to shrink Mac System Data

Where System Data really goes: the macOS Storage bar with every other category blurred and the System Data segment highlighted at 142.81 GB.

Apple's Storage bar shows a gray slice called System Data. On older macOS it was often labeled Other. People open that screen, see 80 GB or 300 GB sitting there with no Delete button, and assume the operating system itself is broken.

It usually isn't. System Data is a catch-all category, not a folder. Apple puts almost anything that doesn't fit Applications, Documents, Photos, Mail, Messages, iOS Files, or the separate macOS row into that bucket, so the way to clear it is to find what feeds it: local Time Machine snapshots, app data in Library, developer caches, and leftovers. This guide walks through what that means on a real Mac, how to find the bulk, and what is safe to remove by hand. You can follow every step without installing anything.

What Apple says System Data is

Apple's Storage settings guide defines it like this:

Contains files that don't fall into the categories listed here. This category primarily includes files and data used by the system, such as log files, caches, VM files, and other runtime system resources. Also included are temporary files, fonts, app support files, and plug-ins. You can't manage the contents of this category.

Apple Support · Storage settings

Apple's free-up-storage article also calls it System Data (or Other) and says it measures space used by Apple and third-party files that don't belong in a more specific category.

Apple also stresses a few practical points:

  1. Categories are not Finder folders. The gray bar is a Spotlight-style grouping, not a directory named System Data.
  2. There is no manage button for this category. Documents, Messages, and iOS Files have ones. System Data does not.
  3. macOS is a separate row. Core OS apps and files sit there. System Data is not "the whole operating system."

Apple sources: Storage settings, Free up storage space, Optimize storage.

Every Storage category, in Apple's words

System Data only makes sense next to the other rows. This is Apple's list from the Storage settings guide, in short form. Your Mac shows only the rows it has data for.

CategoryWhat Apple says it holdsApple's group
ApplicationsEvery app installed on your Mac, not counting system apps.File type
DocumentsFiles in your home folder that fit no other category, such as Pages files and PDFs. Also photos and videos your photo library does not manage, like an image sent by AirDrop.File type
iCloud DriveFiles stored in iCloud Drive. This can include Desktop and Documents if you keep them there.File type
iOS FilesiPhone and iPad backups and firmware.File type
TV, Music, Books, PodcastsPurchases from each app. You can remove them and download them again.File type
MailEmails and attachments.File type
MessagesMessages conversations, including attachments.File type
Music CreationContent from GarageBand, Logic, and MainStage.File type
PhotosYour System Photo Library.File type
TrashItems you deleted. Items deleted from iCloud Drive are not counted.File type
Other Users & SharedFiles created, changed, or shared by other user accounts on your Mac.Size only
macOSmacOS system apps and files, such as Mail, Terminal, and Calculator.Size only
System DataFiles that fit none of the categories above. Mostly logs, caches, VM files, and other runtime files, plus temporary files, fonts, app support files, and plug-ins.Size only

Apple splits the rows into two groups. In a file type category you can open the list, select a file, and click Delete. The last three rows only show how much space they use. There is nothing to select in them.

Other Users & Shared is easy to miss. If anyone else has an account on your Mac, their files land there, not in your Documents. Step 4 below covers accounts that were deleted but left files behind.

You may also see a Developer row. Howard Oakley notes it appears when Xcode is installed. Apple's list does not include it. Source: Apple, Change Storage settings on Mac.

Why the number feels wrong

Start with how System Data is counted. Howard Oakley (Eclectic Light) explains that Storage adds up the other categories and subtracts that from the space in use. System Data is whatever is left, so he calls it "only approximate, a rough estimate". The other categories miss things too. In his test, his Music folder held over 100 GB of audio, but Storage counted less than 50 GB of it as Music. The rest most likely fell into System Data (What is System Data in Storage Settings?). For a free space figure you can trust, he suggests Disk Utility. Select the container, not the volume, and read the free space shown there.

Free space and available space are different numbers. Free space is empty. Available space is free space plus purgeable caches and similar data macOS claims it can drop when needed, so the same disk space can be both "used" and "available" at once. That is why one screen looks full while another still says you have room.

Local Time Machine snapshots are the second reason. When automatic Time Machine backups are on, macOS also keeps short-lived backups on the Mac itself. Apple says it counts snapshot space as available, keeps roughly a day of hourly snapshots, and removes them when space is needed (see About Time Machine local snapshots).

On a 256 GB SSD that design often fails people in practice. Installs fail, sync tools complain, and the Storage bar still shows a huge System Data slice. Howard Oakley (Eclectic Light) has documented that purging snapshots can fail outright, and that local snapshots cover the whole volume. Time Machine exclusions do not shrink those local snapshots, so a large Docker disk image or VM you excluded from the backup set can still inflate snapshot private size.

The third reason is plain mislabeling. Local iPhone and iPad backups belong under iOS Files when Spotlight classifies them correctly, not under System Data, and Photos, Mail, and Messages have their own rows. People still say "System Data" for anything gray or anything they cannot find in Finder.

How to see what System Data contains

Storage settings will not open this category. Apple's guide says you can't manage its contents from that screen, because it is not a folder. You can still name the pieces by looking at what Storage leaves out.

du -hd 1 ~/Library | sort -h du -hd 1 ~/Library/Containers | sort -h du -hd 1 ~/Library/Application\ Support | sort -h du -sh ~/Library/Developer ~/Library/Caches 2>/dev/null

Read the last lines. A Docker disk image, a virtual machine, or an app container you recognize is a real owner. A container for an app you still use can hold that app's data, so this is a map, not a delete list.

The three checks will not add up to the Storage number. Apple counts local snapshot space as available, and du reports files you can see, not blocks that exist only in a snapshot. If Library is modest and Disk Utility shows large snapshot sizes, the gray bar is snapshots. If the snapshots are small and one Library folder is not, that folder is the owner.

A diagnostic order that matches real Macs

Work top to bottom. Stop when you have freed enough space. Jumping straight to deleting ~/Library/Caches is the most common waste of time when System Data is in the hundreds of gigabytes.

1. Note the size, empty Trash, restart

Open System Settings → General → Storage. Write down the System Data figure. Empty Trash. Restart once. Some temporary files and caches clear on their own. If the number barely moves, keep going.

2. Check local snapshots first

If Time Machine automatic backups are enabled, local snapshots are the usual cause of "mystery" System Data in the 100 GB+ range. Apple's local snapshots article is the method to start with. On macOS Ventura 13 or later:

  1. Choose System Settings from the Apple menu, click General, then click Time Machine. (Or choose Time Machine Settings from the Time Machine menu in the menu bar.)
  2. Click Options, choose Manually from the Backup Frequency menu, then click Done.
  3. Wait a few minutes for local snapshots to be deleted.
  4. Turn automatic backups back on. Time Machine remembers the backup disks it was using.

On macOS Monterey 12 or earlier, the same article says to deselect Back Up Automatically, or use the Off/On switch, wait, then turn backups on again.

To see the snapshots before you change the setting, list them for the startup volume. The tmutil manual says listlocalsnapshots lists local Time Machine snapshots of the mount point you pass:

tmutil listlocalsnapshots /

Names look like com.apple.TimeMachine.2011-07-03-123456.local, the form in that manual. The command does not print byte sizes. For those, use Disk Utility's Private Size column, above.

If you want some space back without turning backups off, the manual's thinlocalsnapshots verb thins snapshots on a volume. When you pass a purge amount and an urgency, it attempts, at urgency 1 through 4, to reclaim that many bytes. The manual does not say which end of 1 to 4 is more aggressive, and it does not promise the purge amount will actually be freed. If you omit both, it says the default urgency is used.

tmutil thinlocalsnapshots / <bytes> <urgency>

<bytes> is a number of bytes, not gigabytes. Run tmutil listlocalsnapshots / again afterwards and check Storage.

To remove one snapshot, take the date out of its name. The manual says deletelocalsnapshots deletes every local snapshot for a date formatted YYYY-MM-DD-HHMMSS when you pass a date, and every local snapshot on a disk when you pass a mount point. Pass the date. Passing / removes all of them.

tmutil deletelocalsnapshots YYYY-MM-DD-HHMMSS

The manual says several tmutil verbs need root and Full Disk Access for Terminal. It does not mark listlocalsnapshots or thinlocalsnapshots that way. If a command is refused, grant Terminal Full Disk Access under System Settings → Privacy & Security and try again.

Deleted snapshots are gone. They do not go to the Trash, and you lose those local restore points. Keep an external Time Machine or other backup before you force them away. Apple's article still prefers the Manual frequency toggle over deleting snapshots by hand.

After snapshots drop, check Storage again. This is where a lot of 300 GB System Data cases collapse to something ordinary.

Purge shows the same local snapshots on Overview. Remove deletes older ones after you confirm, runs tmutil deletelocalsnapshots, and keeps the newest snapshot and the one from your last backup. Removed snapshots are gone for good; they do not go to the Trash.

3. Use the categories that do have a manage button

Still in Storage, open:

These are official Apple paths. They are safer than digging in Library folders. Apple's free-up-storage article covers Store in iCloud, Optimize Storage, Empty Trash automatically, and reviewing large files.

The same Apple article lists two Mail commands. If you use the Mail app, choose Mailbox > Erase Junk Mail from the menu bar, then Mailbox > Erase Deleted Items. Look through Junk for real mail first. These shrink the Mail row, not System Data, but on a full disk every row counts.

4. Check /Users for old accounts

Apple's free-up-storage article says to check the Users folder on Macintosh HD for data left by deleted users, and for shared files you no longer need to share. Space used by other accounts shows up as Other Users & Shared, a row with no Delete option.

What you find depends on how each account was deleted. In Apple's steps, you choose System Settings, click Users & Groups, click the Info button next to the user, then click Delete User. macOS then offers three options:

So the first two choices leave the data on disk. In Finder, choose Go > Go to Folder and enter /Users. Look for a Deleted Users folder, and for home folders of people who no longer have an account. Apple says a kept home folder lets you restore that user later. Check with the person before you remove it, then empty the Trash.

5. Inventory Library for owners you recognize

Open Finder, go to your home folder's Library (hold Option and use Go → Library if it is hidden). Sort by size where you can, or use a disk inventory tool you trust, and look at:

Recurring heavy owners on real Macs:

Delete only what you can name. A container for an app you still use can hold chat history, local databases, or license data. Removing an entire Containers tree is how people break apps.

6. Developer branch (skip if you are not a developer)

Regenerable build junk often hides in System Data because Spotlight does not put it under Documents.

Common targets (quit the related apps first):

DerivedData and package caches come back when you build again. That is the point. They are safe to clear when you need the space. For a step-by-step cleanup order, see the Xcode Storage Guide. App and browser caches are a separate pile, covered in how to clear cache on Mac.

7. Clear Safari's website data

Websites store cookies and other website data on your Mac. Storage settings has no Safari row, so you will not see this space named anywhere. Apple's steps:

  1. Open Safari.
  2. Choose Safari > Settings, then click Privacy.
  3. Click Manage Website Data.
  4. Select one or more websites, then click Remove or Remove All.

Apple warns that this may sign you out of websites or change how they behave. It also notes that removing this data in Safari may change or remove it in other apps. Remove the sites you no longer use before you reach for Remove All.

8. Leftovers from uninstalls last

Only after the steps above, remove support files for apps you are sure you deleted and whose folder names you recognize. Prefer the app's own uninstall path when it has one.

What usually works

SituationLikely causeFirst move
System Data jumped after days of Time Machine useLocal snapshotsSet TM to Manual briefly (Apple's method)
Disk inventory shows a huge Docker or VM fileUncategorized app dataCheck Docker.raw's real size, then move or prune inside that app; consider storing VMs on a volume you exclude from TM if Oakley's advice fits your setup
You develop on a 256 GB MacDerivedData, simulators, node_modules, DockerClear regenerable build artifacts
System Data is "only" tens of GBCaches, logs, tempsRestart, Safe Mode once, clear app caches from each app's UI
Storage shows a big iOS Files sliceOld device backupsFinder → device → Manage Backups

VM files: swap and sleepimage

Apple's definition of System Data names "VM files". VM stands for virtual memory. On a Mac these are swap files and the sleep image. Both belong to macOS, and both look like easy gigabytes to delete. Leave them to the system.

Swap files

When memory runs short, macOS writes pages of memory it has not used lately to disk. Howard Oakley describes this swap space as dedicated storage that, in recent macOS, sits on its own hidden volume named VM (Caches, buffers and swap). On a current Mac that volume is mounted at /System/Volumes/VM, and the files are named swapfile0, swapfile1, and so on.

To see how much swap is in use, open Activity Monitor, click Memory, and read Swap Used at the bottom. Or run this. It only reads a number:

sysctl vm.swapusage

Do not delete swap files by hand. The system is using them while the Mac runs. In one Ask Different thread, an answer says not to touch them, and the person asking found that a restart cleared all but one small file. That is the safe fix. Quit the apps using the most memory, or restart.

sleepimage

/private/var/vm/sleepimage is the hibernation file. To see where your Mac keeps it, run:

pmset -g | grep hibernatefile

The pmset manual explains what it is for. On laptops, hibernatemode is 3 by default. The Mac saves a copy of memory to disk when it sleeps and keeps memory powered. If power runs out during sleep, it restores from that copy instead of losing your open work. On desktops the default is 0, which does not back memory up to disk, though standby can still write an image on desktops that support it.

Deleting the file by hand does not turn this off, and one Ask Different answer warns it can be created again. The supported switch is hibernatemode in pmset, which the manual marks "Please use caution". On a laptop, the file is your safety net when the battery dies during sleep. Leave it.

What not to do

Prevention that is not a cleaner upsell

Doing it with an app

Purge can list the regenerable caches and leftovers above and move them to the Trash, so you can put them back. It will not clear the System Data category in one click. Local Time Machine snapshots are the exception: deleting one is permanent, not a Trash move. Everything it does, you can also do by hand with the steps above.

Frequently asked questions

Is it safe to delete System Data on a Mac?

There is no System Data folder to delete. The category is a grouping of files Apple does not file elsewhere, so the safe route is to shrink what feeds it: local Time Machine snapshots, large app data in Library, developer caches, and leftovers from deleted apps. Deleting whole Library folders or anything under /System is how people lose app data or break macOS.

How much System Data is normal?

Apple publishes no normal size. On most Macs it sits in the tens of gigabytes. When it reaches 100 GB or more, one or two owners usually explain it: local snapshots, a Docker or virtual machine disk, or Xcode and package caches on a developer Mac.

Why does System Data shrink after a restart?

A restart clears temporary files and some caches, and gives macOS a chance to drop purgeable data and expired local snapshots. If the number barely moves, the space is held by something that survives a reboot, which is what the diagnostic order above is for.

Does System Data include Time Machine local snapshots?

In practice it often does. Apple says snapshot space counts as available, but the Storage bar's accounting is inconsistent, and many 100 GB-plus System Data figures drop sharply once snapshots are removed. Check them before anything else.

How do I see what System Data actually contains?

Storage settings will not open the category. Compare the other rows, then look at APFS snapshots in Disk Utility (View > Show APFS Snapshots, and the Private Size column) and measure ~/Library with du. tmutil listlocalsnapshots / lists local Time Machine snapshot names. It does not print their sizes.

What is Other Users & Shared in Mac storage?

Apple says it holds files created, changed, or shared by other user accounts on your Mac. Like System Data, it only shows a size, with no files to select. If it is large, check the Users folder on Macintosh HD for home folders of deleted accounts and for a Deleted Users folder, which holds disk images saved when an account was deleted.

Can I delete swap files or the sleepimage file?

Leave both to macOS. Swap files hold memory the system is using, and a restart is the safe way to clear them. sleepimage is the copy of memory a laptop restores from if power runs out during sleep. Deleting it by hand does not turn hibernation off. The pmset hibernatemode setting controls it, and its manual says to use caution.

Sources