First, confirm which volume is full

Open System Settings → General → Storage and select All Volumes. APFS containers can share capacity, so the startup volume and a neighboring volume may draw from the same pool.

Treat the category chart as orientation, not a folder map. Categories such as System Data group many unrelated files and do not always expose the paths behind the total.

The most common places where space accumulates

  • Photo, video, music, and creative-project libraries
  • Downloads, archives, installers, and forgotten disk images
  • Application Support data, device backups, Mail, and Messages attachments
  • Xcode DerivedData, simulators, package caches, node_modules, and build output
  • Docker or virtual-machine disk images that can be sparse files
  • Trash, local snapshots, caches, logs, and other runtime data

A safe four-step investigation

  1. ScanMap the complete startup disk or the largest accessible folder. Grant Full Disk Access only if you want protected locations included.
  2. RankBegin with the largest top-level folders. One 80 GB library matters more than hundreds of tiny cache entries.
  3. InspectOpen the path in Finder, identify the owning app, and check whether the data is replaceable, backed up, or still needed.
  4. Remove safelyPrefer Trash, close the app that owns the data, and never delete an unfamiliar system path merely because it is large.

Why Finder and a disk analyzer can show different totals

Apparent file size, physically allocated blocks, hardlinks, APFS volume layout, purgeable capacity, snapshots, permissions, and cloud placeholders can all change what a number means. A trustworthy scan labels exclusions and makes its sizing mode explicit.

Storage Map uses allocated size by default, deduplicates hardlinks, treats the APFS Data volume deliberately, and leaves excluded locations visible instead of silently presenting an incomplete total as complete.

Primary sources

Product and platform facts were checked against these first-party references: