Mac cleanup apps: decide what to delete first

The storage bar in System Settings shows a wide grey band called System Data, the number next to it is in the hundreds of gigabytes, and clicking it produces no list. That is usually the moment the search for a Mac cleanup app starts. The instinct is reasonable, but the order is wrong. Cleanup tools are not interchangeable, because "unneeded file" covers at least four different things, and each one lives somewhere else, is created by something else, and is safe to remove under different conditions. Picking the tool before naming the category is how people end up paying for a scanner that reclaims two gigabytes when eighty were sitting in a folder they already knew about.

This walks through the four categories, what the built in panel can and cannot see, what actually stays on disk when an application goes in the Trash, and how the available tools divide up along those lines.

Four kinds of unneeded file, and why one tool cannot cover them

Sorting the problem first makes the tool choice almost automatic.

Files created and forgotten. Downloads, screen recordings, exported video, old disk images, duplicate copies of the same archive. These are ordinary documents in ordinary folders. Nothing is hidden about them. They are usually the single largest recoverable block on a working Mac, and no scanning engine is needed to find them, only a view sorted by size.

Files an application left behind. Support folders, saved application state, preference files, login items, and helper tools scattered under the Library folder. These do not appear in any Finder window a person visits daily, and they persist after the application itself is gone.

Caches and intermediate output. Browser caches, image thumbnails, package manager caches, build artifacts, container images, model weights pulled by a command line tool. This category grows silently and rebuilds itself if deleted, which makes it both the safest and the least permanent thing to clear.

Space the operating system is holding. Local snapshots, purgeable space, files that iCloud has already offloaded. Deleting these directly is not possible in the normal sense, because the system decides when to release them.

A tool built for one category is close to useless on the others. A disk visualiser cannot see what an application registered under a launch agent. An uninstaller cannot tell that a video export is a duplicate. Naming the category first is the step that saves the money.

What the built in storage panel shows, and what it hides

The panel lives in System Settings under General, then Storage. Apple's own guidance on freeing space is direct about the part most people skip.

Empty the Trash. Files moved to the Trash continue to use storage space until you empty the Trash. Source: support.apple.com

That sounds trivial until a scanning tool reports twenty gigabytes reclaimed and the free space number does not move, because everything it removed went to the Trash rather than off the disk.

The same page notes that starting the Mac in safe mode clears certain system caches and lets the system rebuild them, which is occasionally enough to get past a failing update without deleting anything a person cares about.

The command line view is worth having alongside the panel, because it answers a different question. On an Apple silicon Mac, df -h / reports the sealed, read only system volume rather than the whole container, so the used figure looks implausibly small. diskutil info / prints Container Free Space, which is the number that actually matters. For finding the weight, du -sh -d 1 ~/Library and du -sh -d 1 ~/Downloads list sizes one level deep and take seconds. Sorting by size in a Finder window set to List view does the same job with the mouse.

System Data is a remainder, not a category

The label causes more confusion than any other part of the panel. It is not a folder and not a type of file.

System Data (or Other) is a general category that measures the storage space used by all Apple and third-party files that don't belong to any more specific category. Source: support.apple.com

In other words, it is whatever is left over after the named categories are counted. A large System Data figure is not a fault and not a sign of junk. It commonly contains caches under the Library folder, local Time Machine snapshots, virtual machine disk images, container storage from development tools, and downloaded media that the classifier could not attribute.

One consequence is worth stating plainly: a tool that promises to shrink System Data is promising to shrink a total, not to remove a thing. Whatever it deletes will come from one of the real locations underneath, and the honest ones say which. If a scanner reports a large System Data figure and offers a single button, the useful question is which paths it is about to touch. That answer either exists in the product's interface or it does not, and it is a reasonable basis for choosing between two otherwise similar products.

Two checks narrow it down quickly. tmutil listlocalsnapshots / lists the local Time Machine snapshots on the boot volume, which are held on disk and released automatically as space runs short. du -sh -d 1 ~/Library/Caches shows whether the caches folder is carrying tens of gigabytes, which happens on any Mac running package managers, browsers, or container tooling. Neither command changes anything, so both are safe to run before deciding on a tool.

What actually stays behind when an app goes in the Trash

Dragging an application bundle to the Trash removes the bundle. It does not remove what the application wrote elsewhere. The usual leftovers sit in a handful of predictable places: ~/Library/Application Support, ~/Library/Caches, ~/Library/Preferences, ~/Library/Containers, ~/Library/Saved Application State, and ~/Library/LaunchAgents. Sandboxed applications from the App Store keep almost everything inside a single container folder, so they clean up cleanly. Applications installed from a downloaded installer package are the ones that spread.

Two things follow from this. First, size is rarely the reason to remove leftovers. A preference file is a few kilobytes. The reason is behaviour: a launch agent that keeps starting a helper for software that no longer exists, or a stale preference that a reinstalled version picks up and misbehaves on. Second, blanket deletion of anything matching an application name is risky, because shared frameworks and licence files sometimes carry a vendor name while still being used by another product.

A dedicated uninstaller is the sensible tool here. AppCleaner from FreeMacSoft is free, and its download page lists version 3.6.8 as covering macOS Mojave up to Tahoe. It works by taking the dropped bundle, finding the related files, and showing them for confirmation before deletion. The confirmation step is the value. Anything that deletes without showing the list is asking for trust it has not earned.

The four shapes of cleanup tool

Shape	What it is good at	Examples and facts
Disk visualiser	Finding the largest forgotten files fast	DaisyDisk is sold for 9.99 US dollars on its own site. OmniDiskSweeper is offered as a free download by The Omni Group
Uninstaller	Removing what an application registered	AppCleaner is free, version 3.6.8, listed for macOS Mojave through Tahoe
All in one maintenance suite	Repeated scanning across several categories	Usually commercial, commonly sold on a subscription. Check whether the licence is a one time purchase before buying
Command line	Measuring and scripting a repeatable rule	du, find, tmutil ship with macOS. Nothing to install

The table is not a ranking. A person whose disk is full of exported video needs the first row and nothing else. A person reinstalling development tools repeatedly needs the second and fourth. A suite covers more ground and costs more, and its value depends entirely on whether the recurring scan gets used after the first month.

One practical filter applies to every commercial option: check what the licence actually is before paying. Some products in this category moved from a one time purchase to a subscription at some point in their history, and the pricing page is the only reliable source for the current terms.

Make every deletion reversible before running anything

Storage cleanup is the one maintenance task where a mistake is permanent, so the safety net is worth building first.

Move before deleting. Create a folder named for the date, move the candidates into it, and continue working for a week. Anything genuinely needed will announce itself. Delete the folder afterwards. This costs one week of disk space and removes almost all of the risk.

Keep deletions inside the Trash for one pass. The Trash exists precisely so that removal and reclamation are two separate decisions, and Finder can also be set to remove items automatically after 30 days, which turns the delay into a default rather than a chore.

Never let a scanning tool delete without showing the list. This applies to commercial software and to a shell one liner equally. find ~/Library/Caches -type d -maxdepth 1 prints what would be affected. Running it before adding any deletion step is the difference between a cleanup and an incident.

Finally, be careful with anything that offers to clear language files, system caches, or so called system junk without naming the paths. The space recovered is usually small and the failure mode is not.

Turn one cleanup into a standing rule

A single clearing session buys a few months. What keeps the disk usable is a rule that runs without deciding anything.

The highest yield rule is the simplest: nothing stays in Downloads. Screenshots, installers, and email attachments accumulate there because the folder has no owner. Setting one weekly moment to empty it, or writing a two line script that moves anything older than 30 days into a dated folder, removes most of the recurring problem.

The second rule is about the tools that generate weight. Package managers, container runtimes, and build systems each have a documented cache clearing command. Running those on a schedule keeps the caches folder from becoming the largest thing on the disk, and it does not require any third party software.

The third is a placement rule for large media. Video exports and disk images go on an external volume from the start, not after the disk fills. Deciding placement at creation time is far cheaper than sorting it out later.

Running these means moving between a folder view, a terminal, and sometimes a quick question about what a directory contains. A file manager with a built in terminal removes the window switching that makes these rules quietly get skipped, and the Features page describes how the folder view and the shell sit in the same window. When the question is whether a general file manager is enough or a dedicated cleaner is needed, the comparison page lays out what the different tools cover.

What to change first

Run du -sh -d 1 ~/Library ~/Downloads ~/Movies and look at the three numbers before installing anything. In most cases the largest recoverable block is already visible in a folder, and the only tool needed after that is an uninstaller for leftovers and a rule that keeps Downloads empty. If the folder view and the terminal are already part of the routine, having both in one window is what makes the rule stick, which is the shape Atriens is built around.