To find out whether storage is going to caches or project files, first check macOS Storage for an overview, then inspect the folders behind the largest items. A “System Data” total can include caches, but it is not a cache inventory. Project files are best identified by their location and contents in Finder; cache status is suggested by a cache folder’s path and app ownership, not by a filename alone.

Start with the macOS Storage view

Open Apple menu > System Settings > General > Storage. Review the storage bar and categories, then open Documents and choose File Browser to see folders and the space they use. Apple says Documents includes files in your home folder that do not belong to another category, while the File Browser shows the contents and storage used by folders. This is a useful first pass for finding large project directories, downloads, and media files. Apple’s Mac storage guide

Do not treat the System Data figure as a direct answer. Apple describes it as a changing category that can include logs, caches, virtual-memory files, temporary files, app support files, plug-ins, and other runtime resources. Storage settings do not let you select and delete the contents of System Data. A large number can prompt further investigation, but it cannot tell you which part is a cache or which app created it. Apple’s Mac storage guide

Inspect likely project files in Finder

Use Storage > Documents > File Browser to locate folders with high usage. Look for recognizable project names and expected working locations, such as folders under Documents, Desktop, or a location you chose when saving. Open a candidate folder and check its contents before removing anything: a project can include source files, assets, exports, databases, and generated intermediate files, and a large file may be essential even when its extension is unfamiliar.

Finder can also help verify an item’s location: select it and use File > Get Info to see its details. Compare the containing folder and filename with the project you recognize. If a project lives in another user’s home folder, external disk, or a cloud-synced location, the Storage File Browser may not make its ownership or sync state obvious; navigate to that location in Finder and confirm before acting. Avoid deleting a project based only on its size or last-accessed date.

Check whether a large folder is plausibly a cache

A standard user cache location is ~/Library/Caches. To open it in Finder, choose Go > Go to Folder, enter ~/Library/Caches, and press Return. The tilde refers to your home folder. Inspect the folder names for an app or vendor you recognize, then compare the apparent size with the app’s own storage or cache controls, if it provides them. Apple’s developer documentation describes Caches as holding data an app can recreate and says user-specific cache folders conventionally sit under ~/Library/Caches in app-named subfolders. Apple’s macOS Library directory documentation

This path is a clue, not proof that every item is safe to discard. Apps can store durable or user-created information elsewhere, and sandboxed apps may keep their data inside app containers rather than in the plain user cache directory. Apple distinguishes caches from Application Support, which can contain app-managed data and user data. If the folder is under ~/Library/Application Support, do not assume it is disposable cache simply because the app created it. Apple’s macOS Library directory documentation

Use a cautious decision sequence

For each large item, write down its full location, size, and the app or project it appears to belong to. Then classify it by evidence: a known project folder and recognizable working files point toward project storage; an app-named folder in ~/Library/Caches points toward cache storage; an unclear location or unfamiliar contents remain unclassified. This simple inventory keeps “large” from being mistaken for “safe to delete.”

If you decide to remove cache data, quit the associated app first and use that app’s built-in cache-clearing option when available. Otherwise, move only the clearly identified app cache to Trash, then reopen the app and check that it behaves as expected before emptying Trash. Some cached content may need to be downloaded or regenerated. If you are unsure what an item does, leave it in place and consult the app developer; Apple’s Storage panel does not expose System Data contents for deletion. Apple’s Mac storage guide

What this method can and cannot establish

This process can identify large folders and build a reasonable, location-based distinction between likely caches and project files. It cannot guarantee that a folder is disposable: only the app or project owner can confirm the role of ambiguous data. Nor does one Storage reading prove that caches caused all of the reported System Data usage. Recheck Storage after any cleanup and allow macOS time to update its estimate; judge the result by available space and the files you actually identified, not by the category label alone.

Sources