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

Why Is My Mac Storage Full? The Real Culprits

Your Mac's storage does not fill itself up with important files. The real culprits are invisible accumulation — layers of caches, artifacts, and forgotten data that build up silently over months and years. Here is where your space is actually going:

App Caches

Every app you use stores temporary data in ~/Library/Caches/ to speed up future launches and operations. Browsers cache website assets, Spotify caches album art and audio, Slack caches workspace messages and files. The problem is these caches are never automatically pruned. A Slack cache can quietly swell to 10–15 GB. Chrome's cache can hit 5 GB on its own. Multiply that across a dozen apps and you are looking at 30–50 GB of data that serves little ongoing purpose.

Xcode and Developer Artifacts

Xcode is one of the single biggest disk consumers on any developer's Mac. Its DerivedData folder — located at ~/Library/Developer/Xcode/DerivedData/ — stores compiled build products for every project you have ever opened. Each build generates gigabytes of object files, intermediate products, and indexes. A developer with three or four active projects can easily accumulate 40–80 GB in DerivedData alone. Add device support files, simulators, and old Xcode archives, and that number climbs past 100 GB.

Node Modules and Package Manager Caches

If you do any JavaScript development, node_modules directories are likely scattered across your filesystem. Each npm install creates a fresh node_modules folder that can range from 200 MB to over 1 GB per project. On top of that, npm, Yarn, and pnpm all maintain global caches. A typical developer's npm cache alone can exceed 5 GB. Homebrew keeps downloaded formula archives. pip has its own cache. Docker stores image layers in ~/Library/Containers/com.docker.docker/ that routinely reach 20–40 GB.

iOS Device Backups

Every time you connect an iPhone or iPad to your Mac and back it up via Finder (or iTunes on older macOS), a full encrypted backup is stored in ~/Library/Application Support/MobileSync/Backup/. A modern iPhone backup is typically 5–20 GB. If you have been backing up for years, or have upgraded devices, you may have three or four old backups sitting there — representing 40–60 GB of data you will never need again.

Downloads Folder Sprawl

The Downloads folder is where files go to die. Installers for apps you set up three years ago, PDFs you meant to file, ZIP archives you extracted and forgot — it all sits there. The average Mac user's Downloads folder contains 8–15 GB of files, most of which have not been accessed in over a year.

Duplicate Files

Photos synced from iCloud then re-imported, documents emailed to yourself, screenshots renamed and copied — duplicates pile up across your entire filesystem. A duplicate finder using proper SHA-256 content hashing (not just filename matching) typically uncovers 3–10 GB of exact copies on a Mac that has been in use for two or more years.

System Logs and Crash Reports

macOS generates diagnostic logs continuously. System logs in /private/var/log/, unified logging data, crash reports, hang reports — they accumulate constantly. While individual log files are small, the aggregate over months adds up to several gigabytes. Crash reports for long-running apps like browsers, IDEs, and media apps can fill directories with hundreds of files.

Language Files and Unused Architectures

Most apps ship with support for dozens of languages — French, German, Japanese, Arabic — even if you only ever use English. These localization files are stored inside each app bundle. Similarly, universal binaries on Apple Silicon Macs sometimes retain Intel slices. Across all your installed apps, these unnecessary files can total 3–6 GB.

8 Categories to Clean on Your Mac Right Now

Here is a systematic, category-by-category walkthrough. Work through these in order — the early categories usually yield the most space the fastest.

1. Clear App Caches

App caches live in ~/Library/Caches/. To open this folder, press Command + Shift + G in Finder and type the path. Sort by size to identify the biggest offenders. You can safely delete the contents of most folders inside — the worst that happens is an app loads slightly slower on its next launch as it rebuilds its cache.

Be careful with a few exceptions: do not delete the CloudKit or com.apple.bird caches, as these are tied to iCloud sync state. And do not delete the Safari cache manually — use Safari's own Clear History command instead, which handles it properly.

2. Purge Your Downloads Folder

1. Open Finder and navigate to your Downloads folder.
2. Switch to List view (Command + 2) and click the Date Added column to sort oldest first.
3. Identify .dmg and .pkg installer files — these are almost always safe to delete after installation.
4. Look for ZIP archives whose contents you have already extracted.
5. Move anything older than 90 days that you cannot immediately identify to the Trash.
6. Empty the Trash when you are confident nothing useful is in it.

3. Find and Remove Duplicate Files

Manual duplicate hunting is impractical — there is no built-in macOS tool for it. You need a tool that computes file hashes and compares content, not just filenames. TrimyMac's Duplicate Finder uses SHA-256 hashing across your entire home directory and presents results grouped by duplicate set, sorted by wasted space, so you can recover the most room with the fewest decisions.

When reviewing duplicates, always keep the copy in the location that makes the most sense — your Photos library, your organized Documents folder — and delete the stray copies elsewhere.

4. Clean Xcode Artifacts

Xcode accumulated data is usually the single largest cleanup opportunity on a developer's Mac. Here are the key locations to address:

• DerivedData: ~/Library/Developer/Xcode/DerivedData/ — Safe to delete entirely. Xcode will rebuild as needed.
• Archives: ~/Library/Developer/Xcode/Archives/ — Delete archives for apps you no longer maintain or have already shipped.
• iOS Device Support: ~/Library/Developer/Xcode/iOS DeviceSupport/ — Delete support files for iOS versions you no longer test against.
• Simulators: Open Xcode → Window → Devices and Simulators → delete simulator runtimes for iOS versions you do not need.
• Xcode itself: If you have multiple Xcode versions, remove older ones from Applications.

5. Delete Old iOS Backups

1. Open Finder (macOS Catalina and later) or iTunes (older macOS).
2. Connect your device, then go to Finder → your device → Manage Backups.
3. Right-click any outdated backup and select Delete Backup.
4. Alternatively, navigate directly to ~/Library/Application Support/MobileSync/Backup/ and delete old backup folders. Each folder is named with a UUID — sort by Date Modified to identify old ones.

If you use iCloud Backup for your devices, you likely do not need local Mac backups at all. In that case you can safely delete all entries in the Manage Backups list.

6. Reclaim Developer Tool Caches

Beyond Xcode, the broader developer toolchain leaves significant debris:

• npm cache: Run npm cache clean --force in Terminal to clear the npm cache, which lives at ~/.npm/.
• Yarn cache: Run yarn cache clean.
• Homebrew cache: Run brew cleanup --prune=all to remove all outdated formula downloads from ~/Library/Caches/Homebrew/.
• Docker: Open Docker Desktop → Troubleshoot → Clean / Purge data, or run docker system prune -a to remove unused images, stopped containers, and build cache.
• Python pip: Run pip cache purge to clear pip's wheel cache.
• node_modules directories: Run find ~/projects -name "node_modules" -type d -prune to locate them, then delete those belonging to inactive projects.

7. Clear Browser Caches

Every major browser caches web content locally. These caches are meant to speed up browsing but left unchecked they balloon over time. Use each browser's built-in clearing tool rather than deleting files manually — this ensures the browser handles the cleanup correctly and does not enter a corrupted state:

• Safari: Safari menu → Clear History → All History. Or use Develop → Empty Caches (enable Develop menu in Safari settings).
• Chrome: Settings → Privacy and Security → Clear browsing data → Cached images and files → All time.
• Firefox: Settings → Privacy & Security → Cookies and Site Data → Clear Data → Cached Web Content.
• Arc: Command Palette → Clear Browsing Data.

8. Remove System Logs and Crash Reports

System logs are safe to delete — macOS will generate new ones as needed. The key locations are:

• ~/Library/Logs/ — User-level application logs
• /Library/Logs/ — System-level logs (requires admin password)
• ~/Library/Logs/DiagnosticReports/ — Crash and hang reports for your user account
• /Library/Logs/DiagnosticReports/ — System-wide crash reports

You can delete all files inside these directories. Sort by size first and focus on any file over 100 MB, which usually indicates a runaway logging process.

How TrimyMac Automates All of This

Working through all eight categories manually takes the better part of an afternoon. You need to know which paths are safe to delete, which apps have their own clearing commands, and which folders are system-critical versus user-generated debris. TrimyMac automates all of it in a single scan.

When you run a Smart Clean, TrimyMac simultaneously scans all nine junk categories:

• App caches in ~/Library/Caches/ and app containers
• User and system log files
• Xcode DerivedData, archives, and device support files
• iOS device backups via the MobileSync directory
• npm, Yarn, Homebrew, pip, and Docker caches
• Browser caches (Chrome, Firefox, Arc)
• Trash contents across all mounted volumes
• Duplicate files via SHA-256 content hashing
• Large forgotten files above a configurable threshold

The entire scan completes in under two minutes on a modern Mac. Results are presented sorted by size — so you immediately see where the biggest wins are — with each file or folder categorized and explained. You check what you want to remove, uncheck anything you want to keep, and click Clean. Everything goes to TrimyMac's Safe Area first, giving you a full recovery window before anything is permanently deleted.

For Pro users, scheduled auto-clean means you set it once and the Mac stays clean automatically. A weekly scheduled clean typically takes under 30 seconds after the first deep clean, since there is far less to process incrementally.

Tips for Keeping Your Mac Clean Ongoing

Freeing up space is satisfying, but the real goal is keeping your Mac consistently clean so you never hit that "disk full" wall again. These habits make a meaningful difference:

Run a Monthly Maintenance Clean

App caches rebuild within days of being cleared. Browser caches fill back up within weeks. A monthly quick clean with TrimyMac's Smart Clean (or a manual sweep of ~/Library/Caches/) prevents gradual accumulation from getting out of hand. On macOS with TrimyMac Pro, simply enable the monthly scheduled clean and forget about it.

Delete node_modules Before Archiving Projects

Before you move an old project to an archive drive or stop actively working on it, run rm -rf node_modules inside it. A project you are not touching does not need its dependency tree materialized on disk. When you come back to it, a fresh npm install restores everything in minutes.

Keep Your Downloads Folder Ruthlessly Lean

Treat Downloads as a temporary inbox, not permanent storage. Every time you download an installer or a document, move it where it belongs (Applications, Documents, a project folder) or delete it immediately after use. A weekly 60-second sweep of Downloads prevents the multi-gigabyte pileup.

Use iCloud Backup Instead of Local iPhone Backups

If you switch to iCloud Backup on your iOS devices, your Mac never accumulates local backup files. Go to Settings → Your Name → iCloud → iCloud Backup on your iPhone and enable it. Then delete any existing local backups via Finder. You get the same protection with far less Mac storage consumed.

Clean Xcode DerivedData After Major Projects

Get in the habit of clearing DerivedData whenever you finish a major feature or release. In Xcode, hold Option and go to Product → Clean Build Folder, or use TrimyMac's one-click Xcode cleanup. This prevents the folder from growing unbounded over the lifespan of a long-running project.

Monitor Storage Quarterly with a Full Analysis

Beyond routine cleaning, do a full Storage Analysis pass every three months. Open TrimyMac's Storage view and sort by size — this surfaces any new large directories that have snuck up on you, like a Docker image cache that ballooned after a new project, or a screen recording you forgot about in ~/Movies/.