Storage guide

How to find what is taking up space on your Mac

A nearly full Mac does not automatically mean you have one giant file to remove. Storage can be spread across applications, downloads, project folders, exact duplicates, local snapshots, caches, and cloud files that are not fully available on disk.

1. Confirm whether the startup disk is actually under pressure

Check total capacity, used space, and available space first. A disk that is close to full can leave macOS less room for temporary files, updates, virtual memory, and application work. The exact point at which this becomes noticeable varies by workload, so use the percentage as evidence rather than a universal diagnosis.

If free space is changing quickly, compare more than one reading. A download, photo sync, development build, or backup process can alter the result while you scan.

2. Measure broad sources before opening individual files

Review your home folders, Applications, and any external or network storage that matters to the question. The useful first result is a ranked set of sources: which areas are large, which were measured completely, and which were partial or unavailable.

With Tend's Storage Explorer, choose a source and drill into its subfolders. Long measurements are cancellable, symlinks are not followed, and permission or timeout gaps stay visible. That makes the result easier to trust than a list that silently skips inaccessible paths.

3. Separate applications from personal files

Large applications can be straightforward candidates, but size alone is not enough. Review the app name, location, version, architecture, last-use evidence when available, receipt, and signing information. If you no longer need an app, use its own uninstaller when the vendor provides one, or move it to the Trash through a reviewed workflow.

For personal files, look at Downloads, Documents, Movies, Desktop, and project folders. Large-file review should show the path, size, age, and type, then let you use Quick Look or Reveal in Finder before taking action.

4. Distinguish exact duplicates from similar photos

Exact duplicates have the same file content and can be verified with a cryptographic hash. Similar-looking photos are different files that require perceptual comparison and human review. Keep these categories separate: two edited images can look alike without being interchangeable.

When reviewing a duplicate group, keep the copy in the location you understand, verify that another application is not depending on a specific path, and remove one file at a time to the Trash.

5. Account for cloud files and snapshots

A cloud folder may contain placeholders that represent remote content without consuming the full logical size locally. Make files locally available before expecting a filesystem scan to measure them. Likewise, APFS and Time Machine snapshots can share blocks, so a listed logical size is not always equal to immediately reclaimable disk space.

6. Turn the result into a review queue

1. Start with the largest fully measured source.
2. Review files you recognize and can recreate or download again.
3. Use Quick Look before moving a personal file.
4. Prefer Trash-based actions over permanent deletion.
5. Measure free space again after the action finishes.

The number of bytes moved and the observed free-space increase may differ because of shared blocks, purgeable data, caches, and concurrent system activity. Record both instead of claiming every moved byte as recovered capacity.