How to Clear Temp Files on Mac (2026 Guide)

Your Mac says it's almost out of space. You open Storage settings, and half the bar is labeled "System Data" or "Other" — a black box that somehow ate 40GB and won't tell you why.

Temp files are usually the biggest chunk of that mystery blob.

I've cleaned out enough MacBooks (mine and other people's) to know the difference between a five-minute fix and a mistake that breaks three apps before lunch. Here's the version that actually works, and where the "just delete everything in /tmp" advice goes wrong.

Why Your Mac Is Full of Temp Files in the First Place

macOS doesn't have one "temp folder" the way Windows does. It has several, each with a different job and a different risk level if you touch it wrong.

The big ones:

• /private/var/folders/ — per-app scratch space macOS assigns automatically, holding thumbnails, render caches, and process leftovers
• ~/Library/Caches/ — user-level app caches (browsers, Xcode, Adobe apps, Slack — these get huge)
• /Library/Caches/ — system-wide caches shared across all users on the machine
• ~/Library/Application Support/ — not technically temp, but stuffed with logs and leftover data from apps you may have already deleted
• /private/tmp/ — the closest thing to a real "temp" folder, cleared automatically on most reboots

Here's the part most cleanup guides skip: macOS is already trying to manage a lot of this for you. Since Sierra, there's a background process that purges old cache files when disk space runs low, without asking permission first.

That's exactly why a lot of "Other" storage doesn't clear itself — the threshold that triggers automatic cleanup is higher than most people expect, so files pile up well before macOS bothers stepping in.

Xcode's DerivedData folder alone can quietly grow past 20GB on a developer machine, and browsers like Chrome will happily cache gigabytes of site data that never gets touched again.

There's also a generational quirk worth knowing about. On Apple Silicon Macs, Rosetta 2 keeps its own translation cache for x86 apps, which adds another layer most Intel-Mac guides never mention.

Docker Desktop is another quiet offender — its VM disk image can balloon well past its actual container usage if you never run a prune command, and I've seen it hit 60GB on machines that only run a couple of lightweight containers.

None of this is a bug exactly. It's just how caching works — trade disk space for speed, and let the user deal with the cleanup later.

Comparison: Which Cleanup Method Actually Works

Not every method is built for the same job. Here's how the main options actually stack up once you've used each one for a while.

In my testing, the built-in Manage Storage panel (Apple menu > About This Mac > Storage > Manage) catches the obvious stuff — old iOS backups, unused apps, large attachments — but it barely scratches app-level cache bloat.

Terminal gets you further, but only if you know which folders are safe to touch and which ones will make an app forget your login session.

Real-World Testing: What Actually Freed Up Space

I ran this on a MacBook Pro that had been chugging along for about 18 months without a real cleanup — 14GB of "Other" storage sitting there, untouched.

Step 1: Check what's eating space first.

• Open Finder, hit Cmd+Shift+G, type ~/Library/Caches
• Sort by size — this alone usually surfaces the worst offenders
• Look for browser folders (Chrome, Safari WebKit data), Slack, Spotify, and any Adobe apps

Step 2: Clear user-level caches safely.

• Quit the app first — deleting cache files from a running app can cause crashes or corrupted preferences
• Delete the contents inside the app's folder in ~/Library/Caches, not the folder itself
• Relaunch the app and confirm it opens normally before moving to the next one

Step 3: Handle Xcode and developer caches (if applicable).

• Run du -sh ~/Library/Developer/Xcode/DerivedData to check the size before deleting anything
• Xcode rebuilds this automatically, so it's one of the lowest-risk folders to clear entirely

On my test machine, clearing browser caches and DerivedData alone recovered just under 11GB — most of that "Other" storage mystery, gone in about fifteen minutes.

Step 4: Verify the results before calling it done.

• Reopen About This Mac > Storage and let it recalculate — this can take a minute or two on first load
• Check Activity Monitor's Disk tab briefly after relaunching your usual apps, just to confirm nothing is stuck re-caching aggressively
• If an app feels slower on its first launch after a cache clear, that's expected — it's rebuilding what you deleted, and it should return to normal within a session or two

I also timed a cold boot before and after the cleanup out of curiosity more than expectation. The difference was marginal — a few seconds — which lines up with what I'd tell anyone expecting a dramatic speed boost from cache clearing alone.

Pro Tip: Before deleting anything from ~/Library/Caches, check if the folder belongs to an app that's currently logged in somewhere (Slack, Discord, email clients). Clearing those caches sometimes forces a re-login and, in rarer cases, a re-sync of large mail attachments — annoying on a slow connection.

If you're dealing with a Mac cluttered by apps you installed and forgot about, it's worth pairing this with a proper uninstall pass — leftover app support files are a huge chunk of what accumulates over a year of casual downloads, and I've covered the difference between dragging an app to Trash and actually removing everything it left behind in a piece on removing unused launchers cleanly, which applies well beyond just that one app.

The Honest Limitations Nobody Mentions

Temp file cleanup has a ceiling, and it's lower than most YouTube thumbnails suggest.

• It's not a permanent fix. Caches rebuild the moment you reopen an app — you're managing an ongoing process, not solving it once
• Some "temp" files aren't safe to touch. Deleting active /private/var/folders/ contents while apps are running can cause crashes, not speed gains
• It won't fix a genuinely full drive. If your Mac only has 128GB and you've got 100GB of photos and videos, temp file cleanup buys you a few gigabytes, not a solution
• Third-party cleaner apps vary wildly in quality. Some are legitimate; others flag harmless files as "junk" to make their scan results look more dramatic than reality

I've also seen the opposite problem: people who get aggressive with Terminal commands and delete system-level cache folders they don't fully understand, then wonder why Spotlight indexing breaks or why a menu bar app stops launching.

If you're not sure what a folder does, the safer move is leaving it alone and researching it first — reversing macOS after a bad system-level delete is a lot harder than it sounds.

• Cleanup results aren't consistent across machines. How much space you recover depends entirely on what you've installed and how long it's been since the last clean — a fresh MacBook and a five-year-old daily driver will show wildly different numbers for the exact same steps
• Some apps regenerate caches faster than others. Chrome and Slack can rebuild several hundred megabytes of cache within a single day of normal use, so don't expect the freed space to stay freed indefinitely

Practical Setup: Commands and Habits That Actually Help

If you want to go the Terminal route, here's what I actually run, in order.

Check total cache size before touching anything:

du -sh ~/Library/Caches

Clear a specific app's cache (replace with the actual folder name):

rm -rf ~/Library/Caches/com.example.appname/*

Clear the system-wide temp directory (safe on almost any modern Mac):

sudo rm -rf /private/tmp/*

• Never run rm -rf on /Library/Caches as a whole — some system caches are actively referenced and clearing them mid-session can cause instability
• Restart the affected app after clearing its cache, not just relaunch from the dock — a full quit-and-reopen clears any in-memory references too
• Set a recurring reminder every couple of months rather than waiting for a "storage full" warning — prevention beats a 20GB emergency cleanup

If you'd rather not remember to do this manually, a basic launchd job can run a cleanup script on a schedule:

• Write a short shell script containing your preferred rm -rf commands, scoped only to caches you've already confirmed are safe
• Save a .plist file in ~/Library/LaunchAgents pointing to that script, with a StartInterval set to something like 30 days
• Load it with launchctl load ~/Library/LaunchAgents/yourfile.plist and forget about it until you actually check your storage again

I'd only recommend automating this once you've done the manual version a few times and know exactly which folders are safe for your specific setup — automating a mistake just means repeating it every month instead of once.

Pro Tip: Run du -sh ~/Library/Caches/* (with the trailing /*) instead of just the parent folder — it breaks down size per app instead of giving you one lump number, which makes it obvious which app is actually the problem before you start deleting anything.

For anyone managing an older Mac that's also just running hot or loud on top of storage pressure, it's worth checking whether dust buildup is compounding the slowdown — a machine fighting thermal throttling and a full drive at the same time behaves very differently than one dealing with just a single issue, and general hardware upkeep is covered well in a guide on keeping your machine running clean over time.

If you're deciding between a cleanup and a fresh machine altogether, storage isn't the only variable worth checking — how much memory your workflow actually demands matters just as much, and that's worth sorting out before assuming an old Mac is beyond saving.

Pro Tip: If "Other" storage stays stubbornly high even after a full cache clear, check Time Machine local snapshots with tmutil listlocalsnapshots / — these count toward storage but don't show up in a normal cache sweep, and deleting stale ones with tmutil deletelocalsnapshots can recover several extra gigabytes.

FAQ

Is it safe to delete everything in /private/var/folders? No — this folder holds active process data for apps that may currently be running, and clearing it while the system is live can cause crashes rather than speed gains. Stick to ~/Library/Caches for the safest, highest-impact cleanup.

Will clearing temp files speed up my Mac? Sometimes, but modestly — the bigger speed gains usually come from freeing enough space that macOS stops struggling with virtual memory swapping, not from the cache deletion itself. If your drive is over 85% full, clearing temp files can noticeably help; on a half-empty drive, don't expect much.

Do I need third-party cleaner apps, or does Terminal do the same thing for free? Terminal reaches the same folders most paid cleaners target, for free, but it requires knowing which folders are safe. A cleaner app trades that manual knowledge for convenience and a subscription fee — worth it for non-technical users, unnecessary for anyone comfortable in Terminal.

How often should I clear temp files on a Mac? Every two to three months for average use, or monthly if you're a developer or heavy Chrome user generating large caches constantly. Waiting until storage alerts start is the least efficient time to do it, since you're then choosing what to delete under pressure instead of methodically.

Can clearing temp files delete my personal files by mistake? It can, if you target the wrong folder — ~/Library/Application Support in particular holds real user data for some apps, not just disposable cache. Stick to folders explicitly labeled Caches, verify with du -sh before deleting anything large, and back up anything you're unsure about before running a bulk delete command.

Temp file bloat on macOS isn't going away — if anything, cache-heavy apps like Chrome, Slack, and modern IDEs are only getting hungrier for local storage as they lean on more aggressive local caching for speed. The fix isn't a one-time deep clean; it's building a habit around checking ~/Library/Caches every couple of months before "Other" storage becomes a 20GB surprise again.

Apple's automatic purging helps at the margins, but it's tuned conservatively enough that manual intervention still wins for anyone who actually wants their space back. Base storage tiers on new Macs haven't grown nearly as fast as the size of modern app caches, which means this is a maintenance habit that's only becoming more relevant, not less.

The Macs that stay fast for years aren't the ones that never accumulate cache — they're the ones where somebody actually checks in on it every so often instead of waiting for a red storage bar to force the issue.