Moving an app to the Trash removes the app, not the data it created. On a Mac that has been in use for years, those leftovers add up.
By MacMonitor · Published · Updated · macOS 26; app requires macOS 14 or later
Short answer: quit the app, move it from Applications to the Trash, then inspect its leftover files in ~/Library: Application Support, Caches, Preferences, Containers, Saved Application State and Logs. Use the app's own uninstaller first if it has one, because some apps install background helpers.
In Finder choose Go → Go to Folder (⇧⌘G) and check these folders for items named after the app or its developer:
| Folder | What is there |
|---|---|
~/Library/Application Support | Databases, downloads and settings |
~/Library/Caches | Regenerable caches |
~/Library/Preferences | Settings files ending in .plist |
~/Library/Containers, ~/Library/Group Containers | Data for sandboxed and App Store apps |
~/Library/Saved Application State | Window positions |
~/Library/LaunchAgents | Helpers that start at login |
Many items are named after the app's bundle identifier, such as com.tinyspeck.slackmacgap for Slack.
Uninstalling an application and resetting it for a fresh start are different jobs. If you intend to reinstall, preserve the documents, presets and account information you will need. If you are leaving the app permanently, export important data into a format you can open elsewhere before removing its support files.
A good uninstall starts inside the application. Look for an export, backup or account-management option, and note where it saves the result. For a drawing app, that might include custom brushes as well as finished images. For a database or note-taking app, the visible documents may depend on an internal library that a broad leftover cleanup would remove.
An uninstaller can suggest that a folder belongs to an app by its name or bundle identifier. That is useful evidence, but shared components make ownership more complicated. A developer may use one support folder for several applications, and a Group Container can hold data shared across related apps or extensions.
Before selecting a support item, check whether another installed product uses the same developer name. Prefer a documented vendor uninstaller for software that installs drivers, network components or background services. Removing an application bundle may leave those components behind, while manually deleting their files can produce a partial or broken installation.
Do not interpret a large support folder as proof of waste. It may contain offline projects, templates, downloads, local databases or message history. A complete removal is a deliberate decision to remove the app and selected associated data, not a requirement to erase every directory with a similar name.
Suppose you want to uninstall an editor you used for a course. Your exported assignments are in Documents, while custom templates and an unfinished project remain in the editor’s own support folder. This is a hypothetical example. Dragging the app to Trash might leave those files; deleting all support files might remove the only editable project.
The sensible order is to open the unfinished project, export or back it up, verify the export, and then remove the application. Review templates separately. A future reinstall might need them even if they are small. You do not need to keep every cache, but you do need to understand which files represent your work.
Some applications keep a menu bar helper, sync service or extension running after their main window closes. Use the app’s Quit command and check its own settings for background behavior. If an uninstaller says the app is still in use, address that state rather than forcing the removal through an unrelated deletion tool.
For a system extension, VPN, antivirus or audio driver, use the developer’s current removal instructions. These tools can have components outside the main application bundle, and their removal may require a restart or a supported system approval. A generic file list cannot replace those instructions.
Deleting an app does not necessarily cancel its subscription, deactivate a device or delete a cloud account. If you pay for the software, check the seller’s account or the App Store subscription controls separately. If the license has a device limit, use the supported deactivation process before removing the app when appropriate.
Similarly, local removal does not establish what happens to cloud data. A synced folder may remain available online, or a deletion inside it may propagate. Confirm the service’s behavior and export important content before deciding to remove an account or shared workspace. Those are larger decisions than uninstalling a local application.
A partial failure should be described as partial. If an app bundle moved but a selected leftover could not be removed, keep the reported path and resolve its ownership or permission separately. Do not keep escalating access just to make a removal list reach zero.
It can leave data, but the exact result depends on the application. Some apps keep their documents separately by design. That is a useful distinction when deciding whether to retain data for a reinstall or remove it permanently.
Do not remove one merely because it appears in a search. Establish which software installed it and follow that software’s current instructions. A similar developer name is a clue, not proof that the component is unused.
Keep a verified export or backup of your work and note the account or license you used. Reinstalling the application can restore its program files; it does not guarantee recovery of support data you permanently erased.
A small review is easier to verify. Start with applications you recognize, preserve their data, and check the result before moving to another. If your main concern is one large app, solve that case before attempting a system-wide purge.
The document may be intact but depend on a format that another installed application cannot read. Reinstall the appropriate app or use a verified export you made before removal. This is why checking document portability belongs at the beginning of an uninstall, even when the app itself is easy to download again. Do not delete the document as an apparent leftover merely because its usual icon or default opening application has changed.
Idle Apps lists your apps with their size and when you last used them, flags apps unused for 90 days, and finds each app's leftover files automatically. Only clearly regenerable leftovers such as caches and logs are pre-selected. If the app is still open, MacMonitor asks it to quit first and refuses to continue while it runs. The app and its leftovers go to the Trash.