How to completely uninstall an app on Mac (and its leftover files)
Updated October 3, 2026
Dragging an app to the Trash removes the app, but not the files it created while you used it. Settings, caches, saved data and background helpers stay in your Library folders. Here is where they live, how to remove them by hand without breaking anything, and the quicker careful way.
Step 1: quit the app and check for its own uninstaller
Quit the app first, including any icon it keeps in the menu bar. Some larger apps, such as security tools, VPNs and apps that install drivers, come with their own uninstaller. If yours has one, run it first, because it knows about system parts that a plain delete does not.
Step 2: move the app to the Trash
In Finder, open Applications, select the app and choose File, then Move to Trash. Do not empty the Trash yet.
Step 3: find the leftovers in your Library folder
Your Library folder is hidden. In Finder, choose Go, then Go to Folder, and type ~/Library. Leftovers are usually named after the app or after its bundle identifier, a name like com.developer.appname. These are the places to look:
| Folder | What an app keeps there |
|---|---|
| ~/Library/ | Saved data, databases, downloads and plug-ins |
| ~/Library/ | Everything a sandboxed or App Store app stores |
| ~/Library/ | Data shared between apps from one developer |
| ~/Library/ | Settings files ending in .plist |
| ~/Library/ | Temporary files the app can rebuild |
| ~/Library/ | Window positions from the last time it ran |
| ~/Library/ | Web cookies and website data |
| ~/Library/ | Log files |
| ~/Library/ | Background items that start when you log in |
Some apps also install parts for every user of the Mac, in the Library folder at the top of your disk: /Library/Application Support, /Library/LaunchAgents, /Library/LaunchDaemons and /Library/PrivilegedHelperTools. Removing those asks for your administrator password.
Step 4: remove only what clearly belongs to that app
This is the step that goes wrong. Before you move anything to the Trash:
- Match the exact app name or bundle identifier, not a word that merely looks similar. A search for a short name finds files from unrelated apps.
- Leave folders named after a developer alone when you still use other apps from that developer. They often share them.
- Leave anything you cannot identify. A few kilobytes left behind cost nothing, and a wrongly removed folder can break another app.
- Move files to the Trash, never delete them permanently, so you can put anything back.
Step 5: check background items, then empty the Trash
Open System Settings, then General, then Login Items (called Login Items & Extensions on newer macOS) and turn off anything left from the app. Restart, use your Mac for a day, and empty the Trash only when everything still works.
If you installed the app with Homebrew
Apps installed as a Homebrew cask can be removed with the extra files their cask lists by running brew uninstall --zap --cask name in Terminal. Homebrew’s own help warns that this may remove files shared with other apps, and some casks delete files permanently instead of moving them to the Trash.
The careful way: UninstallGuard
UninstallGuard does steps 3 to 5 for you without guessing. Choose an app from its list, drop it on the window, or, once you turn it on, right-click it in Finder. UninstallGuard finds the app’s data, caches, settings, containers, launch items, helpers and system extensions, and shows each one with its path, size and the exact reason it matched.
- Nothing starts selected. A scan is information, not permission. You choose what leaves.
- Four plain confidence labels: Safe to Remove, Probably Leftover, Review, and In Use, which blocks removal while the app is running. Name-only clues never count as safe.
- Everything goes to the Trash. Its removal has no permanent-delete path, and History records where every file came from.
- Leftovers from apps you deleted long ago show up under Possible Orphans, never selected for you.
- Homebrew aware. When Homebrew still lists the app, UninstallGuard can update Homebrew’s records too, as a separate step you confirm.
It is one focused app for one job: no cleaner, no optimizer, and no subscription.
Questions people ask
Does dragging an app to the Trash uninstall it?
It removes the app itself. The settings, caches, support files and background helpers it created stay in your Library folders until you remove them too.
Is it safe to delete an app’s leftover files?
Files that belong only to the app you removed are safe to remove. Folders shared by several apps from the same developer, and anything you are not sure about, should stay. Move files to the Trash instead of deleting them permanently, so you can put anything back.
Do leftover files slow down a Mac?
Mostly they just use disk space. The exception is a leftover launch agent or helper tool, which can keep starting in the background after the app is gone.
Do App Store apps leave files behind too?
Yes. Apps from the Mac App Store keep their data in a container in your Library folder, and it stays there after the app is deleted.