How to Free Up Disk Space on Mac in 2026

Apple gives you a pretty bar chart under About This Mac → Storage that tells you exactly nothing useful. "System Data: 47 GB." Thanks, very helpful. You know you have 47 GB of mystery, and you still don't know what to delete.

This guide skips the obvious advice ("empty your Trash!") and focuses on where space actually disappears on a real Mac in 2026. That's especially true for developers, creatives, and anyone who has been using the same machine for more than a year.

Where All That Storage Actually Goes

The first time I ran a proper disk analysis on a two-year-old developer MacBook Pro, the results were embarrassing. Not because the Mac was messy. Because of how invisible the clutter was. Node modules from abandoned side projects. Seven copies of the same client brief renamed slightly differently. A 14 GB Xcode simulator runtime for iOS 15 that I hadn't touched in eighteen months.

Here's what actually fills up most Macs:

Notice something about that table: most of the biggest offenders are caches that rebuild themselves. You can delete them without losing any work. Your tools just regenerate them the next time they need them. That's the low-risk, high-reward category. Start there.

Quick Wins You Can Do Right Now

These take under 10 minutes and require no tools beyond what macOS already gives you:

Developer Caches (The Biggest Hidden Culprit)

If you write code, this section is for you. Developer caches are by far the most efficient storage recovery on a Mac that gets used for software development. They're also the most invisible. They live inside hidden Library folders or deeply nested project directories that normal Finder browsing never surfaces.

Xcode: DerivedData and Simulators

Xcode caches compiled output in a folder called DerivedData. For a project you've built dozens of times across multiple Xcode versions, this folder can grow to 10 to 20 GB without you ever noticing. It's completely safe to delete. Xcode rebuilds it on the next compile.

Simulator runtimes are the other big Xcode offender. Each iOS version you've ever tested against takes up 3 to 6 GB. Realistically you only need the current iOS version, maybe one back for compatibility testing. The rest can go.

Delete simulators: Xcode → Window → Devices and Simulators → Simulators tab. Select the ones you don't use and press Delete.

node_modules: The Silent Folder That Never Sleeps

Every Node.js project you've cloned has a node_modules directory. Each one is typically 200 MB to 2 GB depending on the project's dependency count. If you have ten old repos on your machine, that's potentially 10 to 15 GB of modules for code you haven't touched in a year.

The terminal approach to find all of them:

# Find all node_modules directories and their sizes
find ~/Projects -name "node_modules" -type d -prune | head -20

# If you want sizes too:
find ~/Projects -name "node_modules" -type d -prune -exec du -sh {} \;

Then delete whichever projects you're done with. When you come back to an old project, run npm install and everything comes back in minutes.

Other Caches Worth Checking

Finding and Removing Duplicate Files

Duplicates are sneaky. They don't accumulate in one obvious place. They scatter across Downloads, Desktop, iCloud Drive, and whatever folder your last project was in. You'll have three copies of a client logo, four versions of a contract PDF with names like "contract_FINAL_v2_USE_THIS_ONE.pdf", and a dozen identical iPhone photos that got re-imported twice.

Manual method: Finder search (tedious, but free)

Finder doesn't have a true duplicate finder. What you can do is sort by size, look for files of identical sizes, and manually check them. For photos, Smart Albums in Photos.app can surface duplicates. But for general files across your whole drive, manual scanning stops being practical pretty quickly.

Better: a content-based duplicate scanner

A good duplicate finder scans by file content (not name), so it catches files that were renamed. Files Magic AI's System Cleaner does this. It computes checksums, groups exact matches, and shows you which copy to keep based on location and date. You never delete blindly; every removal is a deliberate choice.

Unused Apps and Their Leftover Support Files

When you delete an app by dragging it to Trash, macOS removes the .app bundle. What it does not remove: the support files stored in ~/Library/Application Support/, preferences in ~/Library/Preferences/, and caches in ~/Library/Caches/. These can collectively add up to hundreds of megabytes, sometimes gigabytes for apps like design tools or video editors.

Then there are apps you still have installed but haven't opened in six months. They're taking up space without giving you anything back. A good cleaner surfaces these sorted by last-used date so you can make a quick decision.

To find leftover support files manually: open Finder, press ⌘⇧G, and go to~/Library/Application Support/. Sort by size. The folders named after apps you've uninstalled are safe to delete.

Using Files Magic AI System Cleaner

If you want to do all of the above in one session without Terminal commands or hunting through Library folders, Files Magic AI has a System Cleaner built specifically for this. Here's how it works in practice:

Most developers I know recover 15 to 40 GB on the first scan. It's less about what you didn't know existed and more about the friction of finding it manually. A scan removes the friction.

Method Comparison: Which Approach Is Worth Your Time?

Keeping Your Mac Clear Long-Term

Cleaning up once is satisfying. Keeping it clean is a different problem. Here's what actually works without becoming a chore:

• Set a Downloads folder rule: Anything older than 90 days that you haven't opened gets deleted. You can automate this with Files Magic AI's scheduling feature, or just manually review it once a quarter.
• Delete node_modules when a project goes inactive: The moment you archive a project or finish a contract, run rm -rf node_modules in the project root. You can always restore with a single command.
• Keep only two Xcode simulator versions: Current iOS release plus one back. Delete the rest.
• Run a system scan quarterly: Developer caches accumulate fast. A quarterly scan with Files Magic AI (or manually via Terminal) catches what daily habits miss.
• Move completed project archives to external storage: Not everything needs to live on your primary SSD. A project you closed six months ago belongs on a backup drive or cold storage, not eating your NVMe.

Frequently Asked Questions

Published June 27, 2026 · More guides · Files Magic AI