How to Safely Uninstall Mac Apps (Without Leaving Leftovers)
Dragging an app to Trash leaves behind preferences, caches, and support files. Learn where leftovers hide and how to remove them safely.
When you drag a Mac app to the Trash, you remove the .app bundle — but that's often just the tip of the iceberg. Most apps scatter files across multiple locations in your ~/Library folder, and those leftovers remain long after the app is gone.
Why dragging to Trash isn't enough
A typical Mac app stores data in up to 11 different locations:
- Application Support (~/Library/Application Support/) — App databases, configurations, and working files
- Caches (~/Library/Caches/) — Temporary data and cached content
- Preferences (~/Library/Preferences/) — .plist files with your app settings
- Logs (~/Library/Logs/) — Application log files
- Saved Application State (~/Library/Saved Application State/) — Window positions and state restoration data
- Containers (~/Library/Containers/) — Sandboxed app data
- Group Containers (~/Library/Group Containers/) — Shared data between related apps
- LaunchAgents (~/Library/LaunchAgents/) — Background processes and auto-start scripts
- WebKit (~/Library/WebKit/) — Web rendering engine data
- HTTPStorages (~/Library/HTTPStorages/) — Cookie and session data
- CrashReporter (~/Library/Application Support/CrashReporter/) — Crash logs
For a large app like Adobe Creative Cloud or Microsoft Office, these leftover files can total hundreds of megabytes or even gigabytes.
The challenge: knowing what belongs to what
The tricky part isn't finding files in ~/Library — it's knowing which files belong to which app. App developers don't follow a single naming convention. Some use their bundle ID (com.company.appname), others use the app name, and some use abbreviated or completely different names.
This is where confidence scoring becomes important:
- Exact match — The file path contains the exact bundle identifier. This is 100% safe to remove.
- High confidence — The file path contains the app's display name. Very likely related.
- Medium confidence — Partial bundle ID match. Probably related, worth reviewing.
- Low confidence — Fuzzy name matching. Could be related, but verify before deleting.
Apps you should never try to uninstall
macOS includes system apps that are deeply integrated into the operating system. Attempting to remove them can cause serious problems:
- Safari, Finder, App Store
- System Settings (System Preferences)
- Terminal, Activity Monitor
- Mail, Calendar, Contacts, Messages
- Preview, TextEdit, Calculator
- Music, Photos, Maps, Notes
These apps are protected by System Integrity Protection (SIP) and shouldn't be touched.
The manual approach
If you want to manually clean up after uninstalling an app:
- Note the app's bundle identifier (right-click the .app > Show Package Contents > Contents > Info.plist > look for CFBundleIdentifier)
- Open Finder, press Cmd+Shift+G, and navigate to each of the 11 locations listed above
- Search for files matching the bundle ID or app name
- Move matches to Trash
This works, but it's tedious and error-prone. You might miss files with unexpected names, or accidentally delete files shared between apps.
A better approach
CleanMyMacOS automates this process safely. It discovers all installed applications, scans all 11 leftover locations, and assigns a confidence score to each match. You see exactly what was found, how confident the match is, and can decide what to keep or remove. System apps are automatically protected from uninstallation.
The confidence scoring system means you never have to guess. Exact matches are clearly marked as safe, while fuzzy matches are flagged for your review.
CleanMyMacOS can help with this — download it free from the Mac App Store.