Is it safe to clear the Microsoft Teams cache on a Mac?
- Yes, with Teams quit. Microsoft documents it: two folders for the new Teams, one for classic Teams. Chats, channels and files are stored in Microsoft 365, not in the cache.
- What it costs you: Teams takes longer to start the first time, because it rebuilds the cache. Microsoft also points out that clearing deletes the diagnostic logs support would need.
- Does it come back? Yes, the next time Teams opens.
- SiftMac’s verdict: Rebuilds
1. What it is
The Teams app keeps local copies of what it shows, along with its diagnostic logs, so it starts quickly and problems can be traced. The conversations themselves, and the files shared in them, are stored in Microsoft 365 and load again after a clear.
Microsoft is clear that it’s a targeted fix, not a first step. Clearing the cache doesn’t fix missing messages, chat history that won’t load, a team or channel that doesn’t show up, or wrong notifications and unread counts. It does delete the logs needed to find the cause of those.
2. Where it is
~/Library/Containers/com.microsoft.teams2
~/Library/Group Containers/UBF8T346G9.com.microsoft.teams
Those two belong to the new Teams; both are app containers, the protected folders macOS gives each app. The older classic Teams kept its cache in ~/Library/Application Support/Microsoft/Teams.
3. How big it gets
It depends on how long you’ve used Teams and how many teams, chats and meetings you’re part of. To check both folders in Terminal:
du -sh ~/Library/Containers/com.microsoft.teams2 ~/Library/Group\ Containers/UBF8T346G9.com.microsoft.teams
4. How to clear it safely
- Quit Teams: right-click its Dock icon and choose Quit, or press ⌘Q.
- Open Terminal from Applications › Utilities.
- Run these two commands, pressing Return after each, then open Teams again.
rm -rf ~/Library/Group\ Containers/UBF8T346G9.com.microsoft.teams/*
rm -rf ~/Library/Containers/com.microsoft.teams2/*
Microsoft’s article deletes the two folders themselves; the commands above empty them instead and leave the folders for macOS. If you copy Microsoft’s version, add a backslash before the space in Group Containers, as above, or the command misses the folder.
For classic Teams, quit it and clear its folder the same way:
rm -rf ~/Library/Application\ Support/Microsoft/Teams/*
5. What happens afterwards
- Teams takes longer than usual to start while its cache files are rebuilt, as Microsoft notes.
- You may have to sign in again.
- Chats, channels, meetings and files are still there: they come from Microsoft 365.
- Earlier diagnostic logs are gone, so if IT is looking into a problem, ask them before clearing.
Questions
Will clearing the Teams cache delete my chats?
No. Chats and files are stored in Microsoft 365, and Teams loads them again. Microsoft even warns that clearing the cache won’t bring back missing messages.
Is UBF8T346G9.com.microsoft.teams safe to delete?
Its contents are, with Teams quit: it’s one of the two folders Microsoft tells you to clear. Other folders in Group Containers that start with UBF8T346G9 belong to other Microsoft apps, so leave those.
Teams still misbehaves after clearing the cache. What next?
Microsoft treats clearing as a fix for a few problems with the app itself. For missing messages or wrong unread counts it doesn’t help, and support needs the logs it deletes, so contact your IT admin.
Do I still need the classic Teams folder?
The new Teams uses its own containers, and Microsoft gives separate steps for each version. If classic Teams is gone from your Mac, its folder in Application Support/Microsoft/Teams is just old cache.
How SiftMac handles it. Teams keeps its cache in app containers, which macOS guards, so SiftMac doesn’t clear them; its space map shows ~/Library/Containers and ~/Library/Group Containers as private rather than reading them. A Teams folder in ~/Library/Caches, if there is one, is treated like any app cache: cleared only while Teams is closed.
Download SiftMac · scanning is free, and so is your first 2 GB of cleaning · See how it works