How to Completely Uninstall Apps on Mac

Uninstalling an app on a Mac feels like it should be simple: drag it to the Trash, empty the Trash, done. And technically, that does remove the app itself. But it doesn't remove everything the app created while it was installed. Preferences, cached data, saved settings, and sometimes entire support folders are often left behind in your user Library, quietly taking up space and occasionally causing odd behavior if you ever reinstall the same app later. If you actually want to completely uninstall a Mac app — not just move its icon out of Applications — there are a few extra steps worth knowing.

None of this is urgent for most people. A handful of leftover preference files aren't going to slow your Mac down. But if you're trying to free up meaningful space, troubleshoot an app by giving it a truly clean reinstall, or just prefer knowing that removing something actually removes it, it's worth understanding what macOS leaves behind and where to look for it.

What "completely" uninstalling actually means

Unlike Windows, macOS doesn't have a centralized uninstaller or registry that apps must register with. Most Mac apps are self-contained .app bundles that live in /Applications, and dragging that bundle to the Trash does remove the actual program. What it doesn't touch are the extra files the app wrote elsewhere on disk while it was running — files that live almost entirely inside your user Library folder (~/Library, hidden by default).

Depending on the app, that can include:

• Preferences — a small .plist file in ~/Library/Preferences/ storing your settings for that app.
• Caches — temporary data in ~/Library/Caches/, usually there purely for performance.
• Application Support data — a folder in ~/Library/Application Support/, which can range from a few kilobytes to several gigabytes depending on the app (think saved projects, downloaded plugins, or a local database).
• Containers — for sandboxed apps (common with anything downloaded from the Mac App Store), macOS keeps a dedicated folder in ~/Library/Containers/ that holds most or all of the app's data in one place.
• Occasionally, smaller traces in ~/Library/Logs/, ~/Library/Saved Application State/, or ~/Library/LaunchAgents/ if the app installed a background helper.

None of this is a flaw in macOS — it's a reasonable design that lets you reinstall an app later and pick up right where you left off, settings and all. The tradeoff is that if you actually want to remove Mac applications for good, rather than just get the icon out of your Applications folder, you have to go looking for these files yourself.

It's also worth knowing that not every app leaves the same footprint. A simple, single-window utility might only ever write one small preferences file. A larger app — a video editor, a note-taking app that syncs a local database, or anything with plugins — can spread files across several of these folders at once, some of them sizable. There's no single rule for how much a given app leaves behind; the only way to know for sure is to check.

How to manually uninstall an app on Mac

The manual approach works fine and doesn't require installing anything else. It just takes a bit of care. Here's the process:

1. Quit the app completely. Check the Dock and menu bar to make sure it isn't still running — right-click its Dock icon and choose Quit, or use Cmd + Q from the front app. Trying to delete files while an app is running can cause errors or leave files locked.
2. Drag the app from /Applications to the Trash. Open Finder, go to Applications, find the app, and drag it to the Trash (or select it and press Cmd + Delete). macOS may ask for your password since removing apps requires admin permission.
3. Open your user Library folder. It's hidden by default. In Finder, click Go in the menu bar, then hold the Option key — "Library" will appear in the menu. Click it to open ~/Library.
4. Search each relevant subfolder for the app's name. Check Preferences, Caches, Application Support, and Containers for anything matching the app's name or its developer's name (developers often use a reverse-domain identifier like com.developer.appname, so it helps to know the developer if the app name alone doesn't turn anything up).
5. Review each match before deleting it. Open the file or folder's info if you're not sure, and confirm it's actually tied to the app you just removed rather than something else with a similar name.
6. Delete what you're confident belongs to the app. Drag each confirmed file or folder to the Trash.
7. Empty the Trash once you're done, to actually reclaim the disk space.

This is the core of how to uninstall apps on Mac by hand, and for a simple app with just a preferences file and a small cache, it only takes a couple of minutes. A quick tip that speeds up step four: Finder's search bar can search within a specific folder rather than your whole Mac. Open ~/Library/Application Support/, use Cmd + F, and set the search scope to that folder rather than "This Mac" — it's a faster way to confirm whether a given app left anything there than scrolling through an alphabetical list by eye.

A word of caution before you start deleting

~/Library is shared territory. It holds files for every app you've ever installed, plus some files macOS itself relies on. Folder names don't always make it obvious what's safe to touch, and two unrelated files can sit right next to each other with confusingly similar names.

The rule worth following: only delete something if you can confidently identify it as belonging to the app you're removing. If a file's name is ambiguous, or you're not sure whether it's tied to the app or to something else entirely, leave it alone. A stray leftover file sitting unused in your Library is harmless — it just takes up a small amount of space. Deleting the wrong file isn't something you can undo once the Trash has been emptied, and depending on what it was, it could affect an app you didn't mean to touch. When in doubt, skip it rather than guess.

A common way this goes wrong: two apps from the same developer, or an app and an unrelated system component, can have overlapping or similarly worded folder names in Application Support. Before deleting a folder there, it's worth glancing inside it — file types and modification dates are usually a good clue as to whether it actually belongs to the app you just removed. If nothing about it clearly points to that app, it costs you nothing to leave it where it is.

Check if the app has its own uninstaller

Before doing any manual cleanup, it's worth checking whether the app came with its own uninstaller. This is more common with larger applications — creative software, developer tools, and some utilities — that write files to multiple locations on disk. Look for an app named something like "Uninstall [App Name]" either inside the app's own folder in Applications, alongside the original installer .dmg file if you kept it, or in the app's Help menu. When one exists, it's usually the most thorough option since the developer knows exactly what their app installed and where.

This is especially common for software that installs more than just an app bundle — things like device drivers, virtualization tools, or apps that add a system extension or kernel-level component. A dedicated uninstaller can remove those pieces cleanly in a way that simply dragging the app to the Trash can't, since some of what they install doesn't live inside the .app bundle at all. If you're not sure whether an app falls into this category, it's worth a quick look at its Help menu or original download page before assuming a plain drag-to-Trash is enough.

What if the app won't move to the Trash?

Occasionally macOS refuses to let you delete an app — you'll see a message saying it's "in use" or the Trash operation just silently fails. This usually means a background process tied to the app is still running even though the main window is closed, or a related helper hasn't fully quit. Opening Activity Monitor and searching for the app's name will often show a leftover process you can force-quit before trying again. We've written a separate guide covering how to uninstall apps that won't delete on Mac if you run into this — it walks through identifying and closing whatever's holding the app open.

A faster way to uninstall apps completely

Hunting through several Library subfolders by hand works, but it does take a bit of time and a bit of confidence in what you're looking at — which is exactly the part most people would rather skip. This is the specific problem CleanMyApple's app uninstaller is built for: pick an installed app, and it identifies the preferences, caches, support files, and container data associated with it, and shows you that list before anything is removed. You review what it found and confirm what gets deleted, rather than moving files to Trash one at a time from four different folders.

It doesn't do anything the manual process above doesn't already cover conceptually — it's still finding preferences, caches, Application Support data, and containers tied to an app, and it still asks you to confirm before deleting anything. It just does the searching part for you, which is the part that takes the most time when you're doing it by hand across several installed apps at once.

Already deleted some apps? What to do about old leftovers

If you've been deleting apps the regular way for a while — just dragging them to the Trash without a second thought — there's a decent chance you've built up a small collection of orphaned files for apps that no longer exist on your Mac at all. These are harmless individually, but they can add up over years of installing and removing software. Our guide on how to remove app leftovers on Mac covers how to track down and safely clear out that kind of buildup after the fact.

Whether you're removing one app today or cleaning up years of leftovers at once, the underlying goal is the same: remove app files that are no longer doing anything useful, without touching anything that is.