How to Free Up Space on Your Mac in 2026: Complete Guide

If your Mac is warning you about low storage, you are not alone — and the fix is not as simple as emptying the Trash. This guide walks through every reliable method for how to free up space on your Mac, in priority order, so you recover real gigabytes rather than a few hundred megabytes. We will cover caches, System Data, large files, Downloads, Mail attachments, and iCloud offloading, with the actual paths and Terminal commands you need.

Before You Start: Check What Is Actually Using Space

Open Apple menu → System Settings → General → Storage. The bar chart breaks your disk into categories: Applications, System Data, Documents, iCloud Drive, and so on. Keep this window open as you work through the steps below — the numbers will not always update instantly, but they give you a baseline.

If a category says System Data and shows more than 20–30 GB, that is usually the single biggest opportunity and we will cover it in depth below.

Step 1: Clear User and System Caches

Caches are temporary files apps create to load faster. They are safe to delete — apps will simply rebuild them. On a Mac used for a year or more, caches routinely accumulate 5–20 GB.

Where caches live

• ~/Library/Caches — your personal app caches (Spotify, Slack, Chrome, Xcode, etc.)
• /Library/Caches — system-wide caches (requires admin password to clear)
• /private/var/folders/ — macOS temporary session caches, managed by the OS

Clearing your user cache manually

1. Quit all open applications first.
2. In Finder, press Shift-Command-G and type ~/Library/Caches, then press Return.
3. Select all subfolders (Command-A) and move them to the Trash.
4. Empty the Trash, then restart your Mac.

What is safe vs. not safe: Everything inside ~/Library/Caches is safe to delete. Do not delete the ~/Library folder itself — it contains application support data, preferences, and keychains you would not want to lose.

Log files

Log files pile up in ~/Library/Logs and /Library/Logs. They are safe to delete entirely. You can remove them in Terminal:

rm -rf ~/Library/Logs/*
sudo rm -rf /Library/Logs/*

Typical recovery: 1–5 GB on a well-used machine.

Step 2: Attack System Data (the Biggest Hidden Culprit)

The System Data category in macOS Storage includes a mix of things: Time Machine local snapshots, iOS device backups, font caches, purgeable space, and files macOS cannot categorize. It is opaque by design, which is why it alarms so many users.

Delete old iOS and iPhone backups

1. Open Finder, select your iPhone or iPad in the sidebar, click Manage Backups.
2. Right-click any outdated backup and choose Delete Backup.

Old device backups can be 5–20 GB each and you likely only need the most recent one.

Remove APFS local Time Machine snapshots

When Time Machine cannot reach its backup disk, macOS stores local snapshots on your internal SSD. List them in Terminal:

tmutil listlocalsnapshots /

Delete all local snapshots at once:

tmutil deletelocalsnapshots /

This can reclaim 10–40 GB on machines that have been offline from a backup drive for weeks.

Purgeable space

macOS marks certain files — iCloud-optimized originals, watched iTunes content, old iOS updates — as purgeable. These count toward System Data but macOS will reclaim them automatically when disk pressure rises. You can force the process by running du or simply downloading a large file: macOS will purge on demand. Most third-party cleaning tools can also trigger this flush explicitly.

Step 3: Purge the Downloads Folder

The Downloads folder is the most consistently neglected source of large files. Disk images (.dmg), installer packages (.pkg), zip archives, and video files accumulate here because there is no automatic cleanup.

1. Open ~/Downloads in Finder.
2. Switch to List view (Command-2) and click Date Added to sort newest first.
3. Sort by Size to identify the biggest culprits. Disk images for apps you have already installed can almost always be deleted.
4. Move what you do not need to the Trash and empty it.

Typical recovery: 2–15 GB on a machine used for a year or more.

Step 4: Clear Mail Attachments

The macOS Mail app downloads every attachment you open and stores it permanently at ~/Library/Mail/V10/ (the version number varies by macOS). On a busy email account this folder can reach several gigabytes.

1. In the Mail app, open Mail → Settings → Accounts and verify each account is set to download attachments only when opened, not automatically.
2. To clear already-downloaded attachments, navigate to ~/Library/Mail/ in Finder (use Shift-Command-G), open the versioned subfolder, and look for Attachments folders inside each account directory. You can delete the contents of those folders safely — Mail will re-download any attachment if you open that email again.

Caution: Do not delete the ~/Library/Mail/ directory itself or any .mbox bundles — those contain your actual email messages.

Step 5: Find and Remove Large Files

A few unexpectedly large files often account for more wasted space than a hundred small ones. Common offenders:

• Virtual machine images (.vmdk, .vhdx, Parallels .pvm bundles) — often 20–80 GB
• Old Xcode simulators and derived data (~/Library/Developer/Xcode/DerivedData)
• Homebrew bottles and old formula versions ($(brew --cache))
• Final Cut Pro libraries and render caches

To clean Xcode derived data and simulators from Terminal:

# Remove derived data
rm -rf ~/Library/Developer/Xcode/DerivedData/*

# Remove unavailable simulators
xcrun simctl delete unavailable

# Remove Homebrew cache
brew cleanup --prune=all

These three commands alone can free 5–30 GB on a development machine.

To find large files manually via Terminal (files over 500 MB, excluding Time Machine):

find ~ -size +500M -not -path "*/Backups.backupdb/*" 2>/dev/null

Step 6: Offload to iCloud and Optimize Storage

If you have an iCloud+ subscription, macOS can store original full-resolution photos and rarely used files in iCloud while keeping local low-resolution proxies or stubs on your SSD. This does not delete your data — it just moves the heavy originals off your local drive.

1. Go to Apple menu → System Settings → [Your Name] → iCloud.
2. Turn on Optimize Mac Storage — macOS will automatically offload older files when space is tight.
3. In the Photos app: Settings → iCloud, choose Optimize Mac Storage.

One honest caveat: If you lose internet access, offloaded files become temporarily unavailable until they re-download. iCloud offloading is a trade-off, not a permanent cleanup. For files you genuinely no longer need, deletion is more reliable than offloading.

Step 7: Uninstall Apps You No Longer Use

Dragging an app to the Trash removes the .app bundle, but it leaves behind support files, caches, and preferences scattered across ~/Library/Application Support, ~/Library/Caches, and ~/Library/Preferences. On apps like Adobe Creative Cloud or Xcode these leftovers can be several gigabytes.

The thorough approach is to find and remove each app's associated files before or after dragging the app to Trash. This is tedious to do manually — you need to know each developer's bundle ID and then hunt across multiple Library subfolders.

This is exactly what Crumb's Uninstall tab handles: it scans for all leftover files associated with any app you select, shows them as a checklist before anything is deleted, and moves the full set to Trash in one step. If you are unsure whether a leftover folder is safe to remove, Crumb's built-in "Is this safe to delete?" AI explains what the folder does and rates its removal risk, so you are never guessing.

The One-Click Alternative to Steps 1–5

If working through each of the above steps manually sounds like a Saturday project, download Crumb — it handles user caches, system caches, logs, temp files, and purgeable System Data in a single click from the menu bar. Crumb shows you exactly what it will delete and how much space you will recover before touching anything, so nothing is deleted silently. The one-click Clean covers the same ground as steps 1 through 5 in this guide, minus the developer-specific commands (Xcode, Homebrew) which you would still run manually.

Quick-Reference Comparison

What You Should Never Delete

A few folders look like clutter but are not:

• ~/Library/Application Support/ — contains app databases, saved states, and sometimes irreplaceable user data.
• ~/Library/Keychains/ — your passwords. Do not touch.
• /System/ and /Library/ at the root level — system files protected by SIP; you cannot accidentally delete most of these, but do not try.
• ~/Library/Mail/ directory itself — your emails live here.
• Any .photoslibrary bundle — this is your entire Photos library.

When in doubt, the safest rule is: if you did not put it there and you do not know what it is, look it up before deleting. Moving something to the Trash before emptying gives you a recovery window. Once the Trash is empty, the deletion is permanent.

Conclusion

Freeing up space on a Mac in 2026 comes down to four high-yield areas: caches and logs, System Data (especially local snapshots and old device backups), large forgotten files in Downloads and developer folders, and app leftovers from uninstalls. Working through this guide in order should realistically recover 20–60 GB on a machine that has never been cleaned, with no data you actually care about lost in the process. If you want to automate the routine parts — caches, logs, temp files, and purgeable storage — and get a clear breakdown of what is eating your disk before anything is deleted, Crumb is built specifically for that.