The short version
- Caches store results your Mac would otherwise recompute, so they make it faster, not slower.
- Clearing a cache forces a rebuild, which is a temporary slowdown, not a speed-up.
- macOS already purges the caches that are safe to purge, automatically, when space is needed.
- Two real reasons to clear a specific cache: to fix a specific glitch, or to reclaim space from one that has grown very large.
What a cache actually is
A cache is a saved result. Rather than redo expensive work every time, your Mac does it once and keeps the answer somewhere fast to reach. QuickLook keeps the thumbnails it generated for your files. The system keeps rendered font data. Browsers keep images and scripts so a page you revisit loads instantly. A web app keeps decoded audio so scrubbing a timeline is smooth. In every case the cache trades a little disk space for a lot of speed.
Howard Oakley, who documents how macOS works internally, describes caches as being "used throughout macOS to improve performance" and to "provide fast-access local storage." That is the whole purpose. A cache is not junk that accumulated by accident; it is a deliberate speed optimisation.
Why clearing it usually slows things down
Follow the logic through. If a cache is a stored answer, deleting it does not make the question go away. The next time your Mac needs that answer, it has to compute it from scratch again, and only then can it re-cache it. So the immediate effect of clearing a cache is the opposite of what people expect: the first time you use each affected feature, it is slower, until the cache fills back up.
Oakley's example is vivid. Deleting the QuickLook caches would make "the Finder much slower, as every document would need its QuickLook preview rebuilt." You would not experience a faster Mac; you would experience a Finder that stutters on every folder until it has regenerated all those thumbnails.
The myth
Clearing caches removes clutter that is slowing your Mac down, so doing it regularly keeps it fast.
The reality
Caches are the speed-up. Clearing them forces a rebuild, so the near-term effect is slower, and there is no lasting performance gain to show for it.
macOS already does the housekeeping
The second reason routine cache-clearing is pointless is that the system does it for you, correctly. macOS has a mechanism for deleting caches when space is actually needed, and the space those caches occupy is counted as "purgeable," meaning it can be reclaimed on demand. Apple states the system "clears caches and logs that are safe to delete" when space is needed, listing temporary database files, interrupted downloads, staged updates and Safari website data among them.
The key word is "safe." macOS knows which caches can go without breaking anything and which cannot. A manual sweep, or an aggressive cleaner, does not always make that distinction, which is how cache-clearing occasionally breaks a working feature.
Because purgeable cache space counts as "free" in the Finder, deleting a cache by hand can move the real free-space number (in df or Disk Utility) while the Finder barely changes, since the Finder had already counted that room as available. It can feel like nothing happened. See Where did my Mac storage go? for why the numbers disagree.
So when is it worth it?
Two cases, and they are both specific rather than routine.
1. To fix a specific glitch
When one app or feature is clearly misbehaving, clearing that cache can genuinely fix it. Corrupted thumbnails, a chat app showing stale content, a browser serving an old broken version of a page, a download cache that got into a bad state: these are cache problems, and clearing the relevant cache is the right fix. This is targeted repair, not maintenance. Booting into Safe mode, which clears certain system caches that are "created again automatically as needed," is the system's own version of this.
2. To reclaim real space from a large cache
Some caches genuinely get big, and clearing them is a legitimate way to get storage back, as long as you understand you are trading space for rebuild time, not buying speed. The clearest example is a video editor's media cache: Premiere's conformed audio and peak files, or After Effects' disk cache, can run to many gigabytes. Clearing them frees that space, and the app rebuilds what it needs from your originals. That is a storage decision, and a sound one.
Clearing a cache to reclaim space is reasonable. Clearing a cache to make your Mac faster is not, because it does the reverse in the short term and nothing in the long term. Keep those two motivations separate and you will make the right call every time.
What this means in practice
- Do not clear caches on a schedule or "just in case." It does not help, and it costs you rebuild time.
- If something is broken, clear that one cache, or boot into Safe mode. Targeted, not blanket.
- If a specific cache is large and you need the space, clear it knowingly, understanding the app will rebuild it.
- For general speed, look elsewhere: Memory Pressure, startup items, and genuinely large files, not caches.
Clear caches for the right reason
StorageSage never clears caches to chase phantom speed. It shows you which caches are actually large, labels each one by what it costs to rebuild, and reclaims space only when you choose, sending everything to the Trash first.
Download for macOSSources
- Apple — Mac User Guide on optimizing storage (macOS clears caches and logs that are safe to delete); safe mode support article (system caches recreated as needed).
- Howard Oakley, The Eclectic Light Company — explainers on caching and on caches and purging in current macOS (caches improve performance; clearing is not routine maintenance; the QuickLook example).