How to Completely Uninstall Apps on Mac (Leftover Files)

Dragging an app to the Trash feels done. The icon disappears, the dock stops nagging, and you move on. But on macOS, the .app bundle in /Applications is only the visible part. Most apps scatter their working files across half a dozen folders in ~/Library, and a surprising number register background agents that keep running after the app itself is gone.

This guide shows where those leftovers hide and how to remove them properly. It's the fourth in our troubleshooting series, after the guides to freeing up disk space, fixing a slow Mac, and taming your RAM.

What actually stays behind

When you install a typical Mac app, it writes to several places at once:

• The app itself in /Applications
• Preferences in ~/Library/Preferences, as files like com.example.app.plist
• Support files in ~/Library/Application Support/<App Name>
• Caches in ~/Library/Caches/<App Name>
• Saved state in ~/Library/Saved Application State
• Login items or launch agents in ~/Library/LaunchAgents
• Sandboxed data in ~/Library/Containers and ~/Library/Group Containers

Dragging the app to the Trash removes only the first item. Everything else stays, and the caches and support files can total hundreds of megabytes for apps you used twice.

The three folders worth checking by hand

You don't need a tool to do most of this. Open Finder, hit Cmd+Shift+G, and paste these paths one at a time. Look for folders or files named after the app, or its developer.

~/Library/Application Support is where apps keep real data: databases, downloaded modules, saved projects. This is usually the biggest leftover. Delete the folder matching the app name.

~/Library/Preferences holds .plist files. They are tiny, but they survive reinstallation, which is why old settings sometimes reappear. Delete the one matching the app's bundle identifier (for example com.spotify.client.plist for Spotify).

~/Library/Caches is safe to clear for any app, running or not. macOS rebuilds caches on demand, and clearing them never breaks an app. This folder is also where a surprising amount of dead weight accumulates.

If the app ran as a menu bar tool or a background service, also check ~/Library/LaunchAgents and /Library/LaunchAgents. A file there means the app starts something at login even when you never open it. Remove the file, then log out and back in.

The terminal shortcut

For apps with unusual names, or when you want to be thorough, a couple of commands beat clicking around.

Find every file that mentions the app:

find ~/Library -iname "*appname*" 2>/dev/null

This lists matches across Preferences, Caches, Application Support, Containers, and everything else in one pass. Check each hit before deleting.

For apps installed via a .pkg installer, macOS keeps a receipt:

pkgutil --pkgs | grep -i appname

If something shows up, remove the receipt with:

sudo pkgutil --forget com.example.pkg.appname

This doesn't delete the files, but it stops future uninstallers and system updates from thinking the app is still installed.

Apps that ship their own uninstaller

Some apps include an uninstaller of their own. Look inside the app's folder in /Applications, or check the app's menu for an "Uninstall" option. Developer-supplied uninstallers are the safest option for those apps, because they know their own file layout.

App Store apps are the one genuine exception. They are sandboxed, so all their data lives inside ~/Library/Containers, and dragging the app to the Trash removes the container too. No follow-up needed.

How a cleaner fits in

Manual removal handles the app itself and the obvious folders. A cleaner helps with the parts you can't easily see: orphaned caches, leftover preference fragments, and the junk that piles up across every app you've ever installed.

DripCleaner is a native macOS cleaner that finds the junk files, caches, and forgotten folders eating your disk, and deletes nothing until you say so. It runs entirely on your Mac, with no uploads and no account. Pair it with DiskBrew when you want to see exactly where your space went before you decide what to remove.

Think of it as the clean-up pass after you've done the manual work: the app is gone, the main folders are gone, and the cleaner sweeps the corners.

A one-pass habit

Doing this properly takes about ten minutes per app. The routine that works: quit the app, drag it out of /Applications, check the three Library folders, clear its launch agents if it had any, then restart once. The restart matters because it confirms no background process is still holding files open.

Leftover files are also a quiet argument for software that keeps its footprint small in the first place. Native programs that store their data in one place and register nothing at login are easier to remove, easier to troubleshoot, and easier to live with. That's the whole idea behind the café menu, where every app is local-first, and one subscription covers all of them.

If you've been meaning to clear out an app you no longer use, this is the weekend for it. And if you're new here, grab a 7-day free trial and see what a tidy, native, offline-first app collection feels like.