Fixing 'Startup Disk Full' on macOS When Files Don't Add Up

A Mac reporting a nearly full disk, when the user’s own visible files clearly don’t account for that much space, almost always has space consumed by something not obvious from a casual Finder browse — this walks through finding it systematically.

Step 1: check the actual breakdown Apple provides

 → About This Mac → Storage → Manage

This built-in view categorizes space usage (Applications, Documents, System, “Other”) — a large “System” or “Other” category is the first real signal of where to look further.

Step 2: check for accumulated local Time Machine snapshots

tmutil listlocalsnapshots /

Local snapshots normally thin themselves automatically as space is needed, but a system under sustained heavy write load can occasionally accumulate more than expected — checking directly rather than assuming automatic thinning is keeping up is worth doing when space is genuinely tight.

Step 3: check for large caches and logs

du -sh ~/Library/Caches/*
du -sh /private/var/log/*

Application caches and system logs can grow substantially over time, especially for apps with bugs in their own cache-management logic — this is usually safe to clear, though clearing caches will make some apps briefly slower on next launch while they rebuild them.

Step 4: check for large, forgotten disk images or VM files

find ~ -name "*.dmg" -size +500M
find ~ -name "*.vdi" -o -name "*.vmdk" -size +1G

Downloaded installer disk images and virtual machine disk files are both individually large and easy to genuinely forget about once you’ve finished with them.

Step 5: check iOS/iPadOS backups stored via Finder or Xcode

du -sh ~/Library/Application\ Support/MobileSync/Backup/*

Local device backups can silently consume tens of gigabytes and are easy to overlook since they don’t appear in an ordinary home-folder browse.

Step 6: use a dedicated disk-usage visualizer for anything still unaccounted for

du -sh ~/* 2>/dev/null | sort -rh | head -20

Running this at the home directory level, and then recursively into whichever folder turns out largest, narrows down a mystery consumer far faster than browsing Finder folder by folder.

Step 7: check for APFS space shared between multiple volumes

On an APFS container with multiple volumes (common on modern Macs, splitting Data from System), free space is shared across all volumes in the container — a large file on one volume affects free space reported for every volume sharing that container, which can make “why does the System volume show so little free space” confusing until this shared-pool behavior is understood.

Why “Other” and hidden system data account for more than people expect

macOS’s own housekeeping — caches, logs, snapshots, backups — genuinely can consume tens of gigabytes without any single item looking alarming on its own, which is exactly why manually adding up visible Documents/Desktop/Downloads sizes rarely matches the reported total. Working through Steps 2 through 5 systematically, rather than assuming a single large hidden file is responsible, is what actually finds where the space went in most real cases.

Understanding “purgeable” space specifically

Some of what df or About This Mac reports as used is actually labeled purgeable — space macOS is holding onto for things like optimized Photos originals already backed up to iCloud, or old iOS device backups, that the system can reclaim automatically the moment free space genuinely runs low. This is deliberate lazy cleanup, not a bug: macOS would rather keep that data available for as long as there’s room to spare (in case you need it) than delete it prematurely, which is why available space sometimes appears to increase substantially, without any explicit action from you, the moment a large file copy actually needs the room.

diskutil apfs list | grep -A2 "Capacity In Use"

diskutil apfs list shows a container’s actual capacity breakdown, including purgeable space, more precisely than the simplified df or Finder view — useful for confirming that a large “missing” chunk of space is genuinely purgeable and will free up under pressure, rather than being permanently and irreversibly consumed by something you still need to go find and delete manually.

When iCloud Drive’s “Optimize Mac Storage” setting is the actual cause

If Photos or iCloud Drive is configured to keep only optimized, smaller versions locally while storing full-resolution originals in iCloud, disabling that optimization (to keep full originals locally instead) can unexpectedly consume far more local disk space than users forecast when they made that change — worth checking System Settings → Apple ID → iCloud for exactly which services have local-storage optimization turned off, particularly Photos, since a large photo library kept in full resolution locally is one of the single largest, easiest-to-overlook space consumers on a storage-constrained Mac.

Related:

Sources: