Mac Startup Disk Full but Files Add Up to Less Than Capacity? Time Machine Snapshots Are the Culprit

You open About This Mac, see the dreaded "disk full" warning, then add up every folder you can find and come up with 60 or 80 GB less than what macOS claims is used. Your files don't add up to your disk usage, and nothing in Finder explains the gap. The most common reason on modern Macs: invisible local Time Machine snapshots sitting on your internal drive, counted as used space by the operating system but hidden from every normal file browser.

Why macOS Reports More Used Space Than Your Files Explain

When Time Machine is enabled and your backup destination is not currently connected (a wireless drive that is off, an external drive you left at the office, a NAS that is sleeping), macOS creates local snapshots on your startup disk. These are point-in-time copies of your files stored inside a hidden APFS volume. macOS treats that space as used because it is committed to snapshot storage. Finder, however, does not show snapshot volumes in its directory tree, so when you manually total up folder sizes you never see them.

The result is the classic "startup disk full but not full Mac" panic: Disk Utility shows 240 GB used on a 256 GB drive, your home folder plus Applications plus System adds up to maybe 170 GB, and the remaining 70 GB seems to have vanished.

APFS snapshots and how they grow

APFS (the filesystem Apple switched to in High Sierra) supports copy-on-write snapshots natively. Every time you modify a file after a snapshot is taken, the old data stays in the snapshot and the new data is written fresh. A snapshot that was 1 GB at creation can swell to 20 GB or more over hours of normal work. If your Mac goes several days without reaching the backup destination, a queue of snapshots accumulates, each one growing as you continue editing files.

macOS will eventually purge old snapshots automatically when space pressure is extreme, but "extreme" often means the disk is already at 99% capacity and the system is throwing up warnings.

How to Confirm Snapshots Are Eating Your Space

Open Terminal (in /Applications/Utilities/) and run:

tmutil listlocalsnapshots /

You will see output like:

com.apple.TimeMachine.2026-06-08-091423.local
com.apple.TimeMachine.2026-06-09-070011.local
com.apple.TimeMachine.2026-06-10-033017.local

Each line is a snapshot. Three snapshots from three different days means three frozen copies of your file system are sitting on your disk. To see how much space they actually occupy, run:

tmutil listlocalsnapshots / | xargs -I {} tmutil localsnapshot info {}

On macOS Sonoma and later (including Sequoia and Tahoe), a faster command that shows total snapshot usage directly is:

du -sh /.MobileBackups

If /.MobileBackups returns "Operation not permitted" that is normal without elevated privileges. The tmutil path is the reliable one for most users.

Cross-checking with Disk Utility

Open Disk Utility (/Applications/Utilities/Disk Utility.app). Select your internal drive (usually "Macintosh HD" or "Apple SSD"). In the bottom bar you will see a breakdown. On APFS volumes, the "Snapshots" row explicitly lists snapshot storage. If that row shows 30, 50, or 70 GB you have your answer: that is the hidden disk space your files never accounted for.

How to Delete Local Time Machine Snapshots

You can remove individual snapshots or all of them at once. Removing local snapshots does not remove your actual Time Machine backups on the external drive or NAS. Local snapshots are just on-device copies. Your off-device backup history is untouched.

Delete a specific snapshot

tmutil deletelocalsnapshots 2026-06-08-091423

Use the date-time string from tmutil listlocalsnapshots /, without the com.apple.TimeMachine. prefix and without the .local suffix.

Delete all local snapshots at once

tmutil listlocalsnapshots / | grep -oE '[0-9-]{19}' | xargs -I {} tmutil deletelocalsnapshots {}

This extracts the timestamp portion from each snapshot name and deletes them in sequence. Run it, then check System Settings > General > Storage to watch the free space update. On Sonoma and later the storage graph refreshes within a minute.

Via System Settings (no Terminal required)

In System Settings > General > Time Machine, turn off the toggle for "Back Up Automatically." macOS will prompt you to confirm. Once Time Machine is disabled, local snapshot creation stops immediately and existing snapshots are purged over the next few minutes. You can re-enable Time Machine afterward and it will resume normal backups without immediately creating new local snapshots (it waits until the next scheduled backup window).

Why the Files Don't Add Up: Other Hidden Space Consumers

Snapshots are the most common culprit, but a few other categories can contribute to the gap between what you see in Finder and what macOS reports as used.

System Data and caches

The System Data category in System Settings > General > Storage is a catch-all bucket. It includes:

• User caches in ~/Library/Caches (browser caches, app build artifacts, Xcode derived data)
• System caches in /Library/Caches
• Log files in ~/Library/Logs and /var/log
• Virtual memory swap files in /private/var/vm
• Core dumps

None of these show up as "your files" but they all count toward used space. A single Xcode derived data folder in ~/Library/Developer/Xcode/DerivedData can exceed 20 GB on an active development machine.

APFS free space vs. purgeable space

macOS distinguishes between free space (immediately available) and purgeable space (held by caches or low-priority data that can be reclaimed on demand). Finder's "Get Info" on your drive shows both combined as "Available," which is why a disk can look 60% full in Finder but throw a full-disk alert when an app tries to write a large file. The app requested more than the truly free portion, even though purgeable space existed.

Preventing the Gap From Growing Back

A few habits keep the "disk full missing space Mac" problem from recurring:

• Keep your backup destination connected regularly. When Time Machine completes a backup to the external drive or NAS, it purges older local snapshots automatically.
• Set a storage alert. In System Settings > General > Storage, macOS can warn you when space drops below a threshold. Catching the problem at 20% free is much less stressful than at 1%.
• Clear Xcode derived data periodically if you develop on the machine. The safe path to delete is ~/Library/Developer/Xcode/DerivedData. Xcode rebuilds it on next build.
• Prune browser caches. Safari, Chrome, and Firefox each store multi-GB caches under ~/Library/Caches. Clearing them inside the browser preferences is faster than hunting for the folders manually.

Using a Whole-Mac Audit to See the Full Picture

Manually running tmutil commands and totaling folder sizes in Terminal gets the job done but requires knowing where to look. If you want a single view that accounts for snapshots, caches, app leftovers, duplicates, and large files all at once, Crumb runs a whole-Mac audit that surfaces the real breakdown, including snapshot storage, without requiring an account or sending any data off your device. It shows a reviewable plan before removing anything and can answer "is this safe to delete?" for each category it finds.

Either way, the important takeaway is this: a startup disk that reads as full when your files clearly do not add up is almost always a snapshot problem on APFS Macs. It is fixable in under five minutes with the Terminal commands above, and once you see it happen once you will know exactly what to check the next time the storage warning appears.