A disk analyzer can undercount storage if it cannot read protected folders or is scanning a smaller location than you expect. Start by checking the scan root and access errors. A small result does not prove that the missing space is mysterious junk.
This guide is for an incomplete scan. If every tool can see the files but reports a different total, also review our guide to differing Mac storage measurements.
Check the location being measured
Compare the exact scan target with the volume shown in macOS Storage. A scan of your home folder will not include every other user’s data or every application installed elsewhere. Likewise, an external SSD scan should not be compared with the internal startup volume’s total.
Write down the scan root, excluded locations, and completion time. If the tool stopped early or skipped directories, those details are more useful than the large headline number on its dashboard.
Look for access errors
Apple’s macOS file-access security guide describes controls protecting locations such as Documents, Desktop, removable storage, and other sensitive data. Access to a folder in Finder does not mean every third-party application has equivalent access.
- Review the scanner’s error or skipped-items list.
- Open System Settings and inspect Privacy & Security.
- Check Files and Folders permissions for the app and relevant volumes.
- If the trusted scanner requires Full Disk Access for the intended scan, review and enable that permission for the correct application.
- Quit and reopen the scanner, then repeat the same scan.
Grant access to the tool you deliberately chose, not to an unrelated helper or an unknown application suggested by a pop-up. For the narrower controls, see Apple’s Files and Folders instructions.
Terminal scans have their own context
If you use a command-line scanner, it runs through a terminal application. Read any permission errors rather than redirecting them away. A neatly sorted result can still be incomplete if unreadable directories were silently excluded.
Do not assume that adding elevated privileges resolves every macOS privacy restriction. First establish the application and location involved. Keep the investigation read-only until the reported sizes are trustworthy.
Account for files that are not ordinary local data
Cloud-only items, snapshots, and filesystem accounting can complicate a comparison. Inspect whether a reported item is a downloaded file or a cloud placeholder. Also avoid summing overlapping parent and child directories as if they were independent storage use.
A simple example: adding a project folder’s size to the sizes of all its children counts the same content twice. Compare like-for-like totals from one completed scan before interpreting a difference as hidden storage.
Use a controlled rescan
Change one variable at a time: first permission, then scope, then exclusions if needed. Re-scan the same location and compare the previously skipped folder. If it now appears, the issue was visibility rather than new files materializing on disk.
Once coverage is understood, use the large-file investigation workflow to identify candidates for review. Access to a file establishes that a scanner can measure it, not that the file is safe to delete.