Home  â€º  Articles

How to Completely Uninstall Apps on Mac

Updated 2026-07-26  Â·  4 min read

Uninstalling apps on a Mac or MacBook by dragging them to the Trash removes the app. It doesn't remove the seven other things the app installed. Here is where they're, and when it matters.

On macOS an application is a bundle, a single .app folder that Finder shows as one file. Deleting it removes the executable and its resources. What it doesn't touch is everything the app wrote outside that bundle while you were using it.

For a sandboxed App Store app, that's usually tidy and contained. For anything installed from the web, it is scattered across your Library.

Where the leftovers live

Seven locations account for nearly all of it. Every path below is inside your home folder unless stated otherwise.

There are also system-level equivalents in /Library/ without the tilde, which need an administrator password and are where installers put things that apply to every user.

Doing it by hand

Find the bundle identifier first, because most folders are named after it rather than the app:

osascript -e 'id of app "AppName"'

That returns something like com.vendor.appname. Then search each Library folder for both the app name and that identifier. Open the Library folder from Finder with Go, Go to Folder, then paste ~/Library.

Two rules that keep this safe Quit the app before you start, or it'll rewrite files as you delete them. And move things to the Trash rather than deleting them outright, so a mistake stays recoverable until you empty it.

What about AppCleaner and similar free tools?

AppCleaner is a long-standing free utility that does the core job well: drop an app on it and it finds the associated files and offers to remove them together. If all you need is occasional clean removal, it is a reasonable answer and it costs nothing.

Where free tools of this kind tend to stop is the case that matters most on an older machine, which is finding leftovers from apps that are already gone. Those tools work from the app bundle, so with no bundle to inspect there's nothing to match against. That gap is the main practical reason to reach for something with a full-disk scan behind it.

Apps that need their own uninstaller

Some software installs kernel extensions, system extensions or privileged helper tools, and dragging the app to the Trash leaves those running. Antivirus products, VPN clients, virtualisation software, backup agents and printer or scanner drivers all fall into this category.

For these, use the vendor's own uninstaller. Adobe, Microsoft, most VPN providers and every antivirus vendor ship one. Removing the app bundle and leaving a system extension behind is how people end up with a network filter they can't switch off.

When leftovers matter, and when they don't

Worth being honest about this, because the category tends to imply every stray file is a problem.

It matters when:

It doesn't matter when:

A few hundred stray plist files don't slow a Mac down. Whoever tells you otherwise is describing a problem that doesn't exist on this operating system. What they do is take up space, which matters only when you're short of it.

Find every leftover from every app you've removed

CleanMachine's Uninstaller checks all seven locations plus the system-level ones, matches on bundle identifier rather than name so it doesn't catch the wrong files, and shows the size of each leftover before removing anything. Everything goes to a recoverable Trash. Free to scan.

↓ Download Free & Scan

Finding leftovers from apps you deleted years ago

This is the harder case, because you no longer have the bundle to read an identifier from. Sort ~/Library/Application Support by size in Finder and look for folders whose names you no longer recognise. Cross-check anything you're unsure of by searching the name before deleting it, and move rather than delete.

On a Mac that has been through a few years of software, this folder is regularly the single largest recoverable thing in your home directory, and it is invisible from the Storage pane in System Settings because macOS files all of it under System Data.

Common questions

Does dragging an app to the Trash uninstall it on Mac?
It removes the application bundle, but not the support files, caches, preferences, containers, launch agents or logs the app wrote to your Library. Those stay behind and can amount to gigabytes.
How do I uninstall apps on a MacBook?
Exactly as on any Mac, since this is macOS behaviour rather than hardware specific. Drag the app to the Trash, then clear its leftovers from ~/Library/Application Support, Caches, Preferences, Containers, LaunchAgents and Logs. Apps with system extensions need the vendor's own uninstaller.
Where do Mac apps store leftover files?
Mainly ~/Library/Application Support, ~/Library/Caches, ~/Library/Preferences, ~/Library/Containers, ~/Library/Group Containers, ~/Library/LaunchAgents and ~/Library/Logs, plus system-level equivalents in /Library.
Do leftover files slow down a Mac?
No. Inactive files have no performance cost. They take up space, which matters only when the disk is nearly full. The exception is a leftover launch agent or system extension that's still running.
How do I find leftovers from an app I already deleted?
Sort ~/Library/Application Support by size and look for folders you no longer recognise. Without the app bundle you can't look up its bundle identifier, so match on folder name and move items to the Trash rather than deleting them.
Do App Store apps leave less behind?
Usually yes. Sandboxed apps keep most of their data inside ~/Library/Containers, so removal is more contained than with apps installed from the web.

Keep reading