What Is ~/Library/Containers on Mac, and Can You Delete It?

~/Library/Containers is not a cache folder, and that single fact settles most of the question. It holds the data of sandboxed apps: their settings, their databases, the media they downloaded. Deleting the container of an app you still use resets that app and takes its data with it. Deleting the container of an app you removed last year frees space and costs you nothing.

Quick answer

What a container is

macOS runs sandboxed apps inside a restricted home folder of their own. Every App Store app works this way, and so do many apps distributed outside it. That private home folder is the container.

Open one and the structure looks familiar:

~/Library/Containers/com.apple.Safari/
  Data/
    Library/
      Application Support/
      Caches/
      Preferences/
    Documents/
    Desktop/       -> symlink to your real Desktop
    Downloads/     -> symlink to your real Downloads

The app sees Data as its home directory. Inside it, Library holds what belongs to the app alone. The Desktop and Documents entries are symbolic links pointing at your real folders, which the app can only follow when it has permission to.

That detail answers the question people worry about most: removing a container removes the links, not the files they point to. Your documents stay where they always were.

What you lose when you delete one

The app-specific part is real data.

• account setup and sign-in state for that app;
• its settings and window state;
• the database it built, such as a mail index or a message history;
• media it downloaded and filed inside its own storage.

An app that finds its container missing starts as if freshly installed. For a note-taking app that syncs from a server, that costs you a re-download. For an app that kept everything locally, that costs you the content.

Which containers are safe to remove

The safe ones belong to apps that no longer exist on your Mac.

du -sh ~/Library/Containers/* | sort -h | tail -20

Take each large folder and read its name. com.company.appname tells you the vendor and the app. Then check whether that app is still in /Applications. When it is not, the folder is a leftover: an app was removed, its container stayed. Move it to Trash.

When the app is still installed, leave the container in place and deal with the size from inside the app. Messaging clients, mail clients, and browsers all expose settings for stored media and cache, and using them keeps your account setup intact.

Group Containers work differently

~/Library/Group Containers holds storage shared between components that declare the same app group: an app and its extension, an app and its widget, a suite and its helper. One folder can back several visible pieces of software.

The same rule applies, with a wider blast radius. Removing a group container for software you no longer have is fine. Removing one that a current app shares with its extension breaks the shared state for both, and the app usually cannot tell you why.

What lives in the biggest containers

A handful of names show up in almost every list.

• Messaging apps. Received photos and video pile up inside the container. Most of these apps have a storage screen that lets you clear old media without touching the account.
• Mail. Copies of downloaded attachments live in its container and grow quietly for years.
• Safari. Its cache sits inside com.apple.Safari rather than in ~/Library/Caches, which is why the browser looks absent from the cache listing.
• Apps you tried once. Small folders, dozens of them, from software that has been gone for years. Individually irrelevant, collectively a tidy few hundred megabytes.

The order that keeps you out of trouble

1. Sort the containers by size and look only at the top of the list.
2. For each one, decide whether the app is still installed.
3. Quit the app if it is running.
4. Move only the orphan containers to Trash.
5. Use the Mac for a day, then empty the Trash.
6. For apps you keep, open their own settings and clear stored media from there.

Step 2 is the whole job. A container is worth removing when nothing is behind it, and worth keeping when something is.

Bottom line

Treat ~/Library/Containers as app data, because that is what it is. The question is never “is it safe to delete containers” in general. It is whether a specific container still has an app behind it. When the answer is no, move it to Trash. When the answer is yes, go into the app and clear what it stored, and leave its container where macOS put it.