How to Completely Uninstall Apps on Mac (2026 Guide)

Deleting a Mac app by dragging it to the Trash feels satisfying — until you realize the app left behind dozens of files scattered across your Library folder, quietly occupying gigabytes of space. This guide shows you how to completely uninstall apps on Mac using three different methods, explains exactly which hidden files each method leaves behind, and helps you decide which approach fits your situation.

Why Dragging to Trash Is Not a Full Uninstall

macOS apps are self-contained bundles, but they routinely store supporting data outside the .app file itself. Preferences, caches, crash logs, application support data, and saved state can end up in half a dozen locations. When you drag an app to the Trash, macOS removes only the bundle — none of those companion files.

Over time, these orphaned files add up. A handful of uninstalled creative apps, browsers, or productivity suites can leave behind several gigabytes of data that serves no purpose.

Where Apps Store Their Files

Before comparing uninstall methods, it helps to know the real folders macOS apps write to. All paths below use the tilde (~) shorthand for your home folder (/Users/yourname).

• ~/Library/Preferences/ — .plist settings files, usually named with the app's bundle ID (e.g. com.apple.safari.plist)
• ~/Library/Application Support/ — App data, databases, offline content
• ~/Library/Caches/ — Temporary cached data; safe to delete, but it rebuilds on next launch
• ~/Library/Logs/ — Crash reports and diagnostic logs
• ~/Library/Saved Application State/ — Window state from your last session
• ~/Library/Containers/ — Sandboxed App Store apps store everything here
• ~/Library/Group Containers/ — Data shared between an app and its extensions
• /Library/Application Support/ — System-wide support files (requires admin access)
• /Library/LaunchDaemons/ and /Library/LaunchAgents/ — Background services that run at login or boot

The ~/Library folder is hidden by default. To open it, open Finder, hold Option, click the Go menu, and select Library.

Method 1: Launchpad Drag-to-Delete

This works only for App Store apps and offers the deepest system-level cleanup of any built-in method.

1. Open Launchpad (pinch with four fingers or click it in the Dock).
2. Click and hold any app icon until icons start to wiggle.
3. Click the X button on the app you want to remove.
4. Confirm deletion in the dialog that appears.

Because App Store apps run inside macOS's sandbox, the system knows their ~/Library/Containers/ folder and removes it automatically. This is the closest thing to a full uninstall that macOS offers natively — for App Store apps only.

What it still leaves behind: Items in ~/Library/Group Containers/ shared with other apps, any files the app wrote outside its sandbox (some apps do this), and any LaunchAgents the app installed.

Method 2: Finder Trash (for Non-App Store Apps)

Most professional and developer apps are distributed outside the App Store and have no sandbox restrictions, which means they write files wherever they like.

1. Open Finder and navigate to Applications.
2. Locate the app, right-click it, and choose Move to Trash (or drag it to the Trash).
3. Empty the Trash.

This removes the .app bundle. Everything else stays.

What it leaves behind: Typically all of it — preferences, caches, application support data, logs, saved state, and any background services the app installed. For a lightweight utility this might be a few kilobytes. For a media app or developer tool, it can be multiple gigabytes.

Method 3: Manual Leftover Cleanup via Terminal

After trashing the app bundle, you can track down leftover files manually. The most reliable approach is to search for the app's bundle identifier or company name.

1. Find the bundle ID before deleting the app. In Terminal:

mdls -name kMDItemCFBundleIdentifier /Applications/AppName.app

2. Search your Library for files matching that ID. Replace com.example.app with the actual bundle ID:

find ~/Library -iname "*com.example.app*" 2>/dev/null

3. Also search by the developer or app name, since not all files use the bundle ID:

find ~/Library -iname "*AppName*" 2>/dev/null

4. Review the results carefully. Delete files you are confident belong only to that app.
5. Check system-level locations with sudo if the app installed a daemon:

sudo find /Library -iname "*com.example.app*" 2>/dev/null

What this leaves behind: Anything you miss. Manual searches are thorough if you know what to look for, but easy to get wrong — especially for apps that use a parent company name across multiple products.

Side-by-Side Comparison

Method 4: Use a Leftover-Aware Uninstaller

If you regularly uninstall apps and want confidence that nothing is left behind, a dedicated tool handles the discovery step automatically. Crumb is a native macOS utility that finds installed apps alongside all their associated Library files in one view. Select an app from the list, review the leftover files it detected (grouped by type — caches, preferences, support data, logs), check or uncheck individual items, and remove everything in one pass.

This approach is particularly useful for apps that spread files across multiple Library locations or install LaunchDaemons in system-level folders that a simple find in your home directory would miss entirely.

What Is Safe to Delete — and What Is Not

Not every file an app leaves behind is harmless to remove. Here is the general guidance:

• Safe to delete: Anything in ~/Library/Caches/ for a removed app. Crash logs in ~/Library/Logs/. Saved state in ~/Library/Saved Application State/. Preferences files for apps you have already removed.
• Delete with care: Files in ~/Library/Application Support/ may include documents, databases, or locally stored data you have not backed up elsewhere. Read the folder contents before deleting.
• Do not delete without knowing what it is: Anything in ~/Library/Group Containers/ that is shared with another app you still use. Any LaunchDaemon or LaunchAgent unless you are certain which app it belongs to and that app is gone.
• Never delete: System framework files, anything inside /System/, or files that belong to apps you still have installed.

If you are unsure whether a folder is safe to remove, Crumb's built-in AI can explain what a given folder is for and rate its removal risk — useful before permanently deleting something unfamiliar. Cleaning is permanent: emptying the Trash cannot be undone, so review before you commit.

Reclaiming Space from System Data

macOS's Storage settings often show a large "System Data" category that accumulates over time alongside unused app leftovers. This includes purgeable files, old iOS backups, and cached content that macOS does not automatically release. After a thorough app uninstall pass, running a cache and system-data cleanup can recover additional space beyond what the leftover files alone account for.

Conclusion

The right method depends on where the app came from and how thorough you want to be. Launchpad deletion is the best built-in option for App Store apps; Finder trash gets the job done quickly but leaves files behind; manual Terminal searches work if you know what to look for and are willing to dig. For a repeatable, low-effort workflow that catches everything — especially for non-App Store apps with scattered support files — a leftover-aware tool like download Crumb removes the guesswork and ensures a genuinely clean uninstall.