You deleted the app — but it left its entire closet behind
On a Mac, uninstalling an app seems simple: drag it to Trash, done. And for the app itself, that works. But the app's settings, caches, login helpers, and support files? They stay behind, scattered across your Library folder, quietly occupying space for years.
One deleted app leaves maybe 50 MB of orphans. But after a few years of installing and removing apps, those leftovers add up to gigabytes — and they become part of the mysterious "System Data" category that Apple never explains.
Why dragging to Trash doesn't fully uninstall
macOS doesn't have a centralized uninstaller like Windows does. When you drag an app from Applications to Trash, you're removing the app bundle — the .app file — and nothing else. The app's support files were created in different folders the first time you launched it, and macOS makes no effort to clean them up when the app is gone.
This isn't a bug, it's a design choice. Apple's philosophy is that these files are small and harmless. And individually, they usually are. The problem is accumulation over time.
Where leftovers hide
Almost all app leftovers live inside ~/Library — a folder that's hidden by default in Finder. (To open it: click Go in the menu bar, hold the Option key, and click Library.) Here's where to look:
| Folder | What's there | Typical size per app |
|---|---|---|
~/Library/Application Support/ | App data, databases, plugins | 10 MB – 2 GB |
~/Library/Caches/ | Cached files, offline data | 50 MB – 5 GB |
~/Library/Preferences/ | Settings files (.plist) | A few KB each |
~/Library/Saved Application State/ | Window positions, last-open state | A few KB – 10 MB |
~/Library/LaunchAgents/ | Background processes, auto-start rules | A few KB (but they run silently) |
~/Library/Logs/ | App-specific log files | 1–50 MB |
How to find leftovers by app name
The simplest approach: search by the app's name (or the developer's name) in each of those folders.
- Open
~/Libraryin Finder. - Use Cmd + F to search within the Library folder.
- Type the app's name — for example, "Slack" or "Spotify."
- Look at the results. You'll see folders and
.plistfiles named after the app.
Move them to Trash. That's the manual uninstall — tedious, but thorough.
Tip: some apps use the developer's name instead of the app's name. For example, Sublime Text stores files under "com.sublimetext" and Chrome uses "com.google.Chrome." If you don't find anything by the app's display name, try the developer's name or reverse-domain format.
App Store apps are cleaner — but not perfect
Apps installed from the Mac App Store are sandboxed. This means their data lives in a contained area, and when you delete the app through Launchpad (long-press the icon, click the X), macOS removes most of the associated data too.
Most — but not always all. Preferences in ~/Library/Preferences and some cached data can still linger. It's better than the drag-to-Trash method, but it's still not guaranteed to be spotless.
The tricky ones: LaunchAgents and LaunchDaemons
Some apps install background helpers that keep running even after you delete the main app. These live in:
~/Library/LaunchAgents/— per-user background tasks/Library/LaunchAgents/— system-wide background tasks (all users)/Library/LaunchDaemons/— system-level services
They're .plist files that tell macOS to run something at login or on a schedule. If an app you deleted left one behind, it might be trying (and failing) to start a process that no longer exists — wasting CPU cycles and occasionally throwing error logs.
.plist if you recognize the app name in its filename and you've already deleted that app. When in doubt, leave it alone — a stray preferences file wastes a few KB; a deleted system daemon can break things.A few apps that leave especially large leftovers
- Docker — containers and images in
~/Library/Containers/com.docker.dockercan reach 10–30 GB. - Xcode — DerivedData, archives, and simulators can total 20–60 GB even after Xcode is removed.
- Adobe Creative Cloud — installs helpers, updaters, and caches across multiple Library subfolders; a full cleanup often requires Adobe's own removal tool.
- Slack, Teams, Discord — their Electron-based caches in
~/Library/Application Supportcan grow to several GB each.
If you've uninstalled any of these and never cleaned the leftovers, there's a good chance you have 5–20 GB of orphaned files. Checking ~/Library/Application Support sorted by size is the fastest way to find out — it's also one of the biggest contributors to unexplained disk usage.
What NOT to touch
Never delete files you don't recognize. If a folder in ~/Library/Application Support has a cryptic name like com.apple.TCC or AddressBook, it belongs to macOS. Stick to folders clearly named after apps you've already removed. And avoid anything inside /System entirely — that's Apple's territory, and removing files there can make your Mac unbootable.
Or let Gigatidy find what's been left behind
Gigatidy scans for orphaned files from apps you've already deleted, shows you exactly what each leftover is, and cleans only what you approve.
Meet Gigatidy →FAQ
How much space do app leftovers typically waste?
On a Mac that's been used for 2–3 years, leftover files from deleted apps commonly total 5–15 GB. Heavy apps like Docker, Xcode, and Adobe products can leave behind much more individually.
Can deleting leftover files break other apps?
Not if you only remove files belonging to apps you've already deleted. Each app's support files are independent. Just make sure you're deleting files for the right app — check the folder name before you trash it.
Do I need a special tool to fully uninstall Mac apps?
You don't need one, but it saves time. The manual method — searching ~/Library by app name — works perfectly. It's just tedious when you have many deleted apps to clean up. The key is knowing where to look, which this guide covers.