How to Uninstall Apps on Mac: The Bin Doesn't Finish the Job

You drag an app to the Bin, empty it, and macOS acts like the job is finished. Quite often it isn't. Knowing how to uninstall apps on Mac properly means knowing what the Bin leaves behind, where that stuff sits, and whether it is worth two minutes of your evening.

Here is the part nobody leads with: for a decent chunk of your apps, dragging to the Bin genuinely is enough. For the rest it isn't, and there is one check that tells you which sort you are dealing with before you go digging.

I have also seen the same three-step answer copied across page one of Google for years, and a chunk of it is now out of date on macOS Tahoe. So let's start there.

The quick version: how to uninstall apps on Mac

Three routes, in the order I actually use them.

1. Finder.

• Open Finder and press Command + Shift + A to jump straight to Applications.
• Select the app, then press Command + Delete, or drag it to the Bin.
• Empty the Bin. Until you do, the space is still in use.

2. The Apps view in the Dock.

• Click the Apps icon in the Dock, click and hold an icon until the icons wobble, then click the delete badge.
• This only works for apps you installed from the App Store. Everything else has no badge, which is why people assume the feature is broken.

3. The app's own uninstaller.

• Some apps ship in a folder inside Applications with an Uninstall app next to them. Adobe, Microsoft and most security software work this way.
• If one exists, use it. It removes the background pieces that Finder cannot see.

Apple's own support page covers routes one and three and stops there. It is correct as far as it goes, and it is where the top result on Google sends you.

Launchpad is gone, and half the guides haven't caught up

If you have read an app-deletion guide in the last five years, it almost certainly told you to open Launchpad, hold the icon until it jiggles, and click the little X. That path no longer exists.

macOS Tahoe removed Launchpad and put an Apps icon in the Dock in the same slot, with a plainer list-or-grid view of everything installed. Macworld has a good walkthrough of what changed and what you lost.

The delete-badge behaviour survived the move, App Store restriction and all. But if you are following a 2023 tutorial and cannot find Launchpad, you are not going mad. It is not there.

The one check that tells you whether leftovers matter

macOS has two kinds of app, and they make very different messes.

Sandboxed apps

Anything from the Mac App Store has to run in a sandbox. That means almost everything it saves goes into a single folder named after its bundle identifier, inside your Containers folder. Delete the app, delete that one folder, and you are done.

Non-sandboxed apps

Most things you download directly from a developer's website are not sandboxed. They can write wherever your user account can write, and they usually spread across five or six locations without telling you.

So the check is simply: did this come from the App Store? If yes, the Bin plus one folder finishes it. If you downloaded it from a website, assume it left traces and read the next section.

Where the leftovers actually live

Your personal Library folder is hidden by default. In Finder, press Command + Shift + G and type ~/Library to get in.

These are the places to look, in rough order of how much space they tend to hold:

• ~/Library/Containers/ - a folder per sandboxed app, named by bundle ID. Can be large if the app cached media.
• ~/Library/Application Support/ - usually named after the app or the developer. The biggest offender for design tools, note apps and anything with a local database.
• ~/Library/Group Containers/ - shared storage where an app has a helper or an extension.
• ~/Library/Caches/ - throwaway files, safe to remove, often several hundred megabytes.
• ~/Library/Preferences/ - tiny .plist files holding your settings. Kilobytes, not gigabytes.
• ~/Library/Saved Application State/ - remembers which windows were open. Harmless, also tiny.
• ~/Library/Logs/ - small, but worth clearing if an app was crashing.
• ~/Library/LaunchAgents/ and /Library/LaunchDaemons/ - background helpers. These are the ones that make an app feel like it never left.

To search all of them at once you need the app's bundle identifier. Right-click the app in Applications, choose Show Package Contents, open Contents, then open Info.plist and look for CFBundleIdentifier. It reads something like com.developer.appname.

Easier route: search ~/Library for the developer's name rather than the app's. Developers are far more consistent about naming folders after themselves than after their products.

Worth saying plainly: most of what you find will be small. If you are chasing tens of gigabytes rather than tens of megabytes, the problem is usually somewhere else entirely, and I went through where in my piece on clearing System Data on a Mac.

What not to delete

Three things I leave alone, and one piece of advice I would ignore.

• Licence files for paid apps. If there is any chance you will reinstall, deleting the licence can mean digging out an order email from 2019.
• Preferences, if you plan to come back. Wiping the .plist resets every setting you configured. Sometimes that is the point, often it isn't.
• Anything in ~/Library you cannot confidently attribute to the app you just removed. When in doubt, leave it. A stray 40KB file costs you nothing.

The advice I would ignore: there is an answer sitting on page one of Google right now, on a Microsoft community forum, telling Mac users to run a sudo command in Terminal to remove apps. Do not run sudo commands you found in a forum thread to delete a piece of software. The downside is enormous and the upside is a few seconds saved.

Apps that need their own uninstaller

Some software installs more than an app. It installs system extensions, launch daemons, network filters or drivers, and none of that goes in the Bin with the icon.

The usual suspects:

• Adobe apps - remove them through the Creative Cloud desktop app, not Finder.
• Microsoft Office - Microsoft publishes a licence removal tool, and skipping it leaves activation data behind.
• Antivirus and VPN clients - these install network extensions that keep running after the app is gone.
• Virtualisation, backup tools and audio drivers - same problem, plus kernel-level components on older versions.

After removing any of these, open System Settings, go to General, then Login Items and Extensions, and check both lists. If the app you just deleted is still sitting there, something is still installed.

The tell-tale symptom is a menu bar icon or a background process that survives a restart. That is a launch daemon, and Finder will never touch it.

How to delete apps on Mac that won't delete

The error message is usually vague, so here is what it actually means.

"The item is in use"

The app, or a helper it started, is still running. Quit it properly, then open Activity Monitor, search for the app's name, and force quit anything that matches. Try again.

It keeps coming back after a restart

A launch agent is reinstalling it. Look in ~/Library/LaunchAgents and /Library/LaunchAgents for a .plist with the developer's name, and remove that first.

You are asked for a password and it still fails

Either the app is a built-in one protected by System Integrity Protection, or your Mac is managed by an employer or school through MDM. Neither is something you can force from Finder, and you should not try.

Built-in Apple apps

A handful can be removed. Most cannot, and the ones that can are mostly the small utilities I wrote about in my round-up of hidden Mac apps.

Do you need a paid cleaner app?

This is the part every other guide answers with an affiliate link, so let me give you the numbers instead.

CleanMyMac, the best-known of them, is listed on MacPaw's store today at 39.95 US dollars a year for one Mac, or 119.95 dollars for a one-off licence. There is no pound price on that page, which is its own small annoyance for a UK buyer.

That one-off licence is exactly three years of the annual subscription, at the undiscounted rate. My arithmetic, not MacPaw's framing, and worth knowing before you pick a tier.

What these tools actually do for uninstalling is search your Library for files matching the app's bundle ID and offer to delete the matches. That is the same job as the Finder search above, done faster and with less thinking.

My honest read: if you install and remove software constantly, a cleaner pays for itself in saved faff. If you remove three apps a year, you are paying an annual subscription for about six minutes of work. AppCleaner does the same file-matching for free if you want the convenience without the bill.

What none of them can safely do is decide which leftovers matter. That judgement is still yours, which is why the do-not-delete list above is the useful half of this article.

My take

For App Store apps, drag to the Bin and stop worrying. The sandbox did the tidying for you, and the one Containers folder left behind is usually measured in megabytes.

For anything you downloaded from a website, give it two minutes in ~/Library before you move on, and check Login Items and Extensions if it was security or creative software. That covers ninety-odd per cent of the mess.

And if you are uninstalling because your Mac feels full rather than because you dislike the app, the apps are almost never the reason. Go and look at System Data first. If you are uninstalling because you picked badly, my list of Mac apps worth keeping in 2026 is a better starting point than another cleaner subscription.

FAQ

Does dragging an app to the Bin uninstall it completely on a Mac?

Not always. For App Store apps it effectively does, because sandboxing keeps almost everything in one folder. For apps downloaded directly from a developer, it removes the app itself but leaves preferences, caches, support files and sometimes background helpers in your Library folder.

How do I delete apps on Mac that won't delete?

Quit the app, then force quit anything with its name in Activity Monitor and try again. If it survives a restart, a launch agent is reinstalling it, so remove the matching .plist from ~/Library/LaunchAgents. If macOS refuses outright, the app is either protected by the system or installed by an employer through device management.

Where do leftover Mac app files go?

Mostly inside ~/Library, spread across Application Support, Containers, Group Containers, Caches, Preferences, Saved Application State and Logs. Press Command + Shift + G in Finder and type ~/Library to get there, then search for the app's bundle identifier or the developer's name.

Source: Delete or uninstall apps on Mac, Apple Support