What's safe to delete in the Mac Library folder
You've opened Mac storage settings, seen a suspiciously large System Data number, and gone looking for the culprit. Sooner or later the trail leads to the Library folder — a hidden collection of folders that sit quietly in the background while your Mac and your apps do their work.
The problem? Some of it is genuinely safe to delete. Some of it looks like junk but is actually important app data. Delete the wrong thing and you could lose Messages history, Notes content, or settings you've spent years tweaking.
This guide breaks the Mac Library folder into three clear buckets: safe to clear, be careful, and leave alone — so you know exactly what you're touching before you move anything to the Trash.
First: which Library folder are we talking about?
Your Mac actually has multiple Library folders, and this matters a lot.
- ~/Library — This is your personal Library folder, tucked inside your home folder (the tilde ~ is shorthand for your home folder). This is the one we're discussing in this article. It contains data and settings for the apps you use.
- /Library — A system-wide Library at the root of your Mac's hard drive. Apps that all users share store things here. Generally, leave it alone unless you know exactly what you're doing.
- /System/Library — This one is part of macOS itself. Never touch it. macOS protects it with System Integrity Protection for good reason.
How to open ~/Library (the hidden one)
Apple hides ~/Library in Finder because accidentally deleting something inside it can break apps. You can still get there two ways:
- Open Finder → click the Go menu in the menu bar → hold the Option key → you'll see Library appear in the list → click it.
- Or: Go menu → Go to Folder → type
~/Library→ press Enter.
Once you're in, you'll see dozens of folders. Here's what each of the important ones actually means.
Safe to clear: Caches and Logs
These two folders are the classic safe win when you want to free up space without risking anything important.
~/Library/Caches
A cache is a shortcut file. When you use an app — say, a web browser or a video editor — it saves temporary files so it can do certain things faster next time. Think of it like a chef pre-chopping vegetables: it saves time, but the vegetables are still in the fridge if the mise en place goes bad.
The key thing to understand: apps rebuild their caches automatically. If you delete them, the app might open a tiny bit slower the next time, and then it creates new cache files. You lose nothing permanent.
Inside ~/Library/Caches you'll find folders named after apps and services — things like com.apple.Safari, com.spotify.client, or Slack. These can easily run into several gigabytes for apps you use heavily.
How to clear caches safely:
- Quit the app whose cache you want to clear (important — deleting files an app is actively using can cause errors).
- Navigate to ~/Library/Caches.
- Open the folder for the app you want to clear and delete the contents (not the folder itself, just what's inside).
- Empty the Trash to actually reclaim the space.
For a more detailed walkthrough of this process, see our guide on how to clear caches safely on Mac.
~/Library/Logs
Logs are text records of what apps have been doing — errors encountered, tasks completed, crashes recorded. They're essentially a diary that apps write to themselves.
Logs are useful for developers debugging problems. For most people, most of the time, they're just taking up space. They don't affect how your apps run, and apps create new log files as needed.
Clearing ~/Library/Logs is safe. You can delete the contents of folders inside it freely. The only reason to keep a log is if you're actively troubleshooting a crash and need to read what happened — in that case, read it first, then delete.
Be careful: Containers, Group Containers, and Application Support
These folders look similar to Caches — they're named after apps, they can be large — but they contain real data, not just temporary shortcuts. Treat them with respect.
~/Library/Containers
A Container is a private, walled-off storage area that macOS gives to each sandboxed app. "Sandboxed" means the app is only allowed to read and write to certain approved locations — this is a security feature Apple introduced to protect your Mac.
Apps from the Mac App Store — including Apple's own apps like Messages, Notes, Reminders, and many third-party apps — store their actual data inside their Container. This includes:
- Your Messages chat history
- Your Notes content
- Saved state, preferences, and documents for those apps
If you delete a Container folder, you can delete all of that app's data. This is not like clearing a cache. There is no automatic rebuild. The data is gone.
The only time it's appropriate to delete a Container is when you have completely uninstalled the app it belongs to and you're certain you no longer need anything that app stored. Even then, move it to the Trash and wait a few days before emptying, just to be sure.
~/Library/Group Containers
Similar to Containers, but shared between a group of related apps — for example, apps that are part of the same developer's suite and need to share data with each other. The same rule applies: treat these as real data, not junk. Don't delete unless you've fully uninstalled every app that uses that group container.
~/Library/Application Support
This folder is a mixed bag. It holds support files, plugins, saved states, databases, and all sorts of things apps need to function. Some of it is truly important (saved game data, email databases, app-specific libraries). Some of it is leftover clutter from apps you deleted years ago.
The danger with Application Support is bulk-deleting. Don't open it and select everything. Instead:
- Look for folders named after apps you no longer have installed.
- If you recognise the app and you're sure you don't use it anymore, the folder is probably safe to remove.
- If you don't recognise the folder name, leave it alone.
Leave alone entirely
Some parts of your Mac's Library system are genuinely off-limits for manual cleanup:
- /Library and /System/Library — The system-wide Libraries. These contain files macOS needs to run. Even removing a single file from /System/Library can break macOS.
- ~/Library/Preferences — These
.plistfiles store your app settings (keyboard shortcuts, window positions, saved logins). Deleting them resets apps to factory settings. Only touch these if you're deliberately resetting a specific app. - Anything you don't recognise — If you don't know what a folder is for, don't delete it. The risk isn't worth the potential space saving.
Why does the Library folder show up under "System Data"?
If you go to System Settings → General → Storage on your Mac, you'll see a breakdown of what's using space. Caches, logs, and app support files in ~/Library often land under the category called System Data — a catch-all label macOS uses for files that don't fit neatly into another category.
This is why System Data can look alarmingly large. It's not all system files you need — a big chunk of it is often caches and logs that are completely safe to clear. We have a full explanation of what System Data on Mac actually contains if you want to dig deeper.
The safer way: let Storage Bee handle the Library scan
Manually navigating hidden Library folders is tedious and easy to get wrong. You have to know what each folder does, quit the right apps beforehand, and be careful not to delete anything important — all while looking at a list of cryptic folder names like com.apple.bird or io.nspanel.NsPanel.
Storage Bee is a Mac storage management app that does this scanning work for you. It reads the same Library locations described in this article — Caches, Logs, Application Support, Containers — and labels each item clearly:
- Safe to delete — rebuilt automatically, no data loss risk
- Check first — real data that may be from apps you no longer use
- Keep — important system or app files
When you choose to remove something, Storage Bee sends it to the Trash (not permanent deletion), so you can undo if anything seems wrong. It's much harder to make a mistake than when you're clicking through hidden folders by hand.
Storage Bee scans Caches, Logs, and Application Support, labels each item, and sends removals to the Trash — so you can reclaim space without risking your data.
⬇︎ Download Storage BeeQuick summary: safe / be careful / leave alone
| Folder | What's inside | Verdict |
|---|---|---|
~/Library/Caches |
Temporary shortcut files; rebuilt automatically | ✅ Safe to clear |
~/Library/Logs |
Text records of app activity | ✅ Safe to clear |
~/Library/Application Support |
Mixed: real data + leftover app folders | ⚠️ Be careful — remove only known, uninstalled apps |
~/Library/Containers |
Actual data for sandboxed apps (Messages, Notes, etc.) | ⚠️ Be careful — only remove for fully uninstalled apps |
~/Library/Group Containers |
Shared data between related apps | ⚠️ Be careful — same rule as Containers |
~/Library/Preferences |
App settings files | 🚫 Leave alone |
/Library and /System/Library |
System-wide files, macOS internals | 🚫 Leave alone |
Frequently asked questions
Is it safe to delete everything in ~/Library/Caches?
Yes, deleting the contents of ~/Library/Caches is generally safe. Apps create these files automatically to load faster, and they will rebuild them the next time you use the app. The one rule: quit any app before deleting its cache folder. If Spotify is running when you delete its cache, for example, it may throw an error. Quit it first, delete the cache, then reopen. The app picks up right where it left off — it just has to rebuild the shortcut files over time.
What happens if I delete a folder inside ~/Library/Containers?
Deleting a Container folder can permanently erase that app's data — including saved messages, notes, documents, or anything else that app stored inside its Container. This is not a cache. The app cannot rebuild it from scratch. The only safe time to delete a Container is when you have fully uninstalled the app it belongs to and you're absolutely certain you no longer need its data. Even then, move it to the Trash and leave it there for a week before emptying, just in case.
Why is my Mac Library folder hidden?
Apple hides ~/Library in Finder to protect you from accidental deletion of important app data and settings. The contents of this folder keep your apps working correctly, store your personal app data, and maintain your preferences. Most users never need to go there manually, and hiding it reduces the risk of someone accidentally wiping something important while tidying up. You can always access it via the Go menu in Finder — hold the Option key to reveal the Library option — or by typing ~/Library in Go to Folder.
Why does Library content show up under System Data in Mac storage settings?
macOS groups files that Finder cannot easily categorise — including caches, logs, and app support data inside ~/Library — under the "System Data" label in System Settings → Storage. This catch-all category is why the number can look surprisingly large. Gigabytes of perfectly safe-to-delete caches and logs often hide inside it. Clearing caches and logs from ~/Library reduces the System Data figure over time. See our full breakdown of what System Data on Mac actually is for more detail.