In this article
Removing the app does not make its remaining data disposable; keep the parent folder. That decision matters when you find a large folder named after software you no longer use. It may be unwanted residue, but it may also contain the settings or local records you expected to recover later. The useful question is what you intend to retain.
Use the app’s removal method first
If you still use the app and only want space back, look for its download manager, storage settings or documented cache-clearing function. Removing selected downloads is a different operation from resetting the entire application.
If you are uninstalling it, check the maker’s current instructions. Apple’s uninstall guide recommends an included uninstaller when available; some apps instead offer removal or reset through a setting. This gives the software’s author a chance to handle components stored outside its main application bundle.
Before starting, decide whether you want a temporary uninstall, a settings reset or removal of both software and data. Those outcomes can require different steps. Export records you want to keep and check that the export opens in a suitable application. A folder’s age or size cannot answer that retention question.
Open one folder and identify its scope
In Finder, choose Go → Go to Folder, enter ~/Library/Application Support, and press Return. The tilde means your home folder. Inspect the particular app or vendor subfolder; do not select the parent as a cleanup target.
The similarly named /Library/Application Support is a different location outside your home folder. A matching name in those two places does not establish that both copies are redundant. Record the full path, not just the last folder name.
Apple’s Library directory reference, an archived developer guide, distinguishes application support data from regenerable caches. Application Support can contain user data. That distinction remains a useful starting point, but the current app’s documentation should determine the meaning of its particular files.
If you prefer a visual walkthrough, Gary Rosenzweig’s MacMost tutorial demonstrates reaching the hidden user Library in Finder. It was published on May 23, 2025 and checked for this article on September 25, 2026. Use it for navigation; apply the retention checks below before removing anything.
A concrete example: VS Code removal versus data removal
Microsoft’s current VS Code uninstall instructions separate the macOS application-removal step from an optional clean uninstall. The latter explicitly removes user data and can reset settings. Its listed locations include $HOME/Library/Application Support/Code, alongside ~/.vscode-shared and ~/.vscode.
That is an example of a documented decision, not a recipe to apply to another app. Wanting the editor gone does not automatically mean wanting its configuration gone.
Microsoft’s settings documentation puts ordinary macOS user settings at $HOME/Library/Application Support/Code/User/settings.json. It also distinguishes workspace settings stored with a project, commonly in that project’s .vscode/settings.json.
| Item in this example | Question to answer before removal |
|---|---|
| The Visual Studio Code application | Do I want to remove the editor? |
| Its documented user-data locations | Do I also want to reset or discard my configuration? |
| A project’s own settings folder | Does this belong with a project I am keeping? |
The home-level .vscode directory and a project’s .vscode directory have similar names but different paths and roles. Copying an incomplete path into a cleanup checklist loses that distinction. Check the vendor’s current instructions for your installation rather than treating a familiar folder name as sufficient proof.
Use a retention worksheet for each candidate
We built this worksheet by separating the ownership and retention questions in the Apple and Microsoft guidance. It is a practical review aid, not the result of an uninstall experiment or a guarantee that deletion is harmless.
| Check | Evidence and next action |
|---|---|
| Who uses this exact path? | Find vendor instructions naming it. If the owner is unclear, keep it and investigate. |
| What do I want to retain? | Identify settings, records, downloads and project data. Inspect them through the app when possible. |
| Can I recover what matters? | Check an export or backup and how to open it. Otherwise preserve the original. |
| Does another app depend on it? | Check suite and shared-component guidance. Leave an uncertain shared location alone. |
Apply the worksheet to the VS Code example: Microsoft supplies owner evidence for the user-data paths and explicitly describes a reset consequence. You still have to decide whether you want that reset and whether the configuration is preserved elsewhere. The vendor cannot make that personal retention choice for you.
For an unfamiliar database, do not infer its importance from the extension alone. Reopening the owning app to inspect or export records can be more useful than searching random filenames. If the application is unavailable, preserve the data while you establish a supported way to read it.
Keep evidence separate from permission to delete
A file association helps explain a path; it does not authorize its removal. For software installed through a package, inspect the Installer receipt when you need another ownership clue. Runtime-created data may be absent from that receipt.
A background component needs its own investigation. The presence of an app-data folder does not show whether a helper is active; login and background settings answer different questions.
VaultDog’s installed-app passport can bring candidate related files together, including matching user Application Support locations. The first-scan workflow explains how to review those paths while the app is still installed. Matches are leads for inspection, not an exhaustive orphan-file inventory or a promise that every listed item is safe to remove.
Once you have identified a specific folder, decided its data is unwanted, checked dependencies and followed the maker’s removal guidance, keep the recovery step deliberate. Moving something to Trash and permanently emptying Trash are separate actions. Merely waiting a few days does not prove that you will never need the records again.
