Here is a number that surprises almost every Mac owner: a single browser cache can quietly balloon into several gigabytes after a year of normal use. On a 256 GB MacBook Air, that is the difference between a comfortable machine and one that nags about storage every other week. Yet “clear the cache” is one of the most misunderstood instructions in tech support, because it can mean four completely different things depending on who is saying it. This guide untangles them, walks through each method step by step, and flags the mistakes that turn a five-minute cleanup into an afternoon of re-downloading and re-logging in everywhere.
What “Cache” Actually Means on a Mac
Before touching anything, it helps to know what is being deleted. A cache is a store of temporary files that apps use to avoid redoing slow work, like re-fetching images from a website or rebuilding a thumbnail. Deleting it is not the same as deleting your files. Nothing important disappears, but things do get slower for a little while as the system rebuilds what it needs.
On macOS, “clear cache” usually refers to one of four layers:
| Cache type | Where it lives | What clearing it fixes |
|---|---|---|
| Browser cache | Inside Safari, Chrome, Firefox, or Edge | Stale pages, broken logins, layout glitches |
| App caches | `~/Library/Caches` | Apps bloating storage, odd behavior after updates |
| System caches | `/Library/Caches` | Rarely worth touching; rebuilt automatically |
| DNS cache | Managed by the system resolver | Sites loading from old IP addresses, network oddities |
Most people who think they need to clear “the Mac cache” actually just need the first one. The others are situational. Knowing which layer you are targeting is the single biggest factor in whether the cleanup helps or hurts.
Clearing the Safari Cache the Supported Way
Safari is the browser most Mac users live in, and its cache is the easiest to clear properly. Apple’s own guidance keeps this inside the app rather than in the file system, which is the safest route. (Clear the cache in Safari on Mac)
- Open Safari and go to Safari > Settings (called Preferences on macOS versions before Ventura, released in 2022).
- Click the Privacy tab.
- Choose Manage Website Data.
- Click Remove All to wipe cached data for every site, or search for a single site and remove just that one.
If the Develop menu is enabled (Safari Settings > Advanced > Show features for web developers), there is also a quick Develop > Empty Caches command. It clears the cache without touching cookies, which is handy when you want to stay logged in. The difference matters: clearing website data logs you out everywhere, while emptying caches does not.
A practical tip from years of troubleshooting: if a site looks broken, try a private window first. If the page loads correctly there, the cache is the culprit and clearing it is justified. If it is broken in a private window too, the problem is the site, not your Mac, and clearing anything will not help.
Clearing Chrome, Firefox, and Edge Caches
Third-party browsers manage their own caches, and each vendor documents the flow separately. The steps are similar across all three:
- Open the browser’s settings.
- Find the privacy or history section.
- Choose “clear browsing data.”
- Select Cached images and files only, and pick a time range such as “last 7 days” if you want to keep older sessions intact.
The common mistake here is ticking every checkbox. That wipes passwords, autofill, and cookies along with the cache, and the next week becomes a parade of password resets. If the goal is purely to free space or fix a stubborn page, select the cache option alone. For a deeper cleanup that includes cookies and site data, the step-by-step guide to clearing browser cache and cookies covers the trade-offs in more detail. (Cache (computing)))
Should You Delete the ~/Library/Caches Folder?
This is where opinions split, and it is worth being honest about the debate. The user cache folder at `~/Library/Caches` holds data from dozens of apps, and deleting its contents is generally safe in the sense that macOS and apps rebuild what they need. But “safe” is not the same as “recommended.” Apple has historically steered users toward built-in storage tools rather than manual file deletion, and there is a real cost: the first launch of every app afterward feels sluggish, some apps briefly misbehave, and a few (especially creative and development tools) take a long time to regenerate their working data.
The folder is hidden by default. To reach it, open Finder, choose Go > Go to Folder, and paste `~/Library/Caches`. From there, sort by size and delete only the folders belonging to apps you recognize and rarely use. Never delete the whole folder itself, only its contents, and leave anything you do not recognize alone.
A better first stop is System Settings > General > Storage. macOS surfaces large categories there, offers recommendations, and lets you review big files without guessing. For most people, that panel plus a browser cache clear solves the storage complaint entirely. The system-level `/Library/Caches` folder is a different beast: it requires admin rights, Apple does not position manual deletion as routine maintenance, and the payoff is small. Skipping it is a perfectly defensible choice.
Flushing the DNS Cache When Websites Misbehave
Sometimes the cache that needs clearing is not files at all. The DNS cache maps domain names to IP addresses, and when a site moves servers, your Mac can keep knocking on the old door for hours. The symptom is distinctive: a site works on your phone but not your Mac, or works over a different network.
The fix is a Terminal command that has stayed stable across macOS releases:
- Open Terminal from Applications > Utilities.
- Run `sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder`.
- Enter your admin password when prompted. Nothing visible happens, which is normal.
This is a low-risk operation with no downside beyond retyping the command if you make a typo. It is also the correct answer to a surprising number of “the internet is broken” tickets. If network weirdness persists after a flush, the next suspects are the router and the browser, not the file system.
The Mistakes That Turn a Quick Cleanup Into a Bad Day
A few patterns show up again and again in support forums, and avoiding them saves real time.
Clearing everything at once. Wiping all caches, cookies, and history in one sweep feels efficient but costs you every saved login and preference. Target the specific layer causing the problem.
Deleting caches to fix a slow Mac. Cache files are not the usual cause of slowness. Startup items, low free storage, and background processes matter far more. If the machine feels sluggish rather than full, run a malware check before deleting anything; the guide to checking for malware on a Mac walks through the signs. A good antivirus tool is worth having too, and this roundup of the best antivirus options for Mac compares the practical choices.
Forgetting that caches come back. Clearing a browser cache is not a permanent fix. If the same site breaks weekly, the site itself is the problem, and a support ticket will do more than a tenth cache clear.
Ignoring the app-level setting. Many apps, from Slack to Photoshop, have their own “clear cache” button buried in preferences. Using it is always safer than deleting folders by hand, because the app knows exactly what it can rebuild.
Skipping the restart. After clearing system-level caches, a restart lets macOS rebuild cleanly and settles any app that was mid-write. It sounds trivial, but it resolves a large share of post-cleanup oddities.
A Sensible Order of Operations
When storage is tight or a page will not load, work from least disruptive to most:
- Try a private browsing window to confirm the cache is actually at fault.
- Clear the browser cache through the browser’s own settings.
- Check System Settings > General > Storage for large files and recommendations.
- Flush the DNS cache if the issue looks network-related.
- Only then consider deleting specific folders inside `~/Library/Caches`, one app at a time.
This order respects a simple principle: the more you delete, the more the system has to rebuild, and rebuilding costs time. The goal is the smallest deletion that solves the problem, not the biggest one possible.
How Often Is This Really Necessary?
Honest answer: far less often than the internet suggests. Browser caches are self-managing and evict old data on their own. A reasonable rhythm for most people is clearing the browser cache when a site misbehaves or every few months as light housekeeping, and leaving everything else alone unless storage warnings appear. Power users who work with large media files or web development may clear more aggressively, but that is a workflow preference, not a requirement.
It also helps to remember that cache clearing is a diagnostic tool as much as a maintenance task. When something is wrong, clearing a cache is a cheap way to rule out one cause. When nothing is wrong, it is mostly busywork. Treating it that way keeps the Mac fast and the user sane.
Conclusion
Clearing the cache on a Mac is less about one magic button and more about knowing which of four caches you are dealing with. Safari and the other browsers handle their own caches through settings that are safe and reversible. The `~/Library/Caches` folder can be pruned, but it should be pruned selectively and with realistic expectations about the rebuild cost. The DNS cache is a one-line Terminal fix for a specific class of network problems. Get that mapping right, avoid the temptation to wipe everything, and the whole job takes minutes rather than an afternoon. The Mac, in the end, mostly maintains itself; the user’s job is to intervene only when there is an actual symptom to fix.
Frequently Asked Questions
Does clearing the cache delete photos or documents?
No. Caches hold temporary copies of data that apps can regenerate, such as website images and thumbnails. Your photos, documents, and other personal files live in separate locations and are untouched by any cache-clearing method described here.
Is it safe to delete everything inside the ~/Library/Caches folder?
It is generally safe in that apps rebuild what they need, but it is not recommended as routine maintenance. Expect slower first launches and occasional odd behavior while caches regenerate. Delete individual app folders you recognize rather than the entire contents, and never delete the folder itself.
Why does my Mac still show low storage after clearing the cache?
Browser and app caches are often a small fraction of total storage. Large culprits are usually Photos libraries, downloads, old iOS backups, mail attachments, and virtual machine images. The Storage panel in System Settings breaks these down and is the better starting point for a space problem.
How do I clear the cache if I cannot find the Library folder?
The Library folder inside your home directory is hidden by default. Open Finder, choose Go > Go to Folder, and enter `~/Library/Caches`. Alternatively, hold the Option key while opening the Go menu to reveal the Library entry directly.
Does clearing the cache log me out of websites?
Clearing cached images and files does not affect logins. Removing website data or cookies does, and you will need to sign in again on sites where you had active sessions. In Safari, use Develop > Empty Caches if you want to stay logged in.
How often should I clear the cache on a Mac?
For most people, clearing the browser cache when a site misbehaves or every few months is plenty. App and system caches rarely need manual attention. Frequent clearing mostly costs time through constant rebuilding and rarely delivers a noticeable performance gain.
