~/Library/Containers and ~/Library/Group Containers hold apps' own data, one folder per app. They get huge when one app caches without limits. On my Mac, Group Containers was 39 GB and Telegram alone was 35 GB, almost all of it a media cache. Find the culprit with du, then clear the space inside that app (for Telegram: Settings › Data and Storage › Storage Usage). Don't delete these folders wholesale: they also hold message databases and settings.
What these two folders are
macOS gives sandboxed apps their own space in your Library:
| Folder | What's in it | Named like |
|---|---|---|
~/Library/Containers | One folder per sandboxed app: its settings, databases, caches, sometimes documents | com.microsoft.teams2 |
~/Library/Group Containers | Data an app shares with its widgets, extensions or sibling apps | 6N38VWS5BX.ru.keepcoder.Telegram |
The first part of a Group Containers name, like 6N38VWS5BX, is the developer's team ID. The rest is the app's ID, which tells you whose folder it is. Apple's own start with group.com.apple.
macOS Storage settings don't show these folders by name. Their space mostly lands in the app's row or in "System Data", which is why people find them only after the disk is nearly full.
Find out which app is using the space
These only read, so they're safe to run:
$ du -sh ~/Library/Containers ~/Library/Group\ Containers $ du -sh ~/Library/Group\ Containers/* | sort -h | tail $ du -sh ~/Library/Containers/* | sort -h | tail
macOS may ask whether Terminal can access data from other apps. That's its protection for app containers; allow it to measure, or measure from Finder with Get Info.
Here's what I found on my Mac on 8 November 2026:
$ du -sh ~/Library/Containers ~/Library/Group\ Containers # 1.7G ~/Library/Containers # 39G ~/Library/Group Containers
677 folders in Containers added up to 1.7 GB; the biggest was Microsoft Teams at 846 MB. Group Containers had 130 folders, and two of them were almost all of the 39 GB:
| Folder | Size | What it is |
|---|---|---|
6N38VWS5BX.ru.keepcoder.Telegram | 35 GB | Telegram for macOS |
HUAQ24HBR6.dev.orbstack | 3.7 GB | OrbStack, which runs Docker containers |
| the other 128 folders | 145 MB together |
Telegram: 34 GB of media cache
Inside Telegram's folder, nearly everything was in one place:
$ du -sh ~/Library/Group\ Containers/6N38VWS5BX.ru.keepcoder.Telegram/stable/account-*/postbox/* # 1.3G db # 34G media
media held 286,213 files: every photo, video, voice message and document I'd opened in Telegram, kept on disk. Reports of this go back years: a bug report from 2019 already described the same folder reaching 100 GB because it was never cleared. db is the local database of your chats, and that one you should leave alone.
Clear it from Telegram
The safe way is inside the app:
- Open Telegram and go to Settings › Data and Storage › Storage Usage.
- Clear the cache, all of it or by type (photos, videos, files).
- Set Keep Media to a short time, such as a week or a month, so unused media is removed by itself.
- Set a Maximum Cache Size, so the cache can't grow past it.
Clearing Telegram's cache only removes local copies. Your chats and their media stay in Telegram's cloud and download again when you open them.
If you clear it by hand instead, quit Telegram first, and move only the postbox/media folder to the Trash, never postbox/db or the whole Telegram folder. Those hold your local chat database and settings.
OrbStack and Docker
OrbStack keeps its disk image in its Group Containers folder; Docker Desktop keeps Docker.raw in ~/Library/Containers/com.docker.docker. Both grow with images, build cache and volumes, and both shrink with Docker's own prune commands, not by deleting the folder. The Docker disk space guide has the safe order, and why volumes are data.
What not to do
- Don't delete
~/Library/Containersor~/Library/Group Containers. Every app that uses them loses its settings and data at once. - Don't delete a folder for an app you still use. Clear space from inside the app.
- Do remove the folders of apps you've uninstalled. Dragging an app to the Trash leaves its containers behind. A folder named after an app you no longer have is safe to move to the Trash, after a look inside.

To see where the rest of your space went, see System Data huge on Mac?, or run diskreceipt, a free Terminal tool that only reads.
Sources
- Measured on this Mac on 8 November 2026 (macOS 26.5.1):
duon~/Library/Containers,~/Library/Group Containersand Telegram'spostbox, and a file count ofpostbox/media. Nothing was deleted. - Telegram for macOS: Settings › Data and Storage › Storage Usage, with Keep Media and Maximum Cache Size.
- Shedi's uninstaller rules: an app's Containers and Group Containers folders are matched by its exact bundle ID and start unselected.