Guide · 6 min read

How to free up disk space on a Mac (2026)

“Your disk is almost full” always shows up at the worst time. Here's where the space actually goes on a modern Mac, how to reclaim it safely by hand, and how to do it in seconds.

1. See what's actually using space

Before deleting anything, find the big offenders. Apple's built-in tool gives a rough picture: open → System Settings → General → Storage. For a real breakdown by folder, a disk map (treemap) is far more useful - it shows your biggest folders first so you don't waste time on small stuff.

2. Empty caches and temporary files

Apps pile up caches in ~/Library/Caches. They're safe to clear - apps rebuild them - and can free several gigabytes.

In Finder, press Cmd-Shift-G and enter ~/Library/Caches
Sort by size and delete the largest folders you recognize (e.g. browser, IDE, Spotify)
Empty the Trash to actually reclaim the space

Tip: Never delete the whole ~/Library folder - only items under Caches. And avoid system caches in /System; macOS manages those.

3. Find and remove large files

Old video exports, disk images, VM files and downloads are usually the biggest single wins. Sort your Downloads and Movies folders by size, and search for files over 1 GB.

4. Delete duplicate files

Duplicates accumulate from downloads, AirDrop and copies. Identical large files (photos, design files, exports) are the ones worth removing - keep one copy of each.

5. Uninstall apps completely

Dragging an app to the Trash leaves behind caches, preferences, and support files in ~/Library. Removing those leftovers too can reclaim hundreds of megabytes per app.

6. Thin local Time Machine snapshots

macOS keeps local snapshots that quietly use disk (shown as "purgeable"). You can list and remove them with tmutil, or let a tool thin them safely.

tmutil listlocalsnapshots /

7. Developers: clear build artifacts

This is the hidden giant. node_modules, Xcode DerivedData, Rust target/, .next, Python venvs - they pile up across every project and can total tens of gigabytes. They're all regenerable. See our dedicated guide on deleting node_modules safely.

8. Clear the Trash and Downloads

Obvious, but easy to forget: the Trash holds everything you "deleted" until you empty it, and Downloads is where files go to be forgotten.

9. The fast way: TidyBar

Doing all of the above by hand works, but it's tedious and easy to get wrong. TidyBar scans for all of it at once - caches, large files, duplicates, app leftovers, snapshots and developer build junk - shows you exactly what's reclaimable for free, and removes it to the Trash (so nothing is ever truly gone) in one click. $25 once, no subscription.

FAQ

Is it safe to delete cache files on a Mac?+

Yes - files in ~/Library/Caches are safe to remove; apps rebuild them. Avoid system caches in /System and never delete the whole Library folder.

What is taking up so much space?+

Usually caches, large media/VM/disk-image files, duplicates, app leftovers, local snapshots, and - for developers - build artifacts like node_modules and DerivedData.

Will I lose anything?+

If you stick to caches, duplicates and regenerable build folders, no. TidyBar moves everything to the Trash so you can restore it if needed.

Do it all in one click with TidyBar

Scan free to see what you can reclaim. $25 one-time · no subscription.

Download TidyBar

More: free up disk space · compare cleaners