Blog / macOS

What is System Data on Mac, and what's really inside it

A 212 GB gray bar with no way to look inside. I took it apart folder by folder, with real sizes, and sorted what's safe to clear from what isn't.

The day my Mac froze because it ran out of room, the first thing I opened was Storage settings. I clicked the big gray bar called System Data and waited for a list. Nothing came.

That bar was 212 GB, almost half of a 460 GB disk. When I measured the folders behind it, about 116 GB came from six owners I could name. Almost all of it came from my own developer tools.

TLDRFind the owner first

System Data is the Storage settings label for everything that doesn’t fit Apps, Documents, Photos, or the other categories: caches, logs, swap, app support files, local Time Machine snapshots, and developer tools’ data. You can’t open it or clear it as one thing. On my Mac, about 116 GB of the 212 GB came from six owners, led by iOS simulators and Docker. Find the biggest owner, clear it with that owner’s own tool, and measure the folder again, because on my Mac most deleted simulator files never left the disk.

Why macOS won’t tell you what’s in it

Apple’s guide to finding and deleting files is honest about it. System Data holds files that don’t fall into the other categories, mostly files the system uses, like log files, caches, VM files, and other runtime resources. It also counts temporary files, fonts, app support files, and plug-ins. Then it says: “You can’t manage the contents of this category.”

So there’s no info button, and no list. Before macOS Monterey, the same bar was called Other.

The same page has the line that turned out to be the useful one. You can manage that data, it says, with the Finder or with the third-party apps that created it. Every gigabyte in that bar has an owner, and the owner is who you ask.

System Data isn’t a folder. It’s a total of hundreds of folders spread across your Library, hidden folders in your home, and system locations. The only way to see inside is to measure those folders yourself.

What was inside 212 GB on my Mac

I measured the usual suspects with du -shx, one folder at a time, and sorted them biggest first:

Folder Owner Size Safe to clear?
/System/Library/AssetsV2/…iOSSimulatorRuntime Xcode simulator runtimes 64 GB Old ones, with Xcode’s tool, then check with du
~/Library/Containers/com.docker.docker Docker Desktop 20 GB Review first
~/Library/Caches App caches 12 GB Mostly, apps rebuild them
~/Library/Developer/CoreSimulator/Devices Simulator devices 9.5 GB Unused ones
~/.npm npm package cache 8.4 GB Yes, it downloads again
/private/var/vm Sleep image and swap 2 GB Leave it alone

That’s about 116 GB from six owners, more than half of the gray bar. I write software on this Mac, and my tools had been filling System Data for months, with nothing in macOS cleaning up after them.

The other 96 GB or so is spread across folders this post doesn’t cover. I haven’t put an owner on it.

On a Mac without Xcode or Docker, this table looks different. The method stays the same: find the biggest folders, then find who made them.

How to measure it on your Mac

Open Terminal and run du on the folders above, starting with these three:

du -shx ~/Library/Caches
du -shx ~/Library/Containers/* | sort -h | tail -5
du -shx /System/Library/AssetsV2/com_apple_MobileAsset_iOSSimulatorRuntime

The second command lists your five biggest app containers. Sandboxed apps keep their data there, and all of it counts as System Data.

Don’t skip the -x. It keeps du from counting disk images that macOS mounts inside a folder. Without it, du told me the simulator folder held 186 GB, about 40% of the disk, when the real number was about 64. That mistake is the whole story of how this started.

If the third command prints a big number, that’s AssetsV2, the system folder where Xcode keeps its simulators, and where most of my 64 GB was.

What’s safe to clear, and how

Clear each owner with its own tool, not by dragging folders to the Trash. The owner’s tool knows which of its files can be downloaded or rebuilt later.

Simulators

If you use Xcode, old simulator runtimes are usually the biggest single item. Each one is a full copy of iOS, about 8 GB. Delete the ones you don’t use with Xcode’s own simctl, then check that the space came back.

The 64 GB in the table was eight runtimes, before anyone deleted one. On September 29, six of them were deleted with simctl, and only one, iOS 26.1, left the disk. The other five, 41.6 GB, stayed in AssetsV2 after simctl and Xcode stopped listing them. The folder still measured 57 GB that day.

By October 15, all five were back on simctl’s list, marked Ready. By October 28, iOS 26.5, one of the two kept on September 29, was off the list and its folder was gone from AssetsV2. That’s where the folder’s drop from 57 GB went: du printed 51,553,840 KB, about 49 GB.

That day I deleted four of the five old runtimes a second time. simctl’s total dropped by 32.5 GB. Ten minutes later, du printed the same 51,553,840 KB, and the runtime folders were all still inside AssetsV2. So simctl can say a runtime is gone while its files stay, and only du shows the difference. The AssetsV2 post has every reading from those dates.

Measure before and after

Run du -sk on the simulator folder before you delete a runtime, and write the number down. Run it again afterward. On October 28, simctl’s list was the only thing on my Mac that changed.

Docker

docker system df shows images, containers, and build cache, and how much of each Docker counts as reclaimable. docker system prune removes stopped containers and unused data after asking you to confirm. Docker’s disk use has its own post.

npm

npm cache clean --force empties the package cache. Packages download again the next time a project needs them.

App caches

For app caches in ~/Library/Caches, quit the app first, then clear its folder. If the app has its own setting for clearing its cache, use that instead. Caches rebuild, but a few apps keep state there that you’d rather not lose.

Apple’s guide to storage recommendations also says macOS clears caches and logs that are safe to delete when space is needed. So the 12 GB here is the part I’d chase last.

Leave these alone

/private/var/vm holds swap files and the sleep image, and macOS manages them while your Mac runs. On October 28, it held one file on my Mac, the 2 GB sleepimage, and no swap files. On the day of the freeze, the crash log said “13 swapfiles and LOW swap space”. macOS writes swap when memory runs short, and a full disk leaves it no room to do that. So the fix that day was freeing disk space, and the swap files were left to macOS.

Leave local Time Machine snapshots to macOS too. It removes them on its own when space runs low. You can list them with tmutil listlocalsnapshots / if you’re curious. On October 28, mine listed none.

Questions people ask

Can I delete System Data on my Mac?

Not as one thing. System Data isn’t a folder, it’s a total, and Apple says you can’t manage its contents in Storage settings. You clear it piece by piece, with the tool or app that made each folder.

Why is System Data so big on my Mac?

On my Mac, it was developer tools: iOS simulators at 64 GB and Docker at 20 GB, out of 212 GB. On a Mac without them, start with ~/Library/Caches and ~/Library/Containers, which every Mac has.

Does System Data shrink on its own?

Partly. Apple says macOS clears caches and logs that are safe to delete when space is needed, and macOS removes local Time Machine snapshots when space runs low. It won’t remove simulator runtimes or Docker images for you.

What was System Data called before?

Other. Storage settings called it Other before macOS Monterey.

Where to start

What I’d do first: start with the single biggest folder, clear it with its owner’s tool, and measure again. On my Mac, simulators and Docker alone were 84 GB, more than everything else in the table combined. The caches were 12 GB, and apps rebuild them, so I’d leave them for later.

The one thing I still can’t do is reclaim the space those stuck simulator files take. On October 28, ls -ldO showed both AssetsV2 and its simulator folder marked restricted, which means System Integrity Protection covers them and even sudo rm can’t remove them. I’m not turning that protection off for disk space.

What Diskling shows here

Diskling breaks System Data down by owner, the way the table above does, and says in plain words what each folder is and whether it’s safe to clear. When you clear something, it uses the owner’s own command and measures the disk again afterward, so a delete that freed nothing shows up as one.

Get Diskling

Before you delete anything, run the three du commands above and write the numbers down, then run them again after. On my Mac, that before-and-after number on October 28 is the only reason I know four runtimes never left. If you find a folder you can’t place, ask in the comments and I’ll help you work out what it is.

Know someone with a full Mac? Send them this.
Nazmoon Munny
Nazmoon Munny Chief Overthinker at Dotbrain

I'm the product manager for Diskling, which mostly means asking "but what if" until nothing breaks. I studied soil science before software, and outside work it's family, farming and whatever I'm learning next.

Comments

No comments yet. Tried this on your Mac? Tell me how it went.

Please add your name.

That email doesn’t look right.

Add a few words first.

I read every comment before it shows up.