If you've been poking around Finder's hidden folders, you've probably stumbled across ~/Library and wondered: is it safe to delete the Library folder on Mac? The short answer is no — not the whole folder. But several subfolders inside it are fair game, and trimming them is one of the most effective ways to reclaim gigabytes on macOS. This guide breaks down every major subfolder with a plain-language verdict so you know exactly what you're touching before you delete anything.
What Is the ~/Library Folder on Mac?
macOS has two Library folders that matter to most users:
~/Library— your personal (user) Library, hidden by default in Finder. Stores per-user data for every app you've ever run./Library— the system-wide Library at the root of your drive. Applies to all users and system services.
This article focuses on ~/Library (the tilde means your home folder, e.g. /Users/yourname/Library). Apple hides it intentionally because deleting the wrong thing can instantly corrupt app data, break preferences, or force you to reconfigure tools you've spent years setting up.
To reveal it in Finder: hold Option, click the Go menu, and choose Library. Or open Terminal and run:
open ~/LibraryFolder-by-Folder Breakdown: What's Safe to Delete?
Here is the honest verdict for each major subfolder.
~/Library/Caches
What's inside: Temporary files apps write to speed up future operations — rebuilt thumbnails, downloaded resources, compiled data. Each app gets its own subfolder, typically named by bundle ID (e.g. ~/Library/Caches/com.apple.Music).
Verdict: Generally safe to delete. Apps regenerate their own cache as needed. You will not lose documents, settings, or purchases. The downside is a temporary slowdown while apps rebuild. Some apps (notably Xcode's derived data and simulator caches) store gigabytes here.
Safe manual approach — delete the contents of a specific app's cache folder, not the Caches folder itself:
rm -rf ~/Library/Caches/com.spotify.client/*Deleting the parent ~/Library/Caches folder entirely is usually fine too, since macOS recreates it, but it's cleaner to target individual subfolders.
~/Library/Logs
What's inside: Text-based diagnostic logs from apps and system services. Useful for debugging crashes; useless once you no longer care about a past issue.
Verdict: Safe to delete. No functionality is harmed. Logs regenerate. They rarely exceed a few hundred MB, but can grow large on systems running server software or development tools.
~/Library/Application Support
What's inside: Persistent app data that is not your documents — game saves, app databases, plugin libraries, license files, AI model weights. Examples: ~/Library/Application Support/Slack/, ~/Library/Application Support/Steam/.
Verdict: Do NOT delete wholesale. Target with extreme care. Deleting an app's Application Support folder typically means losing all its data — save files, offline content, account sessions. You can safely remove the subfolder of an app you've already uninstalled, but only after confirming you don't need that data.
~/Library/Preferences
What's inside: Property list (.plist) files that store every app's settings — window positions, toolbar layout, custom keybindings, feature flags. For example, ~/Library/Preferences/com.apple.finder.plist controls Finder behavior.
Verdict: Do NOT delete as a folder. Deleting all preferences resets every app on your Mac to factory defaults in a single stroke. You can delete the .plist for one specific app to reset it, but even that should be done deliberately.
~/Library/Containers
What's inside: Sandboxed data for App Store apps. Each app gets an isolated container that mimics a mini home directory. Mail, Messages, and Calendar store important data here.
Verdict: Do NOT delete wholesale. The caches nested inside individual containers (e.g. ~/Library/Containers/com.apple.mail/Data/Library/Caches/) are safe to clear. The container itself is not.
~/Library/Saved Application State
What's inside: Window snapshots that macOS uses to restore apps to their previous state after a quit/relaunch. Controlled by the "Restore windows when quitting and re-opening apps" system setting.
Verdict: Safe to delete. Apps simply won't restore their last window state after the next launch. The folder is usually small (under 100 MB) but can hold stale data from apps you've long since removed.
rm -rf ~/Library/Saved\ Application\ State/*~/Library/Mail and ~/Library/Messages
What's inside: Your actual email database and iMessage history, respectively.
Verdict: Never delete unless you have a verified backup and know exactly what you're doing. These are irreplaceable personal data stores.
Quick-Reference Table
| Subfolder | What It Holds | Safe to Delete? | Regenerates? |
|---|---|---|---|
~/Library/Caches |
Temporary app caches | Yes (contents) | Yes |
~/Library/Logs |
Diagnostic logs | Yes | Yes |
~/Library/Application Support |
Persistent app data | Per-app only, carefully | No |
~/Library/Preferences |
App settings (.plist) | One app at a time only | Defaults only |
~/Library/Containers |
Sandboxed App Store data | Nested caches only | Partially |
~/Library/Saved Application State |
Window restore snapshots | Yes | Yes (new entries) |
~/Library/Mail |
Email database | No | No |
~/Library/Messages |
iMessage history | No | No |
Why You Should Never Delete the Whole ~/Library Folder
The question "is it safe to delete the Library folder on Mac" comes up often because the folder can easily occupy 10–30 GB on an active machine. But nuking the entire ~/Library in one go would simultaneously wipe your preferences, app databases, saved passwords (Keychain data lives in ~/Library/Keychains), Mail, and sandboxed app data. macOS would rebuild a skeleton Library on next login, but your apps would behave as if freshly installed — losing years of customization and, in some cases, unrecoverable data.
The rule: never delete a folder you haven't inspected. Delete contents, not containers; and only after you understand what's inside.
How to Safely Reclaim Space in ~/Library
- Identify the biggest subfolders first. In Terminal, sort by size:
du -sh ~/Library/*/ | sort -rh | head -20 - Inspect before deleting. Open any suspicious folder in Finder and read the subfolder names — they're almost always named after the app that owns them.
- Clear caches for specific apps rather than the whole Caches directory if you want to be precise.
- Remove Application Support folders only for apps you've already uninstalled. Leftover support folders are pure dead weight.
- Restart after cleaning so macOS can rebuild any in-memory references to the deleted files.
When You're Not Sure: Ask Before You Delete
If you're staring at a folder name like ~/Library/Application Support/com.elpass.Elpass and have no idea whether it's safe to remove, that uncertainty is exactly what Crumb's "Is this safe to delete?" feature is built for. Point it at any subfolder and it explains what the folder belongs to, what data it stores, and what the risk level is before you take any action — so you're making an informed choice rather than guessing.
Crumb also handles the mechanical side: its one-click Clean pass targets user caches, logs, and purgeable system data — the folders that are safe to wipe — without touching Preferences, Application Support, or Mail. If you want to go deeper and remove leftover support folders from uninstalled apps, the Uninstall tab surfaces those orphaned entries automatically. Download Crumb if you'd rather not run Terminal commands for routine maintenance.
Conclusion
The ~/Library folder is not a junk drawer you can empty in one move. It's the operating layer beneath every app on your Mac. The caches and logs inside it are genuinely safe to trim and will hand you back meaningful disk space. Preferences, Application Support, and anything with "Mail" or "Messages" in the name are not. Spend two minutes with du or a disk visualizer to understand what's eating space, delete surgically, and you'll keep your Mac both lean and stable.