How to clear app caches on a Mac
Tech site Engadget explains how to manually delete application caches on macOS to free up storage or fix glitches. It cautions against doing so routinely or without a reason.

Apple Mac applications store temporary files, known as caches, so they can run faster and avoid re-downloading the same data. Tech outlet Engadget has published a guide to clearing these caches on macOS when they take up too much space or cause problems.
Caches hold items such as image previews and downloaded content. Google Chrome, for example, saves parts of webpages, including images, as you browse so the same site loads faster next time. If left unchecked, a cache can keep occupying storage even when the app no longer needs those files. A Mac may manage them on its own, but there is no guarantee when. Problematic caches can also cause glitches, such as showing outdated or inaccurate content.
How to do it
Some apps, including Safari and Apple Music, let you clear their cache from their settings. For others, you must find and delete the cache by hand. It is usually stored in ~/library/caches. The Library folder is hidden, so Finder may not show it right away. To reveal it, open Finder, press command + shift + H, then command + J and check "Show Library Folder." To see folder sizes, press command + J again inside the Library and check "Calculate all sizes."
In the caches folder, find the folder of the app in question and delete everything inside it. Apple's own apps use the "com.apple" prefix in their bundle identifier, while third-party apps do not. If a cache is not in the caches folder, it may be in ~/library/containers, which holds apps that run in a sandbox.
What to expect afterwards
Clearing caches does not improve app performance unless the Mac is already short on storage, but it can free up space and sometimes fix glitches. Afterwards, an app may launch more slowly and feel sluggish because it has to rebuild its cache. Once that finishes, it should run smoothly again.
Engadget advises against clearing caches indiscriminately or making it part of a maintenance routine. It recommends doing so only if an app misbehaves or takes up too much storage.


