Every "free up space on a Mac" guide you find is written with a MacBook Air or MacBook Pro in mind. The Mac mini gets overlooked — yet it's the most popular entry point into Apple Silicon, and its 256GB base storage fills up faster than you'd expect on a machine that often doubles as a home server, media hub, or development workstation. Here's a desktop-specific guide to reclaiming space on a Mac mini without making rookie mistakes.
Why Mac Mini Storage Fills Up Fast
The Mac mini has no built-in screen, no internal battery, and — critically — no user-upgradeable storage. Whatever SSD you configured at purchase is what you have forever. On the 256GB model, macOS itself consumes roughly 15–20GB at installation, and System Data can quietly balloon to 30–60GB or more over time without you installing a single new app. Developers, photographers, and video editors hit the wall especially fast.
Unlike a MacBook, the Mac mini is often left running 24/7, accumulating crash logs, system diagnostics, and app caches that a laptop would shed through regular restarts and sleep cycles. It also tends to attract external drives, NAS shares, and Time Machine volumes — all of which generate their own metadata on the internal SSD.
Step One: See Where Your Space Actually Went
Before deleting anything, get an accurate picture. Apple's built-in view is a starting point but deliberately vague about what's inside each category.
- Open Apple menu → System Settings → General → Storage. Note the breakdown of System Data, Applications, and Documents.
- For a more granular view, open Finder → Go → Go to Folder and browse
~/Libraryand/Librarymanually — or use a disk map tool. - Crumb's Visualize tab renders a full disk map of your Mac mini and surfaces the largest directories and files in one view, including folders buried deep in
/Librarythat System Settings won't name explicitly.
Step Two: Clean System Data (The Biggest Win)
System Data is the catch-all bucket macOS uses for caches, logs, temp files, and purgeable space. On a Mac mini that's been running for months, this is almost always your largest recoverable category.
User Caches
Each app writes its own cache to ~/Library/Caches/. These are generally safe to delete — apps rebuild them on next launch. The risk is a slightly slower first launch and, in rare cases, signed-out sessions in apps that store auth tokens in their cache folder (check before you delete).
# List the largest per-app cache folders
du -sh ~/Library/Caches/* 2>/dev/null | sort -rh | head -20
System-Level Caches and Logs
System caches live in /Library/Caches/ (all users) and logs accumulate in /Library/Logs/ and ~/Library/Logs/. Diagnostic reports pile up in ~/Library/Logs/DiagnosticReports/ and are safe to delete.
# View size of system log directory (read-only — don't delete blindly)
du -sh /Library/Logs/
Caution: Do not touch /private/var/db/, /System/, or anything inside /Library/Application Support/ without understanding what it is. Deleting the wrong Support folder can break the associated app or, in edge cases, require a reinstall of macOS.
One-Click Option
Download Crumb and use its Clean tab to sweep user caches, system logs, temp files, and purgeable space in one pass. It shows you exactly what it's about to remove before it does anything, and the free tier covers one full cleanup so you can verify the results before committing.
Step Three: Remove App Leftovers
Dragging an app to the Trash removes the .app bundle but leaves behind support files, preferences, caches, and sometimes gigabytes of offline data scattered across your Library folders. On a 256GB Mac mini this waste compounds quickly.
- Think of apps you've uninstalled in the past year — Xcode, Docker, Adobe apps, Unity, Parallels, and games are notorious for large leftovers.
- Check
~/Library/Application Support/for folders whose parent app no longer exists on your Mac. - Check
~/Library/Containers/and~/Library/Group Containers/for sandboxed app data. - Use Crumb's Uninstall tab to find and remove both the app and its associated leftover files in one step, rather than hunting through Library folders manually.
# Quick check for large orphaned support folders
du -sh ~/Library/Application\ Support/* 2>/dev/null | sort -rh | head -20
Step Four: Manage Developer Tools and Derived Data
If you do any development on your Mac mini — which is common given the machine's role as a quiet, always-on desktop — Xcode's Derived Data folder alone can consume 20–50GB.
# Check Xcode Derived Data size
du -sh ~/Library/Developer/Xcode/DerivedData/
# Delete it (Xcode rebuilds on next build — expect a longer compile)
rm -rf ~/Library/Developer/Xcode/DerivedData/*
Also check:
~/Library/Developer/CoreSimulator/Devices/— iOS Simulator images; each simulated device can be 5–10GB~/.gradle/caches/and~/.m2/repository/for Java/Kotlin build caches~/.npm/,~/.pnpm-store/,~/.yarn/cache/for Node package caches~/Library/Containers/com.docker.docker/— Docker's disk image, which grows unboundedly
# Remove old iOS Simulators from the command line
xcrun simctl delete unavailable
Step Five: Offload Media and Large Files
The Mac mini's desktop context means it's often attached to external storage already. Use that to your advantage.
- Move large video projects, raw photo libraries, and VM disk images to an external SSD or NAS.
- Enable iCloud Drive → Optimize Mac Storage in System Settings if you rely heavily on iCloud — macOS will evict local copies of files not recently opened.
- Use Finder → View → Show Status Bar to see a folder's size before moving it.
What not to do: Do not move your home folder to an external drive without understanding APFS ownership semantics. Some apps break when their sandboxed data is on a different volume than the system volume.
Storage Comparison: 256GB vs 512GB Mac Mini
| Use Case | 256GB Realistic Free After macOS + Apps | 512GB Realistic Free After macOS + Apps |
|---|---|---|
| Light productivity (browser, office) | ~200GB — comfortable | ~460GB — no issues |
| Developer (Xcode, Docker, Node) | ~100GB — tight within 6 months | ~320GB — manageable |
| Video/photo editing | ~80GB — will fill fast | ~300GB — plan for external storage |
| Home server / VM host | Often insufficient at purchase | ~200GB — depends on VM count |
Step Six: Prevent Storage Creep Long-Term
Freeing space is a one-time win. Keeping it free requires a light habit:
- Clear
~/Downloads/monthly — it's the fastest-growing folder for most users. - Empty the Trash (right-click the Dock icon → Empty Trash) — files you've deleted still consume space until the Trash is emptied.
- After major app installs or updates, let macOS reclaim purgeable space by restarting — or trigger it manually via a cleanup tool.
- If you run Time Machine to a local external drive, check that it's not consuming space on the internal SSD via APFS snapshots:
tmutil listlocalsnapshotdates /and delete old ones withtmutil deletelocalsnapshots <date>.
What's Actually Safe to Delete vs. What Isn't
- Safe:
~/Library/Caches/*,~/Library/Logs/*,~/Library/Logs/DiagnosticReports/*, Xcode DerivedData, Simulator devices marked unavailable,~/Downloads/contents you've reviewed, Trash - Risky without research:
~/Library/Application Support/subfolders,~/Library/Containers/, anything in/Library/(system-wide) - Never delete:
/System/,/private/var/db/,/Library/StagedExtensions/, anything in/Volumes/that is a mounted disk image, Time Machine backup data you haven't verified elsewhere
When you're unsure about a specific folder, macOS doesn't offer a built-in explanation. Crumb's "Is this safe to delete?" AI feature lets you select any folder and get a plain-language explanation of what it contains and the risk level of removing it — useful when you find a mystery 4GB folder in Application Support and aren't sure if you still need it.
Conclusion
Mac mini storage filling up is a predictable problem, not a sign you bought the wrong machine — but it does require more active management than a MacBook with cloud offload or expandable external storage built into the workflow. Start with System Data (caches and logs), clear app leftovers from old uninstalls, and evict developer build artifacts. On a 256GB model especially, cleaning up 20–40GB is realistic without touching a single file you actually care about. The key is knowing exactly what you're deleting before you delete it — because on a non-upgradeable SSD, you can't undo a mistake by buying more storage.