How to Completely Uninstall Apps on Mac (No Leftovers)

By 8 min read

appscleanupstorage

Written for macOS 27 Golden Gate and macOS 26 Tahoe. The Library folders below have stayed the same for many macOS releases. System Settings labels can shift slightly between versions.

Most Mac apps are a single bundle in the Applications folder, so dragging one to the Trash feels like the whole job, and usually it gets you most of the way. Apps also write settings, caches, saved window state and sometimes background helpers to other places, though, and the drag doesn't touch any of those. Below is a careful, complete uninstall using only what ships with macOS.

What is the short answer?

To completely uninstall an app: quit it, run the developer's uninstaller if one exists, then move the app to the Trash. After that, look in ~/Library for folders named after the app or its bundle ID (for example com.example.app), and switch off anything it left in System Settings › General › Login Items & Extensions. Empty the Trash only after you're sure nothing else broke.

Key takeaways

  • If the developer ships an uninstaller, use it. Apple recommends the same.
  • Leftovers mostly live in a handful of ~/Library folders, named after the app or its bundle ID.
  • Background helpers (launch agents) can keep running after the app is gone, so check Login Items.
  • Uninstalling never deletes your documents and never cancels a subscription.
  • Move things to the Trash instead of deleting them outright, so you can put them back if something breaks.

What does dragging an app to the Trash leave behind?

When you drag an app to the Trash, you remove the application bundle: the .app file with the program and its built-in resources. Data the app created while running lives elsewhere, mostly in your user Library folder. Apple's developer guidelines tell apps to keep support files in ~/Library/Application Support, rebuildable data in ~/Library/Caches, and preferences in ~/Library/Preferences, usually in a folder or file named after the app's bundle identifier.

This is on purpose: reinstall later and your settings are still there. The downside is that removed apps slowly leave orphaned folders behind, and some of them (browser profiles, offline media, virtual machine images) get large.

Should you use the developer's uninstaller first?

Yes, when one exists. Apple's own guidance is that for apps not made by Apple, an included uninstaller "is the best way to delete the app" along with any login items, extensions or other data it stored elsewhere. Apps that install system components need one most, such as VPNs, security tools, audio drivers, virtualization software and large creative suites.

Places to look:

  1. The app's folder in Applications (some apps install as a folder with an "Uninstall" app inside).
  2. The app's own menus or settings. Look for "Uninstall", "Remove" or "Reset".
  3. The developer's support site, which may offer a separate uninstaller download.

If you come up empty, the manual method below works for most apps.

How do you uninstall an app manually, step by step?

Before you start: make sure you have a recent Time Machine backup. You probably won't need it, but with one, any mistake is a small inconvenience instead of a lost afternoon.

  1. Quit the app. If it has a menu bar icon, quit it from there as well. If macOS says the app is in use, restart and try again.
  2. Move the app to the Trash. In Finder, open Applications, select the app and choose File › Move to Trash. Enter an administrator password if asked. Apps from the App Store can also be removed from Launchpad (or the Apps view on newer macOS versions) by holding the icon until it jiggles and clicking the delete button.
  3. Open your Library folder. In Finder, choose Go › Go to Folder (Shift-Command-G), type ~/Library and press Return. The folder is hidden by default, which is why many people never find it.
  4. Check the usual leftover folders. Look for folders or files named after the app, the developer or the bundle ID. (Our guide to the Library folder explains what each ~/Library folder holds.)
    • ~/Library/Application Support/
    • ~/Library/Caches/
    • ~/Library/Preferences/ (files ending in .plist)
    • ~/Library/Containers/ and ~/Library/Group Containers/ (used by sandboxed apps, including App Store apps)
    • ~/Library/Saved Application State/
    • ~/Library/Logs/
    • ~/Library/HTTPStorages/ and ~/Library/WebKit/
    • ~/Library/LaunchAgents/
  5. Check the system-wide Library too. Some apps install for all users. Repeat the search in /Library/Application Support/, /Library/LaunchAgents/ and /Library/LaunchDaemons/. Be stricter here: only move items whose names clearly match the app you removed.
  6. Move matches to the Trash, but don't empty it yet. Leave them there for a day or two as a safety net.
  7. Restart and confirm everything you still use works normally. Then empty the Trash.

A tip for step 4: Finder's search field can search "This Mac" or only the current folder. Searching inside ~/Library with the app's name or the developer's name is often faster than browsing each folder.

How do you remove login items and background helpers?

Some apps install a small launch agent or launch daemon, a background process that macOS starts at login or at boot. These are the pieces most likely to outlive the app.

  1. Open System Settings › General › Login Items & Extensions.
  2. Under Open at Login, select the app if it's listed and click the Remove (–) button.
  3. In the Allow in the Background list, turn off any entry that belongs to the removed app.
  4. If the entry keeps coming back, find its file. Launch agents are .plist files in ~/Library/LaunchAgents/ or /Library/LaunchAgents/, and daemons live in /Library/LaunchDaemons/. Move the matching file to the Trash and restart.

To see whether a helper is still loaded for your user, open Terminal and run:

# Replace "example" with part of the app or developer name
launchctl list | grep -i example

No output means nothing matching is loaded for your user session.

What about apps installed with a .pkg installer?

Apps that came as a .pkg installer can put files outside the Applications folder, and macOS keeps a receipt listing them. You can read those receipts with pkgutil:

# List installed package receipts (filter by developer name)
pkgutil --pkgs | grep -i example

# Show where a package installed its files
pkgutil --pkg-info com.example.pkg

# List every file path that package installed
pkgutil --files com.example.pkg

Use that file list as a map, not a delete list. It often includes shared directories such as usr or Library that other software needs too. Remove only the items that clearly belong to the app. Once you're done, sudo pkgutil --forget com.example.pkg removes the receipt itself. It doesn't delete any files.

Which uninstall method should you use?

MethodRemoves leftoversRiskTimeBest for
Drag app to Trash onlyNoVery lowSecondsSmall, simple apps you may reinstall
Developer's uninstallerUsually, including helpersLow1 to 2 minutesVPNs, drivers, security and creative suites
Manual Library cleanupYes, if thoroughLow to medium5 to 15 minutesApps with no uninstaller
pkgutil receipt reviewYes, for packaged filesMedium10+ minutesApps installed with a .pkg
Uninstaller app that shows related filesUsuallyLow, if it lets you review1 to 2 minutesRemoving several apps at once

What is safe to remove, and what should you leave alone?

LocationWhat lives thereAfter the app is removed
~/Library/Caches/<app or bundle ID>Rebuildable cache dataSafe to remove
~/Library/Saved Application State/<bundle ID>.savedStateWindow positionsSafe to remove
~/Library/Logs/<app>Diagnostic logsSafe to remove
~/Library/Preferences/<bundle ID>.plistSettingsSafe, but you lose settings if you reinstall
~/Library/Application Support/<app>Databases, profiles, sometimes your dataCheck first. Some apps keep libraries or projects here
~/Library/Containers/<bundle ID>A sandboxed app's whole data folderCheck first. Can include in-app documents
~/Library/LaunchAgents/<bundle ID>.plistBackground helper definitionRemove if it matches the app, then restart
Anything named com.apple.*macOS and Apple appsLeave alone
/System and its contentsmacOS itselfLeave alone (it is protected anyway)

What should you not do?

  • Don't delete a folder just because it's big. Some apps keep photo libraries, game saves or project files in Application Support. Open it and look before you remove it.
  • Don't remove anything named com.apple.*. Built-in apps such as Mail and Notes can't be uninstalled, and their data supports macOS itself.
  • Don't empty the Trash right away. Keep removed items for a day or two. File › Put Back restores them to where they came from.
  • Don't run sudo rm -rf on paths from a pkgutil --files list. Those lists include shared system directories.
  • Don't expect uninstalling to cancel a subscription. That's always a separate step.
  • Don't uninstall security or VPN software by dragging alone. Their network extensions and daemons usually need the vendor's uninstaller.

Can an app do this more safely?

A dedicated uninstaller saves you from hunting through Library folders by hand, as long as it shows its work. It should list every related file before anything is removed, let you untick items, move everything to the Trash instead of erasing it, and work without an account or usage tracking. Be wary of any tool that removes things in one click without showing you a list.

Freshist's Apps tool works this way. It finds the files related to each app, shows you the full list with sizes, and moves only what you approve to the Trash. Scanning is free, so you can compare its list with what you found by hand. See how it compares or the Help & Docs.

Sources

Frequently asked questions

Does dragging an app to the Trash uninstall it completely?

It removes the app itself, which is usually most of its size. Settings, caches, saved state and sometimes background helpers stay in your Library folder until you remove them. Most of that is small, but a helper can keep running or keep showing up in Login Items.

Will uninstalling an app delete my documents?

No. Apple notes that deleting or uninstalling an app does not remove documents or other files you created with it. You may still need the app, or another one, to open those files later.

Does deleting an app cancel its subscription?

No. Deleting or uninstalling an app does not cancel a subscription bought through it. Cancel it separately, in the App Store account settings for App Store purchases or with the developer for anything bought on their website.

Is it safe to delete folders in ~/Library?

Folders that clearly belong to an app you have already removed are generally safe to move to the Trash. Leave anything you do not recognise, anything named after Apple (com.apple.*), and everything under /System alone.

Why does an app I deleted still appear in Login Items?

A launch agent or helper the app installed is still on disk. Turn it off in System Settings › General › Login Items & Extensions, then look for its .plist file in ~/Library/LaunchAgents or /Library/LaunchAgents and move that to the Trash.

Keep reading

7 min read

Developer Caches on Mac: What's Safe to Clear

Where Xcode, simulators, npm, pnpm, Homebrew, Docker, pip, uv and AI model caches live on a Mac, what rebuilds, and each tool's own cleanup command.

storagedevelopercleanup

11 min read

Do You Need a Mac Cleaner? An Honest Buyer's Guide

Most Macs don't strictly need a cleaner. What macOS already handles, when one actually helps, how to choose a safe one, and the red flags to avoid.

buying-guidecleanupprivacystorage