Home › Mac Guides › Uninstall Apps on Mac

How to completely uninstall apps on your Mac

Dragging an app to the Trash removes the .app bundle and nothing else. Caches, preferences, containers, saved state and login items stay behind in your Library — often hundreds of megabytes per app, and macOS will never clean them up. Here is how to remove all of it, safely.

Updated 2026-08-02 · Written by the CleanerMac team · macOS 13–15 tested

Why dragging an app to the Trash isn't enough

On macOS an application is a bundle — a folder named Something.app that Finder displays as a single file. Deleting it removes the executable and its built-in resources. It does not remove anything the app wrote outside itself while you were using it, and every non-trivial app writes a lot outside itself.

A typical Mac app scatters data across at least six locations, all keyed to its bundle identifier (something like com.vendor.AppName):

• ~/Library/Application Support/<AppName or bundle id> — databases, downloaded resources, plugins. Usually the largest leftover.
• ~/Library/Caches/<bundle id> — cached downloads and thumbnails. Frequently hundreds of megabytes.
• ~/Library/Preferences/<bundle id>.plist — settings. Tiny, but it is why a reinstalled app remembers your old configuration.
• ~/Library/Containers/<bundle id> and ~/Library/Group Containers/<team id>.<bundle id> — for sandboxed apps, this is where everything lives, including real documents.
• ~/Library/Saved Application State/<bundle id>.savedState — restored window positions.
• ~/Library/Logs/<AppName> and, for apps with helpers, ~/Library/LaunchAgents or /Library/LaunchAgents.

One app leaving 200 MB behind is a rounding error. A hundred apps over five years is not, and nothing in macOS ever cleans it up. That accumulated residue is a large part of what shows up as System Data on the Storage screen.

The right order to uninstall an app

1. Check for a built-in uninstaller first. Adobe, Microsoft Office, VPN clients, printer drivers, antivirus tools and anything that installs a system extension almost always ship one — look in /Applications, inside the app's own folder, or in the original .dmg. Use it. These apps install privileged components that a file-deleting tool cannot cleanly remove.
2. Quit the app, and quit any helper it runs. Check the menu bar and Activity Monitor.
3. Remove login items. System Settings → General → Login Items & Extensions. Remove the app's entry under both Open at Login and Allow in the Background before deleting it, otherwise you can be left with an orphaned entry.
4. Delete the app. Drag Something.app from /Applications to the Trash. On macOS versions that still have Launchpad you can also delete App Store apps from there.
5. Find the bundle identifier if you want to be precise. Before deleting, run osascript -e 'id of app "AppName"', or after the fact use defaults domains | tr ',' '\n' | grep -i vendorname.
6. Search the Library folders listed above for that identifier and the app's name, and delete the matching folders.
7. Empty the Trash — space is not reclaimed until you do.

Finding leftovers by hand

Open Finder, press ⇧⌘G and visit each of these in turn, sorting by name so the app's folders group together:

• ~/Library/Application Support
• ~/Library/Caches
• ~/Library/Containers
• ~/Library/Group Containers
• ~/Library/Preferences
• ~/Library/Saved Application State
• ~/Library/Logs and /Library/Logs
• ~/Library/LaunchAgents, /Library/LaunchAgents, /Library/LaunchDaemons — only if the app ran a background service

Terminal is faster for the search itself. To locate everything mentioning a vendor:

• ls -la ~/Library/Application\ Support | grep -i vendorname
• find ~/Library -maxdepth 3 -iname "*vendorname*" 2>/dev/null
• du -sh ~/Library/Containers/* | sort -h | tail -20 — the twenty biggest containers, which is a good way to spot expensive leftovers you forgot about.

Inspect before you delete, and move things to the Trash rather than using rm -rf, so a mistake is reversible. A useful habit is to check the size of a candidate folder first with du -sh: if a leftover is two megabytes, the risk of deleting the wrong thing outweighs the space you would recover, and it is fine to leave it. Concentrate on the folders that are actually large.

Spotlight is deliberately unhelpful here — it excludes the Library folder from normal searches, which is why apps appear to leave nothing behind until you go looking manually. In a Finder search window you can add the criterion System files — are included to widen the net, though browsing the paths directly is usually quicker and less error-prone.

What not to delete

This is where manual uninstalling goes wrong.

• Containers for apps you still use. Sandboxed apps store your actual documents inside ~/Library/Containers. Deleting a container is deleting your data, not a cache.
• Shared framework folders. Vendors with several products share support folders; removing one app should not take the shared folder with it.
• Anything matched only by a generic word. Searching for "mail", "photo" or "code" will hit system components. Match on the full bundle identifier where you can.
• System launch daemons in /System/Library. These are protected and are not yours to remove.
• Preferences you might want back. If you are reinstalling to fix a bug, keep the .plist until you know the reinstall worked — or move it to the Desktop instead of the Trash.

App Store apps, and apps that resist removal

Apps installed from the App Store are sandboxed, so nearly all their data lives in a single container folder — removing the app plus ~/Library/Containers/<bundle id> is usually a complete uninstall.

If macOS refuses to delete an app, work through these in order: quit it and any helper process; check Activity Monitor and force quit if needed; verify it is not launching at login; boot into Safe Mode (Apple Silicon: shut down, hold the power button until startup options appear, select the disk and hold Shift) and delete it there. If it installed a system extension, System Settings → General → Login Items & Extensions lets you disable it first. Never disable System Integrity Protection to remove an app — no legitimate app requires that.

Command-line tools installed with Homebrew are not in /Applications at all: use brew uninstall <formula> for command-line tools, and brew uninstall --zap --cask <token> for cask apps, which also removes configuration files.

Doing it in one action

The manual process above is complete and free, and worth knowing. It is also tedious for more than a couple of apps, and the risky part — deciding whether a Library folder belongs to the app you are removing — is exactly the part that is easy to get wrong at 11pm.

CleanerMac's uninstaller reads each app's bundle identifier and enumerates the locations tied to it, shows you every file it intends to remove with its size before anything happens, offers to quit the app if it is still running, and sends everything to the Trash so it stays recoverable. Matches found only by name rather than identifier are listed separately and left unchecked, because those are the ones worth a second look. It is a native menu-bar app for macOS 13 and later, runs on-device with no account, is available in 20 languages, and is a one-time $24.99 purchase with a 3-day trial.

After uninstalling: reclaim the rest

A clean uninstall pass is a good moment to finish the job:

• Empty the Trash, then re-check Apple menu → System Settings → General → Storage.
• Clear remaining caches — see clear cache on Mac.
• Look for duplicates left by installers and exports with the duplicate files guide.
• If you removed several apps, work through freeing up space for the remaining categories, and the Mac cleaner overview for a maintenance routine.
• Fewer login items usually means a faster boot; speeding up a Mac covers the rest.

Uninstall the right way

See every leftover before it goes — and recover it if you change your mind.

Download CleanerMac — free for 3 days

macOS 13+ · Apple Silicon & Intel · $24.99 once, no subscription