SiftMac
Is it safe to delete? · Library and system · Updated 21 November 2026

Can I delete ~/Library/Containers on a Mac?

By Mohit Nippanikar, who makes SiftMac

The short answer
On this page
  1. What it is
  2. Where it is
  3. How big it gets
  4. How to remove a container safely
  5. What happens afterwards
  6. Questions

1. What it is

Apps from the App Store, and other apps that use Apple’s App Sandbox, can’t write wherever they like. The first time such an app opens, macOS creates a container for it in ~/Library/Containers and gives the app full access to that folder, with only limited access elsewhere.

Each container has a Data folder laid out like a small home folder, with its own Library/Preferences, Library/Caches and Library/Application Support. Some items in it are links back to folders in your real home folder, so not everything you see inside is stored there.

Since macOS 14, macOS ties each container to its app’s code signature. When another app tries to read inside it, macOS asks you first, which is why Terminal or a disk tool can trigger a permission prompt here.

2. Where it is

~/Library/Containers/<app ID>

In Finder, choose Go › Go to Folder and type ~/Library/Containers. Finder often shows a container under its app’s name rather than its folder name, which is why Microsoft’s Office removal steps list folders like “Microsoft Excel”; Terminal shows the app ID, com.microsoft.Excel.

Two neighbours work differently: ~/Library/Daemon Containers is for sandboxed background services, and ~/Library/Group Containers holds data a family of apps shares.

3. How big it gets

Terminal needs Full Disk Access to measure these (System Settings › Privacy & Security › Full Disk Access), and macOS may still ask about some. Then:

du -sh ~/Library/Containers/* 2>/dev/null | sort -h | tail -10

A big container usually has a cause you can deal with inside the app. Docker Desktop keeps its whole disk image in com.docker.docker (how to shrink it), and Mail keeps copies of attachments you’ve opened in com.apple.mail (Mail Downloads).

4. How to remove a container safely

For an app you use, free space from inside the app rather than deleting its container: remove downloads, old projects or offline content in its settings, and for Docker, use docker system prune instead of touching its files.

For an app you’ve removed:

  1. Make sure the app is really gone: not in Applications, not in ~/Applications, and not about to be reinstalled from the App Store.
  2. Open its container in Finder and look in Data/Documents and Data/Library/Application Support for anything of yours, such as exports or saved files. Copy out what you want to keep.
  3. Move the container to the Trash; macOS may ask for permission first. Empty the Trash when you’re sure.

If the app has an uninstaller or its maker publishes removal steps, follow those instead: they name the exact folders. Leave the Containers folder itself alone, and Apple’s own com.apple.… containers, such as Mail’s.

5. What happens afterwards

Questions

Can I delete containers on a Mac?

Only containers of apps you’ve already removed, after checking they hold nothing of yours. Leave the Containers folder itself, and the containers of apps you use, alone: each one is that app’s data.

Does deleting an app remove its container?

No. macOS has no step that removes a container when its app goes, so containers of deleted apps stay until you remove them. An app’s own uninstaller may take care of it.

Why does macOS ask for permission when I open a container?

Since macOS 14, containers are tied to their apps, and any other app, Terminal included, has to be allowed before it reaches inside. Allow it if you started the action yourself.

Is Containers the same as Group Containers?

No. A container belongs to one app. A group container holds data shared between apps, or between an app and its extensions, from the same developer.

How SiftMac handles it. The space map shows ~/Library/Containers as private: it doesn’t read inside, and its note says macOS guards these. SiftMac never deletes a container, even when it removes an app; from inside containers it lists only Mail’s copies of attachments you opened, which wait on the Undo Shelf, and it explains Docker Desktop’s disk image, which it leaves to Docker’s own commands.

Download SiftMac · scanning is free, and so is your first 2 GB of cleaning · See how it works