How to clear cache on a MacBook Air (browser, apps, and system)

Most people searching this want their browser cache cleared, and that takes about twenty seconds. But three different things get called "cache" on a Mac, and picking the wrong one is why so many pages on this topic feel like they are answering somebody else's question. So, in plain language:

• Browser cache: copies of images, scripts and page assets that Safari or Chrome saved so pages you revisit load quickly. Clear this when a site looks broken or keeps showing you an old version of itself.
• App and system cache: folders inside your hidden ~/Library where apps keep thumbnails, search indexes and downloaded content. Clear this when you want disk space back from apps you have stopped using.
• Whatever a cleaner app means by "cache": usually a mix of the first two, presented as the reason your Mac is slow. It generally isn't, and there is a section on that below.

Nothing here is specific to the Air. A MacBook Air, a MacBook Pro and a Mac mini running the same macOS clear cache in exactly the same way. The reason the Air comes up so often is that it is the machine most people buy at 256 GB, so its owners hit a full disk first.

The Safari steps below match Apple's current Safari User Guide, whose version selector lists them for macOS Sonoma 14 through Tahoe 26. The Chrome steps match Google's desktop help as of August 2026.

Clear your browser cache

Start here if a website is behaving strangely. This is the fix for a page that will not update, or a layout that has gone crooked on one site and one site only.

Safari

Apple documents the cache and cookies together, on one screen.

1. Open Safari.
2. In the menu bar, choose Safari > Settings, then click Privacy.
3. Click Manage Website Data.
4. Select one or more sites and click Remove, or click Remove All to clear the lot.

Apple attaches a caution to that screen, and it matters: removing this data may reduce tracking, but it may also sign you out of websites or change how they behave. If you only wanted a stubborn page to reload properly, clearing a single site from that list is enough, and you keep every other login you have.

Safari can also clear the cache and leave your logins alone, but that command sits behind the developer settings.

1. Choose Safari > Settings, then click Advanced.
2. Tick Show features for web developers. A Develop menu appears in the menu bar.
3. Choose Develop > Empty Caches for All Profiles.

Two things about that. Before Safari 17 the checkbox read "Show Develop menu in menu bar", so older instructions you find online will not match what is on your screen. And the menu item picked up "for All Profiles" when Safari gained profiles; on some setups it may simply read Empty Caches.

A lot of pages get the next part wrong. History > Clear History is not the cache command. Apple's page for it lists what it removes, and that list is history records, the back and forward lists, frequently visited sites, recent searches, page icons and snapshots, and the download list. Cached files and cookies are documented separately, on the Manage Website Data screen above. Use Clear History to tidy your history. Use Manage Website Data to clear cache and cookies.

Chrome

Google renamed this recently, which is why the button you remember may not be where you left it. It now reads Delete browsing data.

1. Open Chrome.
2. Press Command + Shift + Delete. (Or click the three-dot menu at the top right and choose Delete browsing data.)
3. Choose a time range, such as Last hour or All time.
4. Tick Cached images and files. Leave Cookies and other site data unticked if you want to stay signed in everywhere.
5. Click Delete data.

Chrome's own description of that first checkbox is precise: it removes text and images from pages you have visited. Those come back down the wire the next time you visit, which is why the first load afterwards feels slow.

Separately, if Chrome is the reason your fans are spinning, its cache is not what to look at. That is a memory question rather than a disk one, and Chrome using too much memory on Mac covers what actually helps.

Cookies and cache are not the same thing

These two get clubbed together in every menu, which is why people believe clearing cache signs them out. Cookies are what hold a sign-in. The cache only holds copies of page content.

Google's definitions are as clear as any: cookies are files created by the sites you visit, which save browsing data; the cache remembers parts of pages, like images, so they open faster next time. Delete cookies and, in Google's words, if you were signed in you will need to sign in again. Delete only the cached images and files and your logins survive, with the sites loading a little slower once while the pictures come back.

So: cache for a page that looks wrong, cookies for a sign-in that is stuck.

Clear app caches

This is the other meaning, and it is a storage job rather than a browsing one. Apps keep their own caches in your hidden Library folder, and some of them hoard. Slack, Discord, Teams, VS Code and Spotify are the usual names, and a single one can reach a few gigabytes without ever pruning itself.

The method is the same for all of them: quit the app, open the folder clearly labelled Cache inside its own folder, and empty that one folder rather than the folder above it, which holds real data. Clearing app caches on Mac has the exact paths per app and the traps to avoid. For the wider question of which caches are disposable and which are load-bearing, read is it safe to delete cache on Mac before you delete anything.

Two boundaries before you go digging. macOS already clears safe-to-delete caches and logs on its own when space runs low, so the folder you are about to scrub is partly self-managing. And system caches under /System/Library/Caches are not yours to hand-delete; Apple's documented way to clear those is booting into Safe Mode. Howard Oakley, who has measured what that returns, is blunt about the payoff: at worst, it may not free any significant storage space.

Does clearing cache speed up a MacBook Air?

Usually not. Frequently the opposite, for a while.

A cache is stored work: a downloaded image, a built search index, a rendered thumbnail. Keeping it means the Mac does not have to redo that work. Clearing it means the Mac does have to redo that work, immediately, while you sit there. Oakley puts the mechanism plainly: without all that caching, our Macs would be irritatingly slow.

Then the caches come straight back, because everything that made them is still running. So treat a cache clear as two things. It is a one-off reclaim of space, and it is a troubleshooting step for one specific glitch. Repeating it on a schedule buys you nothing.

If the Mac is slow, the cause is almost always somewhere else: a full disk, memory pressure, a process eating a core in the background, or an app that decided to reindex everything. Why your Mac is slow walks through the likely causes in order. That page will do more for you than any number of cache clears.

If it is space you are after

Then start with the categories that hold gigabytes rather than the ones that hold megabytes. Photos, old iPhone backups, the Downloads folder, and the big opaque slice macOS labels System Data are where the room usually is. How to free up space on Mac does this in order, and what you can safely delete marks the boundaries.

Also expect the numbers to argue with you. Deleting things does not always make free space go up straight away, because macOS holds some of it as purgeable space until something actually needs it. That is normal, and it catches everyone out once.

The short version

Browser cache lives in Safari or Chrome and is cleared from inside the browser, in about twenty seconds. App cache lives in your Library folder and is a disk-space job. Cookies are a third thing everyone lumps in with cache, and cookies are the part that signs you out. None of the three will make an ordinary MacBook Air faster in any lasting way, and anything promising otherwise is selling something.

The tedious part is the app-cache side: unhiding ~/Library, telling a disposable cache folder from an app that keeps real data next to it, and finding out which folders are big rather than which ones merely have "cache" in the name. Plumby measures allocated size, so the number it shows you is what a removal would return to the disk rather than what the file claims to be. It shows the exact path of everything before it moves, refuses to call a folder disposable just because of what it is named, and sends what it clears to the Trash by default, so you can put it back. The browser half stays where it belongs, in the browser.