← All posts

· 2 min read

Dragging an app to the Trash is not uninstalling it

What a Mac app leaves behind after you trash it, where those files live, and how to remove them without breaking anything else.

appshow-to
Dragging an app to the Trash is not uninstalling it
AI Mac Cleaner's Applications screen listing an installed app with its leftover files found in ~/Library before removal
AI Mac Cleaner's Applications screen listing an installed app with its leftover files found in ~/Library before removal

On a Mac, "uninstalling" usually means dragging the app to the Trash. That removes the app bundle in /Applications, which is often the smaller part. The rest stays behind, and over the years those leftovers add up to gigabytes.

Where apps keep their stuff

  • ~/Library/Application Support/<App> — the main support folder. Databases, downloaded models, offline content. Slack, Discord, Spotify and Adobe apps store gigabytes here.
  • ~/Library/Caches/<bundle id> — temporary data. Safe to remove any time.
  • ~/Library/Containers/<bundle id> and ~/Library/Group Containers — sandboxed apps store everything here, including their caches and settings.
  • ~/Library/Preferences/<bundle id>.plist — settings. Small but they pile up.
  • ~/Library/Saved Application State — window positions.
  • ~/Library/LaunchAgents — background helpers that start at login. An orphaned launch agent keeps trying to start a program that no longer exists, and shows up in Login Items forever.
  • ~/Library/Logs/<App> — logs.

Some apps also install into /Library (all users) or add a kernel or system extension, which needs an administrator password to remove.

How to find leftovers by hand

Look up the app's bundle identifier (something like com.company.appname). In Finder, press Shift-Command-G, go to ~/Library, and search for the identifier and the app's name in the folders above. Anything with that identifier belongs to the app.

Why an uninstaller is safer than guesswork

Names collide. Search ~/Library for "Code" and you find Visual Studio Code, CodeRunner and Xcode's folders. A good uninstaller matches on the exact bundle identifier and shows you the list before anything moves, instead of matching on whatever word happens to appear in a folder name.

A bundle identifier also tells you things a folder name doesn't. com.apple.* or anything genuinely signed by Apple should never be on an uninstall list at all — a tool that can remove those is one error away from breaking the OS. The same goes for an uninstaller's own identifier: it should refuse to list itself, no matter what you search for.

Orphans from apps you already removed

The launch agents and support folders of apps deleted months ago are still there. They are safe to remove as long as no installed app shares the identifier. AI Mac Cleaner's "Leftovers of deleted apps" category finds these by comparing every identifier in ~/Library against the apps actually installed, and keeps anything that matches an installed app or Apple. It's a review-only category, not one ticked for you automatically — the same identifier check that confirms an orphan is safe also means a false match costs nothing, since nothing moves until you say so.

The safe way

Whatever tool you use, three rules: match on identifiers rather than names, review the list, and move to the Trash instead of deleting. If an app misbehaves afterwards, Put Back restores it.