How to Find Large Files on Mac (and Safely Remove Them)

The fastest way to find what is eating your disk is to measure it, not to browse Finder folder by folder. But before you go hunting, it helps to know why a Mac so often reads as full when the files you can see do not add up to the number. The answer is usually space you cannot see in Finder at all, and a couple of commands expose it.

Here is how disk space is really accounted for, how to measure it, and how to find the large items safely.

Why your disk is full but the files don't add up

Modern Macs use the APFS file system, and APFS reports space differently from what Finder shows. Two categories hide gigabytes:

  • Local snapshots. Time Machine keeps point-in-time snapshots of your disk on the internal drive between backups. They pin the space of files you have already deleted, because the snapshot still references them, until macOS thins them. List them with:

tmutil listlocalsnapshots /

  • Purgeable space. APFS marks caches, local snapshots, and re-downloadable content as purgeable: space macOS reclaims on its own when something needs it. macOS can count this as available, and Finder may include it in the available total. You cannot reliably clear it by hand.

Check the numbers with:

df -h /
diskutil apfs list
diskutil apfs listSnapshots /

df reports what the mounted file system considers used and available. diskutil apfs list shows the shared container, its volumes, and remaining capacity. diskutil apfs listSnapshots / lists snapshots attached to the startup volume. When Finder says the disk is fuller than your files explain, these views help separate ordinary file usage from snapshots and shared APFS capacity.

Measure real usage from the command line

To find the heavy folders, du (disk usage) is the core tool. From your home folder:

du -sh ~/* ~/Library 2>/dev/null | sort -h

-s gives a summary per item, -h prints human-readable sizes, and piping to sort -h puts the biggest last. Drill into whichever line is largest by pointing du one level deeper, for example du -sh ~/Library/* | sort -h. Two things to know about du: it counts a hard-linked file once, not per link, and on APFS, cloned files (copies that share storage until changed) can make a folder look larger than the space it truly occupies.

To find individual large files instead of folders, find filters by size:

find ~ -type f -size +500M 2>/dev/null

That lists every file over 500 MB under your home folder, which catches forgotten video exports, disk images, and virtual machine files. For an interactive map in the terminal, ncdu (install with brew install ncdu, then run ncdu ~) walks a folder and lets you browse it sorted by size, deleting from inside it.

Reclaim the hidden space

If snapshots or purgeable space are the problem rather than a single file, reconnecting your Time Machine drive prompts macOS to thin local snapshots, and freeing real space elsewhere lets it purge the purgeable category on its own. You rarely need to force this by hand; giving the system room is usually enough.

A visual map, when a list is not enough

A disk analyzer showing the whole disk as a treemap: Library fills the largest block at 155.84 GB, with www, Downloads, and other user folders sized as smaller blocks beside it.
A treemap of the whole disk: the largest folders are the largest blocks, and a click drills into any of them. This is Mole's Analyze view.

Sizes in a terminal are precise but hard to hold in your head across a whole disk. A treemap solves that by drawing every folder as a rectangle scaled to its size, so the largest things are the largest blocks and one glance shows where the weight sits. Mole's Analyze view is a GUI version of the du walk above: it maps the whole disk from the root, drills in on a click, and lets you reveal an item in Finder or send it to the Trash (from the right-click menu, with a size confirmation, and always recoverable). Navigational roots like your home folder have no delete option, so a misclick cannot remove something structural. Use whichever you prefer; the treemap and the commands answer the same question.

A disk analysis pipeline that walks directories, measures files, aggregates folder sizes, and renders a treemap while skipping excluded paths
A disk map walks the tree, measures leaf files, adds sizes from children to parents, then maps each folder total to area.

What is safe to remove once you find it

Finding a large item is not permission to delete it. Decide with one rule:

  • Clearly safe: old installers and disk images, finished exports you have backed up, and caches. If a big folder turns out to be leftovers from an app you removed, uninstall it completely to clear the whole trail at once.
  • Leave alone: active app libraries (Photos, Mail, Messages), device backups you still want, anything under /System, and any file whose purpose you cannot explain.

For the wider cleanup beyond single large files, see how to free up space without losing files.

The short version

A Mac reads as full partly because of space Finder never shows plainly: APFS snapshots and purgeable data. List the snapshots with tmutil listlocalsnapshots or diskutil apfs list. To find real weight, measure folders with du -sh piped to sort -h, hunt big files with find -size +500M, or map the disk with a treemap. Then delete on the same rule every safe cleanup uses: remove what you can identify, leave what you cannot, and keep it recoverable in the Trash.