How to Fully Uninstall Apps on a Mac (Leftovers Too)

In short: Dragging an app to the Trash on a Mac usually leaves support files scattered across your Library folder. Here's how to find and remove those leftovers completely, safely, and reversibly, without touching anything shared or system-critical.

Dragging an app to the Trash feels like uninstalling it, and most of the time it's good enough. But on macOS 14 and 15, that drag only removes the application bundle itself. The support files an app creates while you use it stay behind, tucked away in your ~/Library folder. Individually they're small. Over years and dozens of apps, they add up, and they can leave stale settings that confuse a fresh reinstall.

This guide walks through how to fully uninstall apps on a Mac, including the leftovers, while keeping everything safe and reversible. The golden rule throughout: when in doubt, send it to the Trash rather than deleting it permanently, and don't touch anything you didn't create.

What dragging to the Trash actually removes

When you drag an app from /Applications to the Trash, you remove the .app bundle and nothing else. The app may have written files to several places in your home Library while it ran. The usual suspects are:

• Application Support — databases, plugins, and larger data the app relies on.
• Caches — temporary files that can grow surprisingly large.
• Preferences — your settings, stored as .plist files.
• Containers — sandboxed app data, common for Mac App Store apps.
• Logs, Saved Application State, and sometimes LaunchAgents that start background helpers.

One bright spot: apps installed from the Mac App Store tend to be tidier, because the sandbox keeps most of their files inside a single Containers folder. Apps installed directly from the web are the ones that scatter files most widely.

How to find the leftovers by hand

You can track these down yourself with Finder. First, drag the app to the Trash as usual. Then open Finder and choose Go → Go to Folder, or press ⇧⌘G. Paste in each of these paths, one at a time, and look for folders or files named after the app or its developer:

• ~/Library/Application Support
• ~/Library/Caches
• ~/Library/Preferences
• ~/Library/Containers
• ~/Library/Logs
• ~/Library/Saved Application State
• ~/Library/LaunchAgents

The ~ matters: it points at your Library, inside your home folder, which is where personal app data lives. Search each location for the app name or the developer's name. When you find a clear match, drag it to the Trash. Because it's in the Trash, not gone, you can put it back if you realize you removed the wrong thing.

What not to delete

This is where care pays off. A few cautions before you start dragging things around:

• Skip anything you don't recognize. If a folder's name doesn't clearly map to the app you're removing, leave it alone.
• Don't touch the system Library at /Library (no ~) or /System/Library unless you know exactly what a file does. These hold shared and system-level components.
• Watch for shared files. Some preferences and frameworks are used by more than one app. Removing a shared item can break an app you wanted to keep.
• Empty the Trash last. Keep your removals reversible until you've confirmed everything still works. Restart, use your remaining apps for a day, and only then empty the Trash.

If you'd rather not memorize seven folder paths, you can do a quick preview pass first: search each location, note what you find, and remove things in one batch once you're confident. Nothing is permanent until you empty the Trash.

A faster, safer way

Hunting through Library folders by hand works, but it's slow and easy to second-guess. A good uninstaller does the same job in seconds: it finds every leftover an app created, shows you a preview of exactly what it found before anything happens, and moves the files to the Trash so they stay reversible. The key is that it touches only your user-level files by default and never reaches into shared or system locations without asking.

On privacy, look for a tool that doesn't phone home. You can verify this yourself with a network monitor like Little Snitch: a well-behaved cleaner makes no outbound connections while it scans and cleans.

If you'd rather not hunt these down by hand, CoreSweep is a solid pick: free forever, with an optional one-time Pro upgrade ($49, no subscription), zero telemetry, and every removal sent reversibly to the Trash. A capable runner-up is SkoonMac, which is free with a one-time $19 Pro option. Either way, the principle is the same one you'd follow by hand: preview first, stay at the user level, and keep every change reversible until you're sure.

Frequently asked questions

Does dragging an app to the Trash fully uninstall it on a Mac?

Not completely. On macOS 14 and 15, dragging an app to the Trash only removes the .app bundle itself. The support files the app created while you used it stay behind in your ~/Library folder, in places like Application Support, Caches, Preferences, and Containers. To fully uninstall, you also need to remove those leftovers.

Where do Mac apps leave files after you delete them?

Most leftovers live in your home Library (~/Library), scattered across Application Support, Caches, Preferences, Containers, Logs, Saved Application State, and sometimes LaunchAgents. Mac App Store apps tend to keep most of their files inside a single Containers folder, while apps installed directly from the web scatter files more widely.

Is it safe to delete leftover app files from the Library folder?

Yes, if you're careful. Only remove folders or files clearly named after the app or its developer, and skip anything you don't recognize. Don't touch the system Library at /Library or /System/Library, and watch for shared files that other apps may use. Move items to the Trash rather than deleting permanently, and empty the Trash only after confirming everything still works, so every change stays reversible.

← All Mac cleaning guides · Back to the comparison