What is actually inside macOS System Data

Open System Settings, then General, then Storage, and you get a bar graph with a category called System Data. On a Mac with 100GB of free space missing, that bar is almost always where the answer is hiding. Apple gives you a category and a number, never a path, which is why the label has a reputation for being useless.

In practice System Data is a bucket for everything macOS cannot classify as an app, a document, a photo or a message. It is not one thing, and it is not all undeletable. Here is what is in it.

1. Application caches

Under ~/Library/Caches, every app keeps its own temporary storage. Browsers are the worst offenders, followed by chat clients and music apps. Measure the top contributors:

du -sh ~/Library/Caches/* 2>/dev/null | sort -hr | head -15

Ten to forty gigabytes is common on a machine in daily use for a year. These files are rebuildable, which is why this is the safest place to start.

2. Local Time Machine snapshots

This is the contributor that surprises people most. macOS takes local APFS snapshots between backups, and each one holds a frozen copy of your disk state. Delete a 20GB file and the space may not come back, because a snapshot still references it.

tmutil listlocalsnapshots /

Snapshots expire, but not quickly. If you see several from the past week and you need space now, they can be removed specifically:

sudo tmutil deletelocalsnapshots 2026-08-14-093012

Only do this when an external Time Machine backup exists. Snapshots are your local rollback if something goes wrong.

3. Swap and virtual memory

When memory fills up, macOS writes to disk. The swap files live in /private/var/vm and are sized in multiples of your RAM, so heavy use with many apps open can hold several gigabytes.

ls -lh /private/var/vm

Swap files shrink after a restart, and they are managed entirely by the system. If your swap file is large and stays large, the useful conclusion is not to delete it but to notice you are short on memory. macoptimize's Status tab tracks swap against memory free for exactly that reason.

4. Application Support

Not cache. Persistent data such as mail databases, save games, editor state and device backups. This is the folder to treat with respect.

du -sh ~/Library/"Application Support"/* 2>/dev/null | sort -hr | head -15

One entry is worth checking on almost every Mac: ~/Library/Application Support/MobileSync/Backup holds local iPhone and iPad backups, frequently 30GB to 80GB each, including backups of devices you no longer own.

5. Logs and diagnostics

du -sh ~/Library/Logs /var/log 2>/dev/null

Usually small, occasionally not. Old crash reports and installer logs accumulate for years without anyone reading them.

6. Developer caches that count as System Data

Xcode DerivedData, Docker disk images and simulator runtimes all sit under hidden folders in your home directory, so macOS files them under System Data rather than Documents or Applications. On a developer Mac this is usually the largest single contributor, and the guides for Xcode, Docker and Android cover each one individually.

7. Spotlight and Photos working data

Search indexes, thumbnail caches and Photos libraries in progress all land in the same bucket. Spotting these is easy because they appear after a large import or a major OS update, then settle down.

A sane order of attack

1. Local snapshots, because they hold space without holding files you can see.
2. Caches in ~/Library/Caches, sorted by size.
3. Device backups under MobileSync.
4. Developer caches such as Xcode and Docker.
5. Logs and diagnostics last, because the payoff is usually small.

How to measure System Data honestly

Apple's Storage panel does not offer a drill down, so the way to see inside System Data is to measure the folders that make it up. Quit heavy apps first, then run this and read the sorted list:

du -sh ~/Library/Caches ~/Library/Logs ~/Library/Application\ Support ~/Library/Containers ~/Library/Developer ~/private/var/vm 2>/dev/null | sort -hr
tmutil listlocalsnapshots /
du -sh /Library/Updates 2>/dev/null

Three notes on reading the output. Some folders need elevated access and report partial sizes, the snapshot list has no size column at all, and swap lives in /private/var/vm where it is managed by the kernel rather than by you. Together those explain why System Data is described as a category rather than a location.

What System Data is not

Worth clearing up, because it causes most of the confusion in Apple support threads:

• It is not your Photos library, your Music library or your documents. Those are counted separately.
• It is not iCloud. Whatever is stored in iCloud is measured on Apple's servers and only the local copy appears here.
• It is not a folder you can open in Finder and empty. It is a label macOS applies to everything it cannot place in a named category.
• It is not fixed. The number moves by gigabytes during an afternoon, because caches are written and dropped, and snapshots are created hourly.

Why it grows after an update

macOS updates produce a predictable spike. The installer download lands in /Library/Updates, prepares an installation, and leaves the remains behind after restart. At the same time Spotlight reindexes, Photos rebuilds its libraries, and Xcode and other tools regenerate caches with the new system version. Two weeks later most of it has been cleaned automatically, and the part that has not is usually an installer you can safely remove.

An audit worth running twice a year

• Measure the folders listed above and write the numbers down.
• List local snapshots and thin them if the count is high.
• Check /Library/Updates for leftover installer files.
• Clear the caches you can regenerate, and leave Application Support alone unless you recognise the folder.
• Reboot, wait ten minutes, and measure again. Reboots release more than any single delete.

Repeat it in six months and compare. A category that grew by 40GB in that time is worth investigating, while one that moved by two gigabytes is just macOS doing its job.

FAQ

Is it safe to delete System Data?

No, and there is nothing named System Data to delete. It is a summary label. The safe work is deleting the specific folders behind it: regenerable caches, leftover installers and old snapshots, while leaving Application Support, Mail data and Photos libraries alone.

Why did System Data jump after an update?

Software updates leave a downloaded installer in /Library/Updates, Spotlight rebuilds its index, and Photos rebuilds library previews. Each of those is temporary by design, and most of the space returns within a couple of weeks. The leftover installer file is the one part worth deleting by hand.

Does System Data include my files?

Not in the way people fear. Your documents, photos, music and videos are counted in their own categories. System Data holds caches, logs, snapshots, swap, application support files and anything macOS could not classify, which occasionally includes virtual machine images and large app databases.

Can I clear System Data from Finder?

Partially. Finder can show hidden folders once you toggle them with Shift Command Period, and you can empty ~/Library/Caches by hand. The parts that matter most, local snapshots and swap, are not Finder items at all and need Terminal commands.

How long should I wait after an update before worrying about the number?

Two weeks is a fair window. Indexing, snapshot thinning and cache rebuilds all settle in that time. If the category is still large three weeks later, run the audit in this guide and look for a leftover installer or a developer cache that grew into it.