Mac Cleaner Pro — the best free Mac cleaner
that finds hidden gigabytes

macOS stores cache data across five distinct layers, each governed by different rules about size, lifetime and safety. Layer 1 is ~/Library/Caches, the largest and fastest-growing: every app you run writes here, and the files are explicitly marked as re-creatable by macOS itself (the system can delete them under disk pressure). This is where Safari stores its content cache, where Xcode writes intermediate build products, and where third-party apps store network responses. A mac cleaner that only reads this layer captures the most visible junk but misses four more layers that together often hold as much data.

Layer 2 is /Library/Caches — the system-wide equivalent, written by macOS processes and privileged apps. It contains font glyph maps, icon databases, Spotlight index artefacts and update installer payloads. A single major macOS update can leave behind 400-800 MB of installer data here that is never automatically cleaned. Layer 3 is /private/var/folders — the BSD temporary directory space where short-lived process data accumulates. Files here are supposed to be cleaned on reboot, but orphaned directories from crashed processes can persist indefinitely. Most mac cleaners skip Layer 3 entirely because the paths change with each user session. Mac Cleaner Pro resolves the current session's temporary folder at scan time and reads it correctly.

Layer 4 is ~/Library/Containers — the sandboxed storage space for apps distributed through the Mac App Store. Each sandboxed app writes its cache, application support and documents into an isolated container. When you uninstall a sandboxed app by dragging it to the Trash, the container is not removed; it persists indefinitely, consuming disk space for an app that is no longer installed. The app cleaner for mac module inside Mac Cleaner Pro identifies orphaned containers — containers whose parent app bundle no longer exists — and flags them for removal. This is the most common source of the "phantom gigabytes" users notice when they try to tally up what their installed apps should be using versus what the disk actually shows.

Layer 5 is ~/Library/Developer — the build system storage layer. Xcode's DerivedData folder here can balloon to 40 GB on an active development machine. Simulator runtimes for old iOS and tvOS versions add another 4-8 GB each. Core ML model caches and Swift Package Manager dependency caches add several hundred megabytes per project. Mac Cleaner Pro's developer module reads the active Xcode project list to distinguish DerivedData that is still being used (left alone by default) from DerivedData belonging to archived or deleted projects (flagged for removal). This conservative approach is what makes Mac Cleaner Pro safe to use on a developer Mac without fear of breaking an active build.