Dragging an app to the Trash feels like a clean break, but macOS almost never removes everything the app installed. Caches, preference files, support folders, login items, and crash logs scatter across hidden Library directories and quietly consume gigabytes of space. This guide shows you exactly how to remove app leftover files on Mac — both the manual way, digging through your Library folder folder by folder, and an automated route that matches a deleted app's bundle ID to every file it ever created.
Why Leftover Files Accumulate After Uninstalling
macOS has no built-in uninstaller. When you delete an app, the system removes only the .app bundle itself. Everything else the app created during its lifetime stays on disk until you delete it manually. Common culprits include:
- Application caches in
~/Library/Caches/ - Preferences in
~/Library/Preferences/ - Application support data in
~/Library/Application Support/ - Crash logs in
~/Library/Logs/and/Library/Logs/ - Launch agents and daemons in
~/Library/LaunchAgents/and/Library/LaunchDaemons/ - Container data in
~/Library/Containers/(sandboxed Mac App Store apps) - Group containers in
~/Library/Group Containers/ - Saved application state in
~/Library/Saved Application State/
For a heavily used app like Spotify, Dropbox, or Adobe Creative Cloud, these remnants can total hundreds of megabytes or more.
Before You Start: Two Rules to Follow
- Cleaning is permanent. Unlike deleting items on your Desktop, files deleted from the Library are not easily recoverable once the Trash is emptied. Move uncertain files to a staging folder or a compressed archive before permanently removing them.
- Do not delete folders you don't recognize. Many system frameworks and third-party components share names that don't obviously match any app you installed. When in doubt, research a folder name before removing it — or use a tool with a built-in safety explanation (more on that below).
Step 1 — Open the Hidden Library Folder
The user Library is hidden by default. You can reveal it in two ways:
Option A — Finder shortcut:
- Open Finder.
- Hold Option and click the Go menu.
- Select Library (it only appears when Option is held).
Option B — Terminal:
open ~/LibraryThis opens your user Library in a Finder window. The system Library at /Library (note: no tilde) requires navigating via Go > Go to Folder and typing /Library.
Step 2 — Search by App Name Across Library Subdirectories
The most reliable manual method is to search each relevant subdirectory for the app's name or its developer's reverse-DNS identifier (e.g., com.spotify.client). You can do this in Finder or Terminal.
Finder search:
- With the Library window open, press Cmd+F.
- Change the search scope to This Mac or, better, limit it to the current folder.
- Type the app's name (e.g.,
Spotify) to see matching files and folders. - Repeat for the developer name or bundle identifier if results are sparse.
Terminal search (more thorough):
# Replace "Spotify" with the app name you're hunting
find ~/Library -iname "*spotify*" 2>/dev/null# Also check the system Library (requires no sudo for reading)
find /Library -iname "*spotify*" 2>/dev/nullCommon directories to inspect manually:
| Path | What it typically holds | Safe to delete? |
|---|---|---|
~/Library/Caches/com.app.name |
Temporary cache data, can be rebuilt | Generally yes |
~/Library/Preferences/com.app.name.plist |
App settings and preferences | Yes, if app is gone |
~/Library/Application Support/AppName |
User data, databases, extensions | Check contents first |
~/Library/Containers/com.app.name |
Sandboxed app data (App Store apps) | Yes, if app is gone |
~/Library/LaunchAgents/com.app.name.plist |
Background processes that auto-start | Yes — and definitely remove |
/Library/LaunchDaemons/com.app.name.plist |
System-wide background services | Yes — and definitely remove |
~/Library/Logs/AppName |
Crash and diagnostic logs | Yes |
~/Library/Saved Application State/com.app.name.savedState |
Window restore state | Yes |
Step 3 — Remove Found Files
Once you have identified files that belong to the removed app, move them to the Trash:
# Move a specific folder to Trash from Terminal (safer than rm)
# macOS 12+: use the trash command if installed, or simply move to ~/.Trash
mv ~/Library/Application\ Support/Spotify ~/.Trash/After moving everything to the Trash, verify your disk space recovered in Apple menu > About This Mac > More Info > Storage (macOS Ventura and later: System Settings > General > Storage) before you empty it. Once you're confident the right files are gone, empty the Trash.
Step 4 — Check for System-Level Leftovers
Some apps install components that require elevated permissions to remove. Common locations to audit:
/Library/Application Support/— system-wide support files/Library/Extensions/— legacy kernel extensions (.kext)/Library/PrivilegedHelperTools/— helper binaries used by apps that need admin access/Library/StartupItems/— rarely used on modern macOS, but some older apps still write here
sudo find /Library -iname "*appname*" 2>/dev/nullItems in /Library/PrivilegedHelperTools/ and /Library/Extensions/ should be removed carefully. If you don't recognize a kernel extension, look up its bundle identifier before deleting it.
The Automated Route: Matching Leftovers by Bundle ID
The manual approach works, but it's tedious, easy to miss entries, and requires you to know the app's name variants and reverse-DNS identifier. An automated leftover finder sidesteps this by cross-referencing the app's bundle ID against every file on disk — catching things like com.developer.appname even when the folder is named something entirely different.
Crumb does this from its Uninstall tab. Select any app you've already removed (or one you're about to remove), and Crumb lists every surviving file associated with it — caches, preferences, support data, launch agents, and container folders — organized by location. You can review each item, check its size, and remove them all in one pass. Because it uses the bundle ID as the matching key rather than a plain text search, it catches remnants that a simple Finder search for the app's display name would miss.
For folders you're unsure about, Crumb's built-in "Is this safe to delete?" feature explains what the folder contains and what happens if you remove it — useful when you encounter a path like ~/Library/Application Support/com.developer.shared-component that doesn't obviously map to one app.
What NOT to Delete
A few cautions to keep in mind as you clean up leftover files:
- Shared frameworks: Some items in
~/Library/Application Support/are shared across multiple apps (e.g., WebKit storage, Sparkle updater caches). Deleting them might break a different app you still use. - Keychain entries: App passwords stored in Keychain are not in the Library folder; they live in Keychain Access and are unaffected by manual Library cleanup.
- User data you intend to keep: Some apps store documents or databases in
Application Support. Read the folder contents before deleting wholesale. - Anything in
/System/: macOS protects this via System Integrity Protection (SIP). You should never need to touch it for app cleanup.
How Often Should You Clean Up Leftovers?
There's no single right answer, but a reasonable habit is to run a leftover check any time you uninstall a substantial application — particularly creative tools, cloud-sync clients, or security software, which tend to install the most system-wide components. On a Mac you've used for several years, a one-time audit of the full Library often recovers several gigabytes from apps long since forgotten.
Conclusion
To remove app leftover files on Mac, you need to look beyond the Trash and into the hidden Library folders where macOS stores caches, preferences, support data, and background services. The manual steps — opening ~/Library, searching by app name, and removing matched files — give you full control, but they're time-consuming and easy to do incompletely. An automated approach that matches on bundle ID catches everything the manual search might miss. Either way, go carefully, move files to the Trash before emptying it, and skip anything you can't positively identify as belonging to the removed app.
If you'd like to skip the Library archaeology entirely, download Crumb and let its Uninstall tab surface every leftover for you — with size, path, and a plain-English explanation of what each item is.