Why your Time Machine backup is bigger than your Mac — and how to fix it

Q: Why is System Data so large if I use Time Machine?

Time Machine stores local snapshots on your startup disk. These snapshots are invisible in Finder but show up as System Data in storage settings. They're safe to delete if you have your external backup.

Updated September 2026 · 7 min read

You bought a 1 TB external drive for Time Machine. A few months later, it's full — and your Mac only has 400 GB of data. Time Machine doesn't just copy your files. It keeps a history of every version of every file, plus local snapshots on your startup disk. Without a little guidance, it backs up everything — including caches, node_modules, Docker images, and other stuff that changes constantly and doesn't need to be backed up.

Here's how to slim it down.

Why Time Machine backups grow so fast

Time Machine creates incremental backups: the first backup is a full copy of your disk, and each subsequent backup adds only what's changed. The problem is that some files always change:

Developer caches — Docker images, npm caches, build artifacts change on every build
Virtual machines — a VM disk image is one giant file that changes entirely on every use
Application caches — browser caches, Spotify cache, Adobe media cache — gigabytes that regenerate daily
Large creative files — video projects with frequent saves create new versions in every backup

Time Machine faithfully backs up every version of all of these. That's why a 400 GB Mac can fill a 1 TB backup drive in months.

Step 1: Exclude what doesn't need backing up

This is the single most effective thing you can do. Go to System Settings → General → Time Machine → Options. Click the + button to add folders to the exclusion list.

Good candidates for exclusion:

What to exclude	Why
`node_modules` folders	Rebuilt from package.json in seconds
`~/Library/Caches`	Apps rebuild these automatically
Docker data (`~/Library/Containers/com.docker.docker`)	Images re-pull; volumes should be backed up separately
Virtual machine disk images	Single large files that change entirely each session
Xcode DerivedData (`~/Library/Developer/Xcode/DerivedData`)	Rebuild on next compile
Downloads folder (optional)	Usually contains replaceable files

When not to exclude: never exclude your Documents, Desktop, or Photos folders — those contain irreplaceable data. And don't exclude ~/Library entirely — some app data stored there (email archives, notes databases) is important. Exclude specific subfolders, not the whole Library.

Step 2: Remove old local snapshots

Time Machine keeps local snapshots on your startup disk — copies of your files in case the backup drive isn't connected. These are invisible in Finder but can eat 10–50 GB.

To see them:

tmutil listlocalsnapshots /

To delete a specific snapshot:

tmutil deletelocalsnapshots 2026-08-15-120000

For a deeper dive into local snapshots and how they relate to System Data in storage settings, see our Time Machine local snapshots guide.

Step 3: Thin old backups on the external drive

If your backup drive is already full, Time Machine automatically deletes the oldest backups to make room for new ones. But you can speed this up or be more selective.

Open Time Machine (enter Time Machine from the menu bar icon), navigate to old dates, and delete specific large items you no longer need backed up. Right-click a file or folder in the Time Machine browser and select "Delete All Backups of [item]."

This is particularly useful for large files you no longer have — old video projects, VM images, or app installers you downloaded once.

Step 4: Consider a fresh start

If your backup has accumulated years of versioned caches and build artifacts, the cleanest fix is starting fresh:

Set up exclusions first (Step 1)
Erase your backup drive (or use a new one)
Let Time Machine do a fresh full backup with the exclusions in place

The first backup will take a while, but the resulting backup set will be dramatically smaller and future increments will grow much more slowly.

How much should a healthy backup be?

A well-configured Time Machine backup should be roughly 1.5–2x your actual data size after a few months of history. If it's 3x or more, your exclusion list needs work.

Know what's bloating your disk before it bloats your backup

Gigatidy identifies caches, developer junk, and other reclaimable files on your Mac — the same stuff that makes Time Machine backups explode.

Meet Gigatidy →

FAQ

Will excluding folders from Time Machine lose my data?

Only for those specific folders. The key is to exclude only data that can be regenerated — caches, build artifacts, and downloaded packages. Your documents, photos, and actual work should always be included.

Does Time Machine automatically delete old backups?

Yes. When the backup drive runs out of space, Time Machine deletes the oldest backups first to make room. It keeps hourly backups for the past 24 hours, daily backups for the past month, and weekly backups for everything older — purging the oldest weekly backups when space runs low.

Why is "System Data" so large if I use Time Machine?

Time Machine stores local snapshots on your startup disk so it can back up even when your external drive isn't connected. These snapshots are invisible in Finder but show up as "System Data" in storage settings. They're safe to delete if you have your external backup.