# What Is ~/Library/Containers on Mac? App Data, Caches and Leftovers

> Identify the app behind a Library container, separate replaceable caches from personal data and check one controlled change before deleting more.

Published: 2026-05-13 | Updated: 2026-10-31

A large folder in `~/Library/Containers` is a reason to identify the app and its data, not a reason to delete the whole folder. A sandbox container can hold caches alongside settings, databases and documents, so the useful question is which child folder is large and whether its contents can actually be replaced.

## What Library Containers Holds

Apple's [App Sandbox documentation](https://developer.apple.com/documentation/security/accessing-files-from-the-macos-app-sandbox) explains that macOS creates a container in `~/Library/Containers` when a sandboxed app first launches. Think of it as that app's private home for local data, separate from its application bundle.

Inside a container, the part to inspect is often `Data/Library`. Apple's [file system guide](https://developer.apple.com/library/archive/documentation/FileManagement/Conceptual/FileSystemProgrammingGuide/FileSystemOverview/FileSystemOverview.html) distinguishes support data, preferences and caches. Their purpose matters more than the size of the parent folder.

| Location inside a container | What it is for | Cleanup decision |
| --- | --- | --- |
| Data/Library/Caches | Data the app should be able to recreate | Consider only identified, replaceable cache contents |
| Data/Library/Application Support | Supporting data, which can include databases | Keep unless deliberately removing that app's data |
| Data/Library/Preferences | App preferences | Keep during cache cleanup |
| Data/Documents | Documents kept by the app | Keep or export and back up first |

This is not `~/Library/Group Containers`. Shared App Group folders have a different ownership question, covered in [the Group Containers guide](https://mole.fit/blog/what-is-group-containers-mac).

## Open the Folder Without Changing It

In Finder, use **Go › Go to Folder** and paste this path, following Apple's [folder navigation instructions](https://support.apple.com/en-gb/guide/mac-help/mchlp1236/mac):

```text
~/Library/Containers
```

The `~` means your home folder. Inspect one container and its children, recording the exact location and size before changing anything. A folder you cannot read is unknown, not empty.

On macOS 14 and later, Apple's sandbox documentation describes permission requests when one app accesses another app's container. If access is denied, stop at that boundary rather than changing permissions or retrying with a deletion command.

## Match a Bundle Identifier to an App

A reverse-domain name is an identification clue, not an instruction to remove the folder. To check a likely installed app, inspect its bundle identifier rather than matching only the product's display name.

1. Find the suspected app in Finder and use the context menu to open its package contents, as Apple's [bundle guide](https://developer.apple.com/library/archive/documentation/CoreFoundation/Conceptual/CFBundles/AboutBundles/AboutBundles.html) describes.
2. Locate `Contents/Info.plist` and read it without editing.
3. Compare `CFBundleIdentifier` with the container name. Apple documents this key in its [property list reference](https://developer.apple.com/library/archive/documentation/General/Reference/InfoPlistKeyReference/Articles/CoreFoundationKeys.html).
4. If the name does not match, leave the container while checking the vendor's instructions. A helper or extension may have its own identifier.

Do not rename the container to make the names agree, and do not edit the app's property list. If a container has an opaque name or the owner remains uncertain, a guessed match is not enough to delete it.

## Work Out Why the Container Is Large

Compare the child folders before choosing an action. A large cache calls for a different decision from a large document store, even when both sit inside the same container.

If Caches dominates, first look for the app's own cache or storage controls. If Application Support or Documents dominates, look for downloads, attachments or retained documents in the app and remove only content you no longer need there.

Treat Mail, Messages, Notes and other personal-data apps as data stores, not a collection of disposable cache folders. Do not assume their containers contain all of their data, or that signing back into an account will recreate everything you removed.

For the general cache decision, use [which Mac caches are safe to delete](https://mole.fit/blog/which-mac-caches-are-safe-to-delete). Keep this inspection focused on the identified app rather than clearing unrelated Library folders.

## Make One Cache Change and Check It

Only proceed when the app's own documentation or controls establish that the selected cache can be rebuilt, and the required source files or downloads are still available. Apple's file system guide defines Caches as recreatable data, but a folder name does not prove that an app has stored everything correctly.

1. Quit the app and preserve a separate backup of any irreplaceable data.
2. Move only the identified cache child to the Trash, keeping its parent container and other data in place.
3. Reopen the app and test a real document or task, including anything needed offline.
4. Compare the same folder again, and keep the removed item until those checks pass.

Moving something to the Trash does not yet release its disk space. Apple's [deletion and recovery instructions](https://support.apple.com/en-nz/guide/mac-help/-mchlp1093/mac) explain how to return an item while it is still there. If the test fails, quit the app before restoring the original item, and do not overwrite newly created data without checking it.

A cache can grow again during normal use. If the rebuilt cache is immediately large, further clearing may only repeat the same work, so reconsider the app's retained content instead of broadening the deletion.

## Keep Whole Containers Unless Removing the App's Data

Removing an installed app's entire container removes its local home, so it can reset preferences and discard stored data rather than just clear cache. An empty replacement container does not recover the old databases or documents.

An uninstalled app's container may be leftover data, but absence of a familiar app name is not enough to establish that it is unused. Check the owner, any remaining helper or extension, and whether you want the data for a future reinstall before removing it.

Keep an independent backup or an app-supported export of wanted data. Account synchronization is not a separate backup, and reinstalling an app does not promise to restore local-only content. Trash recovery remains possible only while the removed item remains in the Trash.

## Where Mole Fits

Mole Mac's **Clean** can list eligible children of `Data/Library/Caches` inside app containers under **App Caches & Logs**. This lane requires Full Disk Access, applies cache safety and whitelist checks, and does not turn the whole Containers folder into a cache target.

The generic container-cache scan skips Mail, Messages and Notes containers, which also have protected paths in the deletion guard. App uninstall scanning can associate container remnants with a selected app, so review those as app data separately from cache cleanup. An unchecked row is left for your review, and selecting it does not preserve its contents.

## FAQ

### Can I Delete Everything in Library Containers?

No. The folder holds app data as well as caches. Identify one owner and one replaceable cache child instead of deleting the parent directory.

### Does Reinstalling the App Restore Its Container?

It may create a new local container, but that does not restore deleted settings, documents or local-only databases. Recovery needs an available backup, export or the original item still in the Trash.

### Why Does Mole Show Less Than the Container's Size?

An eligible cache child is smaller in scope than the whole container. Access permissions, cache safety and whitelist checks also affect what Clean can list, so its result is not a total of every app's stored data.

---

Canonical HTML page: https://mole.fit/blog/what-is-library-containers-mac
Blog index for agents: https://mole.fit/blog/llms.txt
Site index for agents: https://mole.fit/llms.txt