If you've ever looked at your Mac's disk usage and spotted a swollen ~/Library folder, you've probably asked yourself: can I delete the Library folder on my Mac? The short answer is no — not the folder itself — but plenty of what lives inside it is fair game. The trick is knowing which subfolders are safe to touch and which ones will break your apps or corrupt your user account if you delete them.
What Is the Library Folder on a Mac?
Your Mac actually has three Library folders, and they serve different purposes:
~/Library— your user Library, hidden by default. Stores preferences, caches, app support data, and saved states for your account only./Library— the system-wide Library at the root of your drive. Holds resources shared across all users: fonts, extensions, launch agents, and more./System/Library— owned by macOS itself. Do not touch this. It contains the core operating system components.
When people ask about deleting the Library folder on a Mac, they almost always mean ~/Library — the one tied to their user account. That's what we'll focus on here.
Why You Should Never Delete ~/Library Wholesale
Deleting ~/Library entirely would be the Mac equivalent of pulling the fuse box out of a running car. Your system would not immediately crash, but the next time you logged in — or even rebooted — macOS would have nowhere to write preferences, app data, or authentication tokens. Most apps would lose all their settings. Some would refuse to launch. Keychain access, Safari history, Mail accounts, and iCloud state are all stored inside ~/Library. Recovering from a full deletion typically means restoring from a Time Machine backup.
So the folder itself stays. What you're really asking is: which parts of it can I safely clear?
Library Subfolders: Safe vs. Risky at a Glance
| Subfolder | What it stores | Safe to delete contents? |
|---|---|---|
~/Library/Caches |
App cache files — thumbnails, downloaded data, compiled assets | Yes — apps rebuild caches on next launch |
~/Library/Logs |
Diagnostic and crash logs written by apps | Yes — logs are not needed for normal operation |
~/Library/Application Support |
App databases, saved data, configuration files | Selective — deleting an app's subfolder removes its saved data |
~/Library/Preferences |
.plist files that store every app's settings |
Selective — deleting a .plist resets that app to defaults |
~/Library/Containers |
Sandboxed app data (App Store apps) | Risky — contains documents and data, not just caches |
~/Library/Keychains |
Passwords, certificates, encryption keys | No — you will lose saved passwords |
~/Library/Mail |
All locally stored email messages | No — permanent loss of offline mail |
~/Library/Safari |
Bookmarks, history, local storage | No — wipes your browsing data irreversibly |
The Subfolders That Are Genuinely Safe to Clear
~/Library/Caches
This is the biggest legitimate source of recoverable space. Apps write temporary data here — Xcode build artifacts, browser cache, Spotlight indexes, thumbnail databases — and none of it is essential. Deleting the contents (not the folder itself) is safe. Apps will recreate their cache folders the next time they run, though some apps like Xcode or browsers may feel slower on first launch as they rebuild.
To clear a single app's cache from Terminal:
rm -rf ~/Library/Caches/com.example.AppNameTo see which apps are using the most cache space:
du -sh ~/Library/Caches/* | sort -rh | head -20~/Library/Logs
Log files accumulate over time and can reach several gigabytes on a machine that has been running for years. They are written for debugging purposes and have no effect on app behavior once you delete them. Clearing this folder is safe at any time.
rm -rf ~/Library/Logs/*Subfolders That Require Care
~/Library/Application Support
This folder is different from Caches. It holds data that apps consider persistent — game saves, local databases, offline content. Deleting a subfolder here for an app you have already uninstalled is perfectly fine. Deleting one for an app you are still using means losing that app's saved state permanently. There is no undo once you empty the Trash.
~/Library/Preferences
Each .plist file here stores one app's settings. If Photoshop is misbehaving, deleting ~/Library/Preferences/com.adobe.Photoshop.plist resets it to factory defaults — a common troubleshooting step. But bulk-deleting Preferences will reset every app on your Mac simultaneously, which is rarely what you want.
How to Safely Access ~/Library
Apple hides ~/Library by default to protect users from accidental deletion. To open it in Finder:
- Open Finder and click Go in the menu bar.
- Hold the Option key — Library will appear in the dropdown.
- Click Library.
Alternatively, use Terminal:
open ~/LibraryWhen You Uninstall an App, Library Leftovers Remain
Dragging an app to the Trash removes the app bundle but leaves behind everything it ever wrote to ~/Library — caches, preferences, support files, container data. Over time these orphaned files can add up to gigabytes. Identifying them manually means cross-referencing bundle identifiers across three or four Library subfolders, which is tedious and error-prone.
Crumb handles this automatically. Its Uninstall tab finds an app's leftover files across all the relevant Library locations and shows you exactly what will be removed before anything is deleted — so you can confirm the list rather than guess. If you're ever unsure whether a specific subfolder belongs to something you still need, Crumb's Is this safe to delete? feature explains any folder's purpose and flags the risk level in plain language.
What About /Library and /System/Library?
Leave /System/Library entirely alone. It is protected by System Integrity Protection (SIP) on macOS 10.11 and later, and macOS 15 Sequoia extends further protections to core system directories. Even with SIP disabled, modifying files here can prevent your Mac from booting.
/Library (the root-level one) contains launch agents, login items, fonts, and resources shared across all user accounts. Some legitimate cleanup happens here — removing launch agents from apps you've uninstalled, for instance — but it should be done one item at a time, not swept in bulk.
A Safer Approach Than Manual Deletion
If your goal is recovering disk space rather than troubleshooting a specific app, the most reliable approach is:
- Clear
~/Library/Cachesand~/Library/Logs— these are safe and often yield the most space. - Uninstall apps you no longer use, and remove their Library remnants at the same time.
- Check
~/Library/Application Supportfor folders belonging to apps you've already removed. - Let macOS manage purgeable space on its own — it does a reasonable job with APFS.
If you want to see exactly what is taking up space before touching anything, download Crumb and use its Visualize tab to get a disk map of your entire drive, including the Library folders, with size breakdowns you can drill into.
The Bottom Line
You cannot and should not delete ~/Library as a whole — but a handful of its subfolders, particularly Caches and Logs, are safe to clear at any time. Everything else requires knowing what each folder contains before you act. When in doubt, look it up, read what the folder does, and delete only what you can confidently identify. Cleaning is permanent, and a backup before any significant Library work is always a good idea.