How to Reduce System Data on Mac — What It Actually Is and What You Can Safely Remove

You open About This Mac → Storage and see a massive block labeled System Data. It's taking up 30, 40, maybe 50 gigabytes. And there's no breakdown — just the number.

That's frustrating by design. macOS lumps a wide range of files under this single label, which makes it impossible to know what's safe to touch without digging.

Here's what's actually inside, and what you can do about each piece.

What "System Data" Actually Contains

Apple's official explanation is intentionally vague.^[1]

In practice, System Data is a catch-all for anything that doesn't fit neatly into the other categories (Apps, Documents, iCloud Drive, etc.). It typically includes:

• System logs and crash reports — written continuously, can accumulate significantly
• Application cache — apps that don't clean up after themselves
• Time Machine local snapshots — macOS keeps these automatically when the external backup drive isn't connected
• Virtual machine disk images — Parallels, VMware, or UTM images live here
• Container data — Docker images and volumes can take enormous amounts of space
• Leftover app data — support files from deleted apps that never got cleaned up
• iOS app installers — old .ipa files from syncing
• Safari offline storage, extensions data, and website caches

The reason it all gets lumped together is partly that the categories overlap, and partly that macOS doesn't want to expose too much file system detail in a consumer UI. Reasonable decision — but it makes storage management harder.

How to Check What's Actually Inside

The quickest way to investigate: open Finder, press ⌘ + Shift + G, and navigate to these paths one by one.

Logs: ~/Library/Logs and /private/var/log

App cache: ~/Library/Caches

Application support (leftover app data): ~/Library/Application Support

Time Machine snapshots: can't browse directly in Finder — use Terminal

Container data: ~/Library/Containers and ~/Library/Group Containers

Looking at the folder sizes (right-click → Get Info, or use a disk analyzer) will tell you which category is contributing most to the number.

Time Machine Local Snapshots

This is often the biggest hidden contributor.

macOS automatically creates local "snapshots" — a kind of on-device Time Machine backup — so you can restore recent changes even when your external backup drive isn't plugged in.^[2]

These snapshots are supposed to be released automatically when disk space gets tight. In practice, that release mechanism doesn't always kick in fast enough.

To see your local snapshots, open Terminal and run:

tmutil listlocalsnapshots /

To delete a specific one:

tmutil deletelocalsnapshots <date>

Replace <date> with the snapshot identifier from the list output. If you have an external Time Machine backup and don't need local snapshots, you can also disable local snapshotting entirely in Time Machine settings.

System Logs and Crash Reports

Every time an app crashes, macOS writes a report. Every background service produces logs. These accumulate continuously.^[3]

They're safe to delete. Logs are diagnostic data — if you're not debugging a specific crash, you don't need them.

Manual cleanup:

• ~/Library/Logs — application logs, safe to delete
• /private/var/log — system logs, safe to clear but requires admin password

You can also open Console.app, which gives you a UI for browsing logs — but it doesn't help with deletion.

Docker Images and Virtual Machine Disks

If you use Docker, the storage footprint can be significant.

Docker images, build cache, and unused containers all live under ~/Library/Containers/com.docker.docker. A Docker installation that's been running for a year might have 20–30GB in images alone.

In Docker Desktop:

• Go to Settings → Resources → Advanced to see the disk image size
• In Volumes and Images tabs, you can identify and remove unused items
• Run docker system prune in Terminal to remove all stopped containers, unused networks, and dangling images

Virtual machine disk images (Parallels, VMware Fusion, UTM) are even larger — a Windows VM might be 40–80GB. If you've set up a VM and rarely use it, it's worth asking whether you still need it.

Leftover App Data in Application Support

When you delete an app by dragging it to Trash, the app bundle is removed — but the support files it wrote to ~/Library/Application Support usually aren't.^[4]

Over years of installing and uninstalling software, this folder grows into a graveyard of data from apps you haven't thought about in years.

Browse ~/Library/Application Support in Finder and look for folders with names you don't recognize or that correspond to apps you've deleted. If the app is gone, the support folder is safe to remove.

Using an app uninstaller that finds these leftover files when you delete an app prevents this from accumulating in the first place.

Application Cache

~/Library/Caches is technically not always counted in System Data — macOS sometimes attributes it to individual apps. But it ends up in the System Data count frequently enough to be worth checking.

Clearing app cache is generally safe. Apps rebuild their caches as needed. The risk is a temporary slowdown after clearing (the app re-generates what it needs), not data loss.

How Much Can You Actually Recover?

It depends entirely on what's contributing to your number.

If Time Machine snapshots are the culprit, you might recover 10–15GB from that alone. If Docker is the issue, you could get back 20–30GB.

If it's primarily logs and small leftover app data, the number will be lower — but the cleanup is faster and risk-free.

The important thing is not to guess. Checking the actual folder sizes before deleting anything takes five minutes and prevents accidentally removing something that matters.

The Safer Approach

The reason System Data cleanup has a reputation for being risky is that people delete things without understanding what they are.

A practical approach:

1. Check Time Machine snapshots first — often the biggest contributor, lowest risk
2. Clear obvious log and cache folders
3. Use an app uninstaller for leftover support files
4. For Docker/VMs, manage within the app itself
5. Review before deleting anything you don't recognize

Treating System Data as one big blob to delete is how people accidentally break things. Treating it as several distinct categories — each with different risk levels — makes the cleanup both safer and more effective.