Moving an app to the Trash deletes the .app file you see in Applications, and that’s about it. Its caches, settings, databases, and background helpers stay on your Mac, often for a while. As a result, you may end up with a cluttered startup disk or a slower Mac. The good part is, you can still find and remove these leftovers. And here are three ways to do it:
- App Cleaner & Uninstaller: the quickest way that finds leftovers of apps you’ve forgotten. Go to Applications → switch to Remains → select the leftovers → click Remove.
- Finder: a slow, hands‑on way of digging through main directories across your Mac. Use Go to Folder to open Library folders → find files by the app’s name and bundle ID → move the matches to the Trash.
- Terminal: the advanced technical way, based on typing commands. Reveal leftovers with the find command → check the results → trash files in Finder.
Below, you’ll learn where leftovers hide, which of them are worth your attention, and how each method works step by step: an automatic tool, a manual pass in Finder, and Terminal.
This article contains:
What are app leftovers on Mac?
App leftovers, also called remaining files or remnants, are service/support files an app creates outside its bundle: caches, preferences, support data, web storage, and helpers. Most of them are located in the Library folder, which macOS hides by default.
Types of leftover files
| Leftover type | Example path | What it holds | Typical size |
|---|---|---|---|
| Hidden home folders | ~/.ollama, ~/.cache, ~/.config | Data of command‑line and AI tools | Up to tens of GB |
| Containers | ~/Library/Containers/<bundle ID> | All data of a sandboxed app | MBs to tens of GB |
| Application Support | ~/Library/Application Support/<App or developer> | Databases, downloads, projects, local AI files | MBs to 10+ GB |
| Group Containers | ~/Library/Group Containers/<team ID>.<name> | Data shared by apps from one developer | MBs to GBs |
| Caches | ~/Library/Caches/<bundle ID>, /private/var/folders/…/C/<bundle ID> | Temporary data the app can rebuild | Tens of MB to 1+ GB |
| Web data | ~/Library/HTTPStorages, ~/Library/WebKit, ~/Library/Cookies | Cookies, sign‑in sessions, web storage | Hundreds of MB |
| System extensions | /Library/Extensions, /Library/SystemExtensions | Drivers, network and security filters | MBs, active |
| Privileged helpers | /Library/PrivilegedHelperTools | Tools running with admin rights | KB to MBs, active |
| Logs and crash reports | ~/Library/Logs | Activity and crash records | KB to MBs |
| Launch agents and daemons | ~/Library/LaunchAgents, /Library/LaunchDaemons | Instructions to start background jobs | KB, but active |
| Preferences | ~/Library/Preferences/<bundle ID>.plist | App settings | A few KB |
| Saved state | ~/Library/Saved Application State/<bundle ID>.savedState | Window positions for reopening | KB |
| Installer receipts | /private/var/db/receipts | Lists of files a .pkg installer placed | KB |
Why dragging an app to the Trash isn’t a full uninstall
macOS keeps no install registry. An app writes data wherever it needs to, and nothing keeps track of it, so the Trash has no list of what to remove along with the app.
Apple admits as much. Its support page calls an app’s own uninstaller ‘the best way’ to delete the app together with its login items, extensions, and data stored in other locations. Most apps don’t come with an uninstaller, though, and that leaves the job to you.
How remaining files hurt your Mac
Both my old Mac and my current one have had between 50 and 100 apps installed. And after a few rounds of trying and ditching software, the forgotten files add up. Not all of them matter, but four kinds are worth clearing:
- Big data folders. AI models, virtual machines, Docker images, Xcode data, and browser profiles often take several gigabytes each. On a base 256 GB MacBook Air, that’s a real chunk of the drive, and it usually shows up as a mysterious System Data number.
- Active items. A leftover launch agent tries to start at every login, and a leftover helper can keep running. This is the one case where leftovers cost you performance, not just storage.
- Privacy data. Sign‑in tokens, cookies, and local message databases stay after you stop using a service. If you’ve closed your account or just want it gone, this is what to clear.
- Reinstall conflicts. Reinstall an app, and it picks up its old settings, bugs included. A clean reinstall means clearing preferences and support files first.
How big leftovers get
Here’s how much data a few popular apps leave behind after you drag them to the Trash:
| Category | App or tool | Where the data sits | Size |
|---|---|---|---|
| AI apps and models | Claude (desktop) | ~/Library/Application Support/Claude (11.5 GB in vm_bundles) | 13.4 GB |
| Ollama: gpt‑oss 20B / 120B | ~/.ollama/models | 14 GB / 65 GB per model | |
| Ollama: Llama 3.1 8B / Gemma 3 4B | ~/.ollama/models | 4.9 GB / 3.3 GB | |
| Python and AI dev tooling (uv) | ~/.cache/uv | 3.6 GB | |
| Developer tools | Xcode | ~/Library/Developer (DerivedData, simulators) | Up to ~90 GB reported |
| Docker Desktop | ~/Library/Containers/com.docker.docker/…/Docker.raw | Grows with every image pulled | |
| Everyday apps | Google Chrome | Application Support/Google + Caches/Google | 2.7 GB |
| Microsoft 365 / OneDrive | Application Support/Microsoft | 1.4 GB | |
| Firefox | ~/Library/Caches/Firefox | 1.1 GB | |
| Zoom | Application Support/zoom.us + launch daemon + privileged helper | 622 MB + 2 background items | |
| Games | Battle.net launcher | Application Support/Battle.net | 541 MB |
A few things stood out to me:
- AI tools take the most space now. One local model can outweigh all other leftovers on a Mac combined. Command‑line AI tools keep their data in hidden home folders like and
~/.ollamaCopy
, so a search limited to Library misses them.~/.cacheCopy
- Browsers and chat apps leave cache, for the most part. Expect up to a few GB, all of it safe to delete.
- Size isn’t the biggest risk. Zoom’s daemon and helper stay active after the app is gone.
Before you delete anything: Some safety rules
- Sign out and cancel first. Log out of the app’s account and cancel any subscription before removing it, since deleting files doesn’t stop billing.
- Quit the app’s background processes. Open Activity Monitor and search for the app’s name, because helpers can keep running.
- Export what you want to keep. Save chat history, projects, presets, or license keys before clearing Application Support.
- Delete the app’s subfolder, not the parent folder. For example, remove , not
Application Support/Google/ChromeCopy
, if you still use Google Drive.Application Support/GoogleCopy
- Move files to the Trash first. Wait a few days before emptying it, in case something stops working.
- Check Login Items afterward. Open System Settings → General → Login Items & Extensions and turn off anything the deleted app left in Allow in the Background.
What you should never delete
A leftover cleanup may go wrong in two ways: deleting a shared folder or something that belongs to macOS. This table keeps you out of both:
| Yes Usually safe | Partial Review first | No Leave alone |
|---|---|---|
| Caches of deleted apps | Application Support folders | Anything starting with com.apple |
| .plist files of deleted apps | Group Containers shared by a suite | The Library folders themselves |
| Logs and crash reports | Shared folders like Google or Microsoft | /System and other SIP‑protected items |
| Saved Application State | Launch agents and daemons | ~/Library/Keychains |
| Web data of deleted apps | ~/.cache and ~/.config (shared ones) | ~/Library/Mobile Documents (iCloud Drive) |
Three methods to remove leftovers: Brief table
| Method | Finds forgotten apps? | Batch removal | Time per app | Skill |
|---|---|---|---|---|
| App Cleaner & Uninstaller | Yes Lists leftovers of every deleted app | Yes All apps at once | < 1 min | Beginner |
| Finder | No Needs the app’s name | No One app at a time | 15–30 min | Intermediate |
| Terminal | Partial Only with broad searches | Partial With pro scripts | 10–20 min | Advanced |
What differs across macOS versions
- All versions: App Cleaner & Uninstaller, Go to Folder, the hidden‑file shortcut (Shift‑Command‑Period), and Terminal commands work the same way.
- Monterey and earlier: Storage is under About This Mac, and login items under Users & Groups.
- Ventura and later: Storage and login items moved to System Settings → General.
- Sonoma and later: macOS asks for permission before one app reads another app’s container.
- Sequoia and later: Login items and extensions share one screen.
- Tahoe and Golden Gate: Launchpad is gone, so apps get deleted with an uninstaller, Finder, or Terminal.
Remove all leftovers at once with App Cleaner & Uninstaller
App Cleaner & Uninstaller doesn’t need you to remember the app’s name. It scans the Library folders, plus the non‑standard locations some developers use, and lists every orphaned set of files under the name of the app that created it. Here are more perks:
- No risk to apps you use. The Remains list only shows files of apps that are already gone.
- Nothing hidden. The tool shows every path and file size before removal.
- Easy to undo. Files go to the Trash first, and Removal History restores them to their original folders.
- Fast, however long the list. Clear leftovers of dozens of apps in under a minute.
- Finding forgotten apps is the part a manual search can’t do. You’ll see leftovers of apps you removed a year ago and forgot about, next to the ones you trashed yesterday.
The whole process takes a few clicks, and here’s how it goes:
- Download and launch App Cleaner & Uninstaller.
- Flip the switch above the list from Apps to Remains.
- Select the remnants you want gone, or all of them → click Remove.
- Review the files you are about to remove → confirm.
Catch leftovers when you drag an app to Trash
Old habits die hard, and dragging an app to the Trash is one of them. With App Cleaner & Uninstaller, that habit stops costing you storage. With the Detect apps moved to Trash and offer full removal setting on, a pop‑up tells you how much it left behind and asks you to finish the job as soon as an app lands in the Trash.
- Drag an app to the Trash as usual → a pop‑up appears with the size of the remaining files.
- Click Uninstall → review the list of remaining files.
- Uncheck anything you want to keep → click Remove.
Find and delete leftovers manually in Finder
The manual way costs nothing and works on every macOS version. The catch:
- You need to know the app’s name and bundle ID.
- Plan on 15 to 30 minutes per app, mostly spent opening folders and comparing names.
- A search by name alone misses a good share of the files.
- Search results mix the app’s files with lookalikes from other apps, so every match needs a second look.
Step 1: Find the app’s bundle ID and developer name.
Most leftovers carry the bundle ID in their name, like com.google.Chrome, or sit inside a developer folder, like Application Support/Google. Get both before you start searching.
App still installed: run this in Terminal, with the app’s name in quotes:
osascript -e 'id of app "AppName"'
Copy
For example:
osascript -e 'id of app "Google Chrome"'
Copy
~/Library/Preferences
Copy
.plist
Copy
Step 2: Open your user Library and check each folder.
- In Finder, press Shift‑Command‑G → type → press Return.
~/LibraryCopy
- Go through the folders below, searching by app name, developer name, and bundle ID.
| Path | What to look for | Risk |
|---|---|---|
| ~/Library/Caches | Bundle ID or app name folder | Yes Low |
| ~/Library/Preferences | <bundle ID>.plist files | Yes Low |
| ~/Library/Logs | App or developer name folder | Yes Low |
| ~/Library/Saved Application State | <bundle ID>.savedState | Yes Low |
| ~/Library/Application Scripts | Bundle ID folder | Yes Low |
| ~/Library/Internet Plug-Ins | Browser plug‑ins | Yes Low |
| ~/Library/PreferencePanes | .prefPane with the app’s name | Yes Low |
| ~/Library/HTTPStorages, WebKit, Cookies | Bundle ID folders and .binarycookies files | Yes Low (signs you out, which is the point) |
| ~/Library/Application Support | App or developer name folder | Partial Check for your own projects or libraries first |
| ~/Library/Containers | Bundle ID folder | Partial Holds everything a sandboxed app saved |
| ~/Library/Group Containers | Team ID + app or suite name | Partial May be shared with apps you still use |
| ~/Library/LaunchAgents | .plist with the developer’s name or bundle ID | Partial Confirm the owner app is gone |
Step 3: Check the system Library (/Library).
/Library
Copy
/Library/Application SupportCopy
/Library/CachesCopy
/Library/PreferencesCopy
/Library/LaunchAgentsCopy
/Library/LaunchDaemonsCopy
/Library/PrivilegedHelperToolsCopy
/Library/LogsCopy
/Library/ExtensionsCopy
/Library/Audio/Plug-InsCopy
/Library/Internet Plug-InsCopy
/Library/PreferencePanesCopy
/Library/FrameworksCopy
This list includes the common locations, not all of them. Some apps can save files in non‑standard locations.
Note:
Stuck halfway and not in the mood for more digging? Open App Cleaner & Uninstaller → Remains → select every file you haven’t cleared yet.
Step 4: Move to the Trash, restart, then empty the Trash.
- Move every match to the Trash with right‑click → Move to Trash.
- Restart your Mac. macOS caches preferences in a background process called cfprefsd, so a deleted .plist can be rewritten until you log out or restart.
- Use your Mac for a few days. If nothing broke, empty the Trash.
Method 3: Find leftovers with Terminal
If typing commands doesn’t scare you, Terminal finds leftovers faster than Finder and reaches hidden dot‑folders that Finder searches skip. The catch:
- Results come back as long lists of paths, and some belong to apps with a similar name.
- Searching protected folders requires Full Disk Access for Terminal.
- The commands below only find and show files. Delete what they find in Finder, not with a removal command: it removes files permanently, skips the Trash, with no way back.
- Run Terminal.
- Find files by name in both Library folders with the command below, replacing appname with your app’s name:
find ~/Library /Library -iname "*appname*" 2>/dev/nullCopy
The 2>/dev/null part hides 'Permission denied' messages from protected folders.
- Open a result in Finder to check it before deleting. Run this command, replacing /path/to/file with a path from the output above:
open -R "/path/to/file"Copy
- Finder opens with the file selected → move the file to the Trash in Finder → repeat for each result you want gone.
Finish: How to stop leftovers from piling up
- Uninstall properly from now on. Use the app’s built‑in uninstaller or App Cleaner & Uninstaller instead of dragging to the Trash, so leftovers never form.
- Check Remains every few months. It takes a minute and catches files from apps you removed the old way.
- Reset apps instead of reinstalling them. A reset clears the settings and cache that cause most bugs, and your app stays in place.
App Cleaner & Uninstaller covers all of it in one place: full uninstalls, the Remains list, and app resets. Your Mac stays tidy without a monthly trip through Library folders.



