You drag an app to the Trash, empty it, and feel good about reclaiming that space. But here is the uncomfortable truth: the app itself is only a fraction of the data it left behind. Preferences, caches, support files, containers, logs, and saved state can collectively occupy hundreds of megabytes — sometimes several gigabytes — and they stay on your drive indefinitely after the app is gone. After years of installing and uninstalling software, those silent leftovers add up to a substantial and completely invisible drain on your available storage.
This guide explains exactly why the drag-to-Trash method is incomplete, identifies all seven locations where app leftovers hide on macOS, walks you through the manual process for finding them, and shows how TrimyMac's App Uninstaller eliminates every trace of an app in a single operation — with full visibility into what is being removed and how much space you get back.
To fully uninstall an app on Mac, you must delete the app itself from
/Applications AND manually remove its support files from seven hidden locations inside ~/Library: Application Support, Preferences, Caches, Containers, Logs, Saved Application State, and Group Containers. Alternatively, use TrimyMac's App Uninstaller, which scans all seven locations automatically, shows the total leftover size per app, and removes everything in one click.
Why Drag-to-Trash Leaves Files Behind
On macOS, applications are bundled as self-contained .app packages — folders that look like single files in Finder. When you drag one to the Trash, you delete only that bundle. But macOS deliberately separates an app's executable code from its runtime data. This separation follows Apple's design philosophy: the app itself should be portable and shareable, while its personal data and settings live in user-specific locations.
The macOS sandbox model reinforces this further. Sandboxed apps (required for Mac App Store distribution) are confined to specific directories and cannot write data anywhere outside their designated container. This makes them safer — but it also means their data is scattered across multiple Library subdirectories, each serving a different purpose, none of which are deleted when you remove the app bundle itself.
Even non-sandboxed apps follow the same conventions by convention. Developers write preferences to ~/Library/Preferences, caches to ~/Library/Caches, and persistent data to ~/Library/Application Support because that is where macOS expects them. Deleting the app from /Applications leaves every one of those files exactly where they are.
A single heavily-used app like Slack, Zoom, or Figma can leave behind 500 MB to 2 GB in leftover files after uninstallation. On a Mac that has had dozens of apps installed and removed over several years, total orphaned data commonly reaches 5–15 GB — enough to noticeably affect performance on a drive that is getting full.
The 7 Locations Where App Leftovers Hide
macOS has a well-defined set of locations where apps are permitted to store data. When an app is uninstalled, files in these locations become orphaned — they reference an app that no longer exists. Here is exactly what lives in each location and why it matters.
Application Support
~/Library/Application Support/[AppName]This is the primary location for an app's persistent user data — everything that needs to survive between launches but is not a user-facing document. It includes databases, downloaded content, account data, plugin configurations, licensing information, and app-specific settings that do not belong in the Preferences system. For apps like Slack, Spotify, or any productivity tool, this folder can grow very large. Slack's Application Support folder, for example, routinely reaches 1–3 GB due to cached messages and workspace data that persists even after the app is removed.
Typical leftover size: 50 MB – 3 GBPreferences
~/Library/Preferences/[com.company.app].plistEvery app that respects macOS conventions stores its settings in a .plist (property list) file here, named using the app's bundle identifier in reverse-DNS format — for example, com.apple.Safari.plist or com.spotify.client.plist. These files store window positions, user-selected options, account preferences, and any customisations you made. They are small individually (typically just a few kilobytes each), but they persist indefinitely after uninstallation and can number in the hundreds on an actively used Mac. More importantly, if you reinstall the same app, macOS will pick up the old preferences file and restore your previous configuration — which can be confusing when you wanted a clean start.
Caches
~/Library/Caches/[com.company.app]App caches are temporary files that apps write to speed up future operations — rendered UI assets, network response data, thumbnail previews, compiled assets. Unlike Application Support data, caches are technically disposable: the app regenerates them on demand. But when an app is uninstalled without cleaning up after itself (which is the norm, not the exception), its cache folder stays behind and is never rebuilt or removed. Web browsers, media players, and communication apps are the biggest offenders — a browser cache alone can occupy 500 MB or more.
Typical leftover size: 10 MB – 1 GBContainers
~/Library/Containers/[com.company.app]This location is specific to sandboxed Mac App Store apps. The macOS sandbox confines each sandboxed app to its own Container directory, which holds the app's preferences, caches, application support data, and other files — all in one location, isolated from other apps. Containers can be significant in size because they consolidate data that non-sandboxed apps spread across multiple directories. When a sandboxed app is deleted without using TrimyMac or a similar uninstaller, its entire Container folder remains on disk, occupying the full amount of space the app had accumulated during its lifetime.
Typical leftover size: 100 MB – 2 GBLogs
~/Library/Logs/[AppName]Applications write diagnostic and activity logs to this directory. These logs record events, errors, network activity, and debug information — invaluable during development or troubleshooting, but entirely useless once the app is gone. Logs are typically small per entry, but verbose apps running over a long period can accumulate substantial log files. Communication apps, browsers, and developer tools are particularly prolific loggers. Because log files are plain text and compress well, their actual disk footprint is often modest, but they can still add up to tens of megabytes per uninstalled app over time.
Typical leftover size: 1 MB – 100 MBSaved Application State
~/Library/Saved Application State/[com.company.app].savedStatemacOS's Resume feature allows apps to reopen exactly where you left them — with all windows, scroll positions, and unsaved content preserved across relaunches and even system restarts. Each app stores this state in a dedicated .savedState bundle here. For apps with complex multi-window interfaces or large document previews embedded in the saved state, these folders can be surprisingly large. They are among the most commonly overlooked leftover locations because the Saved Application State directory itself is not widely known, even among experienced Mac users.
Group Containers
~/Library/Group Containers/[group.com.company.shared]Group Containers are shared data locations used by app families — a suite of apps from the same developer that need to share data with each other. Apple's own apps use this extensively: iCloud Drive, Notes, Reminders, and other system apps share data through Group Containers. Third-party developer tools, productivity suites, and creative apps with companion utilities also use them. Because Group Containers are shared across multiple apps, they are the trickiest to clean safely — you cannot simply delete a Group Container if another app in the same family is still installed. TrimyMac's uninstaller accounts for this by checking all apps sharing a Group Container before flagging it for removal.
Typical leftover size: 10 MB – 500 MBUse the Developer's Uninstaller First
Apple recommends using an app's own Uninstall, Uninstaller, Remove, or Reset feature when one is provided. That is the safest first choice for apps that install login items, system extensions, drivers, or privileged helpers because the developer knows which components belong to the app. Deleting an app also does not cancel a subscription or remove documents you created with it. See Apple's current uninstall guidance.
How to Find App Leftovers Manually
If you prefer to clean up manually, macOS provides two paths to the hidden Library folder where most leftovers reside. Neither is particularly discoverable — Apple hides ~/Library from casual users by default — but both are straightforward once you know them.
-
1
Open the User Library folder in Finder
Open Finder, click the Go menu in the menu bar, then hold the Option key. A hidden Library menu item will appear. Click it. This opens
~/Librarydirectly in a new Finder window. From here you can navigate to Application Support, Preferences, Caches, Containers, Logs, and Saved Application State individually. -
2
Use Go to Folder to navigate directly
Press Cmd + Shift + G in Finder (or choose Go → Go to Folder) and type the exact path of the directory you want to inspect — for example,
~/Library/Application Support/Slack. This is faster when you already know the app name and want to jump straight to its folder. -
3
Search with Spotlight
Press Cmd + Space to open Spotlight and search for the app's name or bundle identifier (e.g.,
com.tinyspeck.slackmacgap). Spotlight will surface related files across the filesystem, including Library subdirectories. However, Spotlight does not always index every Library subdirectory, so this method can miss items that Finder navigation would find. -
4
Check all seven locations for each app name
For a thorough manual cleanup, visit each of the seven locations listed above and look for folders or files matching the app's name or bundle identifier. Preferences files use the bundle ID format (
com.company.app.plist), while Application Support and Logs folders typically use the app's plain name. Group Containers use agroup.prefix followed by the bundle ID. This process takes 10–15 minutes per app and requires knowing both the app's display name and its bundle identifier. -
5
Delete the identified files and folders
Once you have located the leftover folders and files, select them and press Cmd + Delete to move them to the Trash, then empty the Trash. Be cautious: do not delete Preferences or Container files for apps that are still installed, as this can cause data loss or unexpected app behaviour. Always verify the app is fully removed from
/Applicationsbefore cleaning its support files.
TrimyMac App Uninstaller: All 7 Locations, One Scan
TrimyMac's App Uninstaller was built specifically to solve the problem of incomplete uninstallation on macOS. Rather than requiring you to manually navigate seven different Library subdirectories for every app you want to remove, it scans all seven locations automatically, matches files to their parent app, and presents the complete picture — including the total leftover size — before you confirm anything.
How the scan works
When you open the App Uninstaller in TrimyMac, it indexes every app installed on your Mac and simultaneously scans all seven leftover locations. For each app, it builds a complete file manifest by cross-referencing the app's bundle identifier, display name, and developer identifier against files found in Application Support, Preferences, Caches, Containers, Logs, Saved Application State, and Group Containers. The result is a list of every installed app with two key pieces of information: the size of the app bundle itself, and the total size of all associated leftover files.
For apps you have already deleted from /Applications, TrimyMac flags them as orphaned — the app is gone but its data remains. These are sorted to the top of the list because they are the clearest candidates for cleanup. You will often be surprised by how many orphaned apps are accumulating data on your drive, especially if you have been using your Mac for several years.
Remove app + all leftovers in one click
For each app, TrimyMac gives you two removal options. The first option — Remove App Only — deletes just the .app bundle from your Applications folder, equivalent to dragging it to the Trash yourself. This is useful when you want to remove the app but intentionally keep its data (for example, if you plan to reinstall the same app on another Mac and want to preserve preferences).
The second option — Remove App + All Leftovers — is the complete uninstall. TrimyMac removes the app bundle and every associated file across all seven locations in a single operation. Before deletion, it displays a detailed file list showing exactly what will be removed and the total reclaimed space, so you can review and deselect anything you want to keep. This gives you the thoroughness of a manual cleanup with none of the manual effort — a process that would take 15 minutes per app in Finder takes about 10 seconds in TrimyMac.
| Method | App bundle removed | All 7 leftover locations cleaned | Shows size before removal | Time required |
|---|---|---|---|---|
| Drag to Trash | Yes | No | No | 5 seconds |
| Manual Library cleanup | Yes | Yes (if thorough) | No | 10–20 min per app |
| TrimyMac — Remove App Only | Yes | No | Yes | < 10 seconds |
| TrimyMac — Remove App + All Leftovers | Yes | Yes (all 7) | Yes | < 10 seconds |
Stop leaving invisible files behind
TrimyMac's App Uninstaller scans all 7 leftover locations, shows you exactly what each app left behind, and removes everything in one click. Free to download for macOS.
Download TrimyMac Free macOS 13 Ventura or later · Apple Silicon & Intel · No subscriptionHow to Remove All App Data on Mac: A Complete Walkthrough
Whether you use TrimyMac or prefer the manual route, here is a complete end-to-end walkthrough for fully uninstalling an app on Mac and confirming that no data has been left behind.
-
1
Quit the app completely
Before uninstalling, make sure the app is not running. Click the app in the Dock and select Quit, or press Cmd + Q while the app is active. For apps that run in the background (like menu bar utilities), right-click the menu bar icon and choose Quit. Attempting to delete an app's files while it is running can cause errors or leave partial files behind.
-
2
Note the app's bundle identifier
Right-click the app in Finder and choose Show Package Contents, then open
Contents/Info.plistin a text editor. Look for theCFBundleIdentifierkey — its value (e.g.,com.spotify.client) is the bundle ID you will use to find Preferences files and Container folders. If the app is already deleted, search online for "[App Name] bundle identifier" — this is publicly documented for most apps. -
3
Delete the app from /Applications
Drag the app from your Applications folder to the Trash, or right-click and choose Move to Trash. For Mac App Store apps, you can also delete them from Launchpad by holding Option until icons jiggle, then clicking the X button. Do not empty the Trash yet — wait until you have reviewed and removed the leftover files.
-
4
Navigate to each of the 7 leftover locations
Open Finder, hold Option, click Go → Library, then visit each directory:
Application Support/[AppName],Preferences/[com.company.app].plist,Caches/[com.company.app],Containers/[com.company.app],Logs/[AppName],Saved Application State/[com.company.app].savedState, andGroup Containers/(search for the developer's identifier prefix). Move any matching items to the Trash. -
5
Empty the Trash and verify
Once you have moved the app and all leftover files to the Trash, choose Finder → Empty Trash (or right-click the Trash icon and choose Empty Trash). To verify the cleanup is complete, open Spotlight and search for the app name — if no Library files appear in results, the uninstallation is thorough. You can also run a Finder search across
~/Libraryfor the app's bundle identifier to confirm nothing remains.
Frequently Asked Questions
Common questions about uninstalling apps completely on Mac, finding leftover files, and using TrimyMac's App Uninstaller.
How to uninstall apps on Mac completely?
To completely uninstall an app on Mac, you need to do two things: first, delete the app bundle from your /Applications folder (drag to Trash or delete via Launchpad); second, manually remove leftover files from seven locations in your Library folder: ~/Library/Application Support, ~/Library/Preferences, ~/Library/Caches, ~/Library/Containers, ~/Library/Logs, ~/Library/Saved Application State, and ~/Library/Group Containers. The fastest and most reliable way is to use TrimyMac's App Uninstaller, which finds all leftover files automatically and removes them alongside the app in one click.
Does deleting an app on Mac delete all its files?
No — deleting an app on Mac by dragging it to the Trash removes only the app bundle itself (.app file). It does not remove any of the app's associated data files, which are stored separately in your user Library folder across up to seven different locations. This is by design: macOS separates the application code from user data so that uninstalling an app does not automatically destroy anything the user created or configured. The downside is that uninstalling an app cleanly requires deliberate extra steps beyond just emptying the Trash.
Where are app leftover files stored on Mac?
App leftover files are stored in your hidden user Library folder (~/Library), which you can access by holding Option and clicking Go → Library in Finder. The specific subdirectories to check are: Application Support (persistent app data), Preferences (settings .plist files), Caches (temporary cached data), Containers (sandboxed app data), Logs (diagnostic log files), Saved Application State (window and session state), and Group Containers (shared data between apps from the same developer). Each location uses either the app's display name or its bundle identifier (in com.company.app format) to name its folder.
Is it safe to delete app support files after uninstalling an app?
Yes — it is completely safe to delete Application Support, Preferences, Caches, Containers, Logs, and Saved Application State files for an app that has already been uninstalled. Once the app is gone, these files serve no purpose and cannot be used by any other app. The only exception to be careful about is Group Containers: if the Group Container is shared with another app from the same developer that you still have installed, deleting the Group Container could affect that other app. TrimyMac's App Uninstaller checks for this automatically and only flags Group Containers for deletion when no other installed app shares them.
How do I find the bundle identifier of an app on Mac?
The easiest ways to find an app's bundle identifier are: (1) Right-click the app in Finder, choose Show Package Contents, open Contents/Info.plist in TextEdit, and look for the CFBundleIdentifier key. (2) Run this command in Terminal: defaults read /Applications/AppName.app/Contents/Info CFBundleIdentifier. (3) Search online for "[App Name] mac bundle identifier" — most well-known apps have this documented in developer resources. The bundle identifier follows the format com.company.appname and is what macOS uses to name Preferences files and Container folders.
What is the difference between "Remove App Only" and "Remove App + All Leftovers" in TrimyMac?
Remove App Only deletes just the application bundle from your Applications folder — equivalent to dragging the app to Trash manually. Use this when you want to keep the app's data on disk, for example if you plan to reinstall the app and want to preserve your settings and preferences. Remove App + All Leftovers performs a complete uninstall: it removes the app bundle and scans all seven leftover locations (Application Support, Preferences, Caches, Containers, Logs, Saved Application State, and Group Containers), displaying a full file list with sizes before anything is deleted. This is the option to choose when you want to permanently remove an app and reclaim all the disk space it occupied.
Can TrimyMac find leftover files from apps I deleted months or years ago?
Yes — TrimyMac scans the seven leftover locations for all orphaned data, regardless of when the app was originally deleted. Files in ~/Library/Application Support, ~/Library/Caches, and other locations persist indefinitely after the app is removed; macOS never cleans them up automatically. TrimyMac identifies orphaned files by checking whether the app that created them is still installed on your system. If the parent app is missing, TrimyMac flags the files as orphaned and includes them in the cleanup list. On Macs that have been in use for several years, these historical leftovers can collectively add up to 5–20 GB of recoverable space.