How to Find Leftover Files From Apps You've Already Uninstalled

A useful experiment: open ~/Library/Application Support on a Mac you’ve owned for two years. Count the folders. Now count how many of those apps you actually still have installed.

For most people the second number is roughly half the first. The rest are leftovers — caches, preferences, saved data from apps you trashed months or years ago, sitting on your SSD, doing nothing.

Why leftovers stick around

When you drag an app to the Trash, macOS removes the .app bundle. That’s it. Every file the app wrote to your user library during its life is still where it was when you last quit it. There’s no built-in mechanism to clean those up, because Apple can’t safely tell whether you might want to reinstall the app and pick up where you left off.

So the burden of garbage collection is on you — or on a tool that knows what to look for.

What “orphaned” actually means

A file is orphaned when its parent app no longer exists. There are a few flavors of this:

• Cleanly orphaned — the app’s folder in ~/Library/Application Support/<App Name> exists, but the app itself is gone from /Applications. Easy to spot.
• Bundle-ID orphaned — files in ~/Library/Preferences or ~/Library/Containers named after a bundle ID like com.figma.Desktop that no longer corresponds to an installed app. Harder to spot because the names are cryptic.
• Group orphaned — Group Containers shared between an app and its extensions. If neither the app nor the extension is installed anymore, the Group Container is dead weight.
• LaunchAgent orphaned — .plist files in ~/Library/LaunchAgents pointing at executables that don’t exist. These actively cause errors at every login.

The manual hunt

If you want to find leftovers by hand, here’s the process. Plan on it taking 30–60 minutes for a Mac that’s been in use for a few years.

1. Open Finder, hit Cmd+Shift+G, go to ~/Library/Application Support.
2. Sort by name. Go down the list and ask “do I still have this app installed?” for each folder. Toggle Spotlight or just check /Applications to be sure.
3. For each folder where the answer is no, note the size and add it to a “delete” list.
4. Repeat for ~/Library/Caches, ~/Library/Preferences, ~/Library/Containers, ~/Library/Group Containers, ~/Library/Saved Application State, ~/Library/Logs.
5. Check ~/Library/LaunchAgents and /Library/LaunchAgents for entries pointing at missing apps.
6. Move everything to Trash. Empty.

The painful part is step 2 with the cryptic bundle IDs. Some bundle IDs are obvious (com.spotify.client). Many aren’t (com.runningwithcrayons.Alfred-Preferences — that’s Alfred, naturally).

Skip the manual huntSweep finds every leftover preference, cache, and support file in seconds — and only removes what you OK. Download Sweep free →

How to decode a bundle ID

If you see a folder you don’t recognize, you can usually figure out what it belonged to:

• Search the bundle ID on Google. Most bundle IDs are unique enough that the first hit is the app’s website.
• Look at the contents. A Cache.db next to a Network folder is usually an Electron app — check the Local Storage folder for hints about which one.
• Check the parent folder for a .plist with a CFBundleDisplayName field.

If you can’t identify it after five minutes, it’s probably safe to leave it alone — it’s small, and you don’t want to delete something a system service relies on.

How much space are we talking about?

A few real numbers from Macs I’ve cleaned up:

• 6-month-old Mac, light usage: 1–3 GB of orphans
• 2-year-old Mac, normal usage: 5–15 GB
• 5-year-old Mac, design or video work: 20–60 GB
• Anything with Adobe history: add 5–20 GB

The biggest contributors are usually:

1. Old Adobe app caches (/Library/Application Support/Adobe/)
2. Old browser-based app caches (Slack, Discord, Spotify clones)
3. Old game data (~/Library/Application Support/Steam, anything from Epic Games)
4. Old IDE caches (Xcode is the worst — ~/Library/Developer can be 30+ GB by itself)
5. Old sync clients (Dropbox, Google Drive, OneDrive — each can leave several GB of metadata)

Finder tricks for hunting orphans

A few things that help when you’re doing this manually:

• View → Show View Options → Show item info. This shows folder sizes inline, which makes it easier to spot the giant orphans.
• Cmd+J → Calculate all sizes. Same idea, more reliable.
• Sort by Date Modified. Folders that haven’t been touched in a year are excellent leftover candidates.
• Quick Look (Space). Lets you peek at a .plist to figure out what it belongs to without opening anything.

What to be careful about

A few categories of files in ~/Library look like leftovers but aren’t:

• Anything in ~/Library/Mobile Documents — that’s iCloud Drive
• ~/Library/Containers/com.apple.* — Apple system containers
• ~/Library/CloudStorage — third-party sync providers Apple manages
• Anything in ~/Library/Keychains — your saved passwords

When in doubt, leave Apple-prefixed and system-looking files alone. The leftovers worth cleaning up are third-party app data, almost always.

Using Sweep to do this in seconds

Sweep’s leftover-files scan does exactly what we just described, but in a fraction of the time:

• Scans every standard library location
• Cross-references against installed apps to find orphans
• Identifies bundle-ID-only folders for apps that are no longer present
• Flags LaunchAgents pointing at missing executables
• Shows everything with sizes before removing anything

The preview matters. There’s no “trust the algorithm” mode — every file Sweep finds is shown to you, and you confirm what goes.

There’s a faster waySweep does the same hunt in seconds, with a preview before anything is removed. Try Sweep free →

Should you actually delete leftovers?

For most apps, yes. The data is from a version you were last running months or years ago — even if you reinstall, the new version may not be compatible with the old preferences anyway, and many apps deliberately ignore old prefs to avoid carrying forward bugs.

A few cases where you might want to keep them:

• Apps with substantial saved work (DAWs, video editors, design tools — check for project files first)
• Apps with license files you’d struggle to recover (rare these days, but it happens)
• Apps you specifically plan to reinstall and continue using

If you’re not sure, move the folder to a backup location before deleting. Or just trust the preview and uncheck anything that looks valuable.

How often to do this

For a typical Mac, once or twice a year is plenty. The exception is if you try a lot of apps — designers, developers, anyone who downloads-and-discards regularly should clean up every 3–4 months.

The accumulation is gradual, so you won’t usually notice the day-to-day impact. The “huh, my Mac feels faster” effect mostly comes from removing dead LaunchAgents (faster login) and freeing enough disk space that APFS isn’t fighting for room (faster file ops).

Quick recap

To find leftover files from uninstalled apps:

• Open ~/Library (Cmd+Shift+G in Finder)
• Check Application Support, Caches, Preferences, Containers, Group Containers, Saved Application State, Logs
• Identify folders for apps that are no longer in /Applications
• Check ~/Library/LaunchAgents and /Library/LaunchAgents for orphan helpers
• Delete what’s clearly orphaned, leave what’s ambiguous
• Empty Trash

Or run Sweep’s leftover-files scan and review the preview. Honestly, the manual route is fine if you only have a handful of apps to check. The moment you’re trying to clean up after years of accumulated software experiments, a tool earns its keep.