Free Interactive Mac Tool

Mac App Leftovers Path Finder

Dragging an app to the Trash leaves gigabytes of hidden support files, caches, and preferences behind. Search any popular Mac app to reveal its exact leftover paths, copy folder locations, or clean them safely.

App not listed?

Generate standard macOS Library paths for any custom or unlisted application.

Google Chrome

Web Browser
Google LLC com.google.Chrome
Estimated Leftovers 1.5 GB to 15 GB

When you delete Chrome, macOS preserves all browser cache, download history, extension databases, and profile logins in hidden Library folders.

Discovered Path Locations: 6 Folders
DiskCompanion App Icon
Tired of hunting through 10+ hidden folders?

Completely Uninstall Any Mac App in One Safe Click

Manually deleting folders inside ~/Library is tedious and risky. One mistaken deletion can reset your other apps. DiskCompanion's native uninstaller automatically traces every container, cache, preference, and background launch helper, moving everything safely to the Mac Trash with 100% reversible Put Back support.

Apple Notarized Zero Background Daemons 14-Day Money-Back Guarantee

Why Dragging Apps to the Trash Leaves Hidden Files Behind

On macOS, applications distributed outside the Mac App Store are self-contained bundles ending in .app. When you install an application, you simply drag that bundle into your /Applications folder.

However, as soon as you launch the application for the first time, macOS creates dedicated support directories inside your personal user Library folder (~/Library). These directories hold downloaded caches, local databases, user authentication tokens, preference plists, and crash logs.

When you eventually drag the .app bundle to the Trash, macOS removes only the executable binary in /Applications. It leaves all files in ~/Library untouched. Apple designed macOS this way so that if you reinstall the app in the future, your preferences and settings will still be intact. But if you never plan to use the app again, those orphaned files remain permanently on your drive, silently consuming gigabytes of SSD capacity.

The 7 Hidden Folders Where Mac Apps Scatter Files

Third-party Mac software scatters files across seven primary locations inside your personal user Library:

Folder Location Typical Size What Is Stored Here
~/Library/Application Support/ 100 MB to 30 GB Large local databases, user profile data, extensions, offline assets, and application engines.
~/Library/Caches/ 500 MB to 20 GB Temporary web assets, rendered video previews, font caches, and image thumbnails.
~/Library/Containers/ 200 MB to 15 GB Sandboxed application environments for Mac App Store apps and modernized third-party software.
~/Library/Group Containers/ 500 MB to 25 GB Shared data pools between related apps (such as Microsoft Office apps or Adobe Creative Cloud).
~/Library/Preferences/ 10 KB to 5 MB Property list (.plist) files containing user configuration, window sizes, and license keys.
~/Library/Saved Application State/ 1 MB to 200 MB Snapshots of open windows and document states so the app can restore your session upon reopening.
~/Library/LaunchAgents/ 5 KB to 50 KB Startup instruction plists that instruct macOS to launch background monitors upon login.

How to Safely Reveal the Hidden ~/Library Folder in Finder

Because deleting critical system files could disrupt your user account, Apple hides the user Library folder by default. Here are the two safest ways to reveal it:

  • The Option Key Shortcut: In Finder, click the Go menu in the top menu bar, then press and hold the Option (ƒ) key. The hidden Library entry will appear between "Home" and "Computer". Click it to open.
  • The "Go to Folder" Shortcut: In Finder, press Command + Shift + G. In the input dialog, type ~/Library and press Return.

Note on the Tilde Symbol (~): Always include the tilde (~). The path ~/Library points to your personal user account data, whereas /Library (without the tilde) points to the global system-level library shared across all computer accounts.

Manual Deletion vs Automated Uninstallation

While searching for leftover folders manually is completely free, it comes with important trade-offs:

  • Shared Framework Risks: Apps from the same developer (such as Adobe, Microsoft, or Google) often share files in ~/Library/Application Support. Deleting a shared folder can inadvertently reset other apps that you still use.
  • Obscure Bundle Identifiers: Many applications do not use their obvious consumer brand name for container folders. For example, Telegram stores its primary sandboxed database under ru.keepcoder.Telegram, and WhatsApp stores data under net.whatsapp.WhatsApp.
  • The DiskCompanion Solution: Rather than forcing you to memorize reverse-domain bundle identifiers and manually verify dozens of folders, DiskCompanion maps all associated files automatically. When you choose to uninstall an app, DiskCompanion gathers every leftover and moves it to the macOS Trash, ensuring 100% reversible Put Back protection.

Frequently Asked Questions

Why does dragging an app to the Trash leave files behind on Mac?

When you drag an application bundle from the Applications folder to the Trash, macOS only deletes the executable program itself. By design, macOS does not delete the user settings, caches, login tokens, and container files stored inside your hidden Library folder (~/Library). Over months and years, these leftover files accumulate into tens of gigabytes of wasted storage.

How do I safely open the hidden Library folder in macOS Finder?

Open Finder, click the 'Go' menu in the top menu bar, and hold down the Option key on your keyboard. The hidden 'Library' folder will appear in the dropdown list. Alternatively, press Command + Shift + G in Finder and type ~/Library to jump directly to your personal Library folder.

Can deleting app leftovers break other applications or macOS?

Deleting leftover files for an app you have already uninstalled is safe. Modern macOS locks core system files inside a cryptographically sealed, read-only system volume (the Signed System Volume) that third-party apps cannot modify. However, manually digging through ~/Library carries the risk of accidentally deleting a folder belonging to an app you still use. Always verify the folder name before deleting, or use a tool that routes deletions through the Mac Trash so you can restore them.

What is the difference between ~/Library and /Library on Mac?

The tilde symbol (~) represents your personal user home directory. The ~/Library folder contains preferences, caches, and application data unique to your personal user account. The /Library folder at the root of your hard drive contains system-wide resources shared across all user accounts on the Mac, such as shared audio plug-ins, printer drivers, and privileged helper tools.

What happens if I delete an app's Preferences (.plist) file?

A .plist (property list) file stores user settings such as window positions, keyboard shortcuts, and license keys. If you delete a .plist file for an app that is still installed, the app will reset to its factory default settings the next time you launch it. If you have uninstalled the app, the .plist is pure leftover clutter.

How does DiskCompanion automate app leftover removal?

DiskCompanion includes an automated application uninstaller that traces all associated containers, caches, preference plists, and background launch agents across your system. Instead of permanently deleting files, DiskCompanion moves everything safely to the native macOS Trash, giving you 100% reversible 'Put Back' recovery.