How to Clear the Microsoft Teams Cache

Clearing the Microsoft Teams cache fixes a specific and recognisable set of problems: a client stuck loading, messages that will not send, a status that never updates, missing chats, or a sign-in loop.

It is safe — nothing is deleted from the server, because Teams stores everything in the cloud. What you clear is a local copy, which Teams rebuilds on the next launch.

Before clearing the cache

Two faster things fix a good share of Teams problems:

1. Quit properly and reopen. Closing the window leaves Teams running. Right-click its icon in the notification area and choose Quit, then reopen.
2. Sign out and back in. Profile picture → Sign out.

If neither helps, clear the cache.

Windows

1. Quit Teams completely

1. Right-click the Teams icon in the notification area → Quit.
2. Open Task Manager (Ctrl + Shift + Esc) and end any remaining Microsoft Teams processes.

This step is not optional — files in use cannot be deleted, and skipping it is why the process appears not to work.

2. Clear the cache folder

For the current Teams client:

1. Press Win + R.
2. Paste this and press Enter:

%LOCALAPPDATA%PackagesMSTeams_8wekyb3d8bbweLocalCache

3. Delete the contents of that folder. Skip anything that refuses — it is still in use.
4. Reopen Teams.

The first launch afterwards is slower while it rebuilds.

The complete reset

If clearing the cache is not enough, reset the app itself — this is cleaner than deleting folders by hand:

1. Settings → Apps → Installed apps.
2. Find Microsoft Teams, three-dot menu → Advanced options.
3. Try Repair first, which keeps your data.
4. If that fails, use Reset. You will sign in again.

macOS

1. Quit Teams entirely: Cmd + Q, then check it is gone from the Dock.
2. In Finder, press Cmd + Shift + G.
3. Go to:

~/Library/Group Containers/UBF8T346G9.com.microsoft.teams

4. Move the contents to the Bin.
5. Also check ~/Library/Containers/com.microsoft.teams2 for the current client.
6. Reopen Teams.

If you are still signed in with old credentials afterwards, open Keychain Access, search for Microsoft Teams, and delete the entries.

Teams on the web

The browser version has its own cache. Clear it for that site only:

1. With Teams open, select the padlock or tune icon in the address bar.
2. Cookies and site data → Manage on-device site data → delete.
3. Reload and sign in.

Clearing only that site keeps you signed in everywhere else — see managing browser data.

What clearing the cache does and does not do

The one genuine loss is anything not yet synced — a message typed while offline that never sent. Rare, but worth knowing before you clear.

When the cache is not the problem

• Nobody in your organisation can use Teams: check the Microsoft 365 service status. A service incident is not fixable locally.
• Camera or microphone not working: that is Windows permissions. Settings → Privacy & security → Camera and Microphone. See resetting sound settings.
• Poor call quality: a network problem, not a cache one. Try a wired connection.
• Sign-in fails repeatedly: may be conditional access policy on a work account — contact IT.

Frequently asked questions

Will I lose my chat history?

No. Chats, channels and files are stored on Microsoft’s servers. The cache is a local copy that Teams rebuilds.

How often should I do this?

Only when something is wrong. It is a troubleshooting step, not maintenance — and the first launch afterwards is noticeably slower.

The folder will not delete.

Teams is still running. Quit it from the notification area and end any remaining processes in Task Manager, then try again.

Why does Teams use so much disk space?

The cache holds images, avatars and message data for fast loading, and it grows steadily. Clearing it reclaims that space, at the cost of a slower first launch.

Does this apply to the old Teams client?

The old client’s folder — %AppData%MicrosoftTeams — is what most older guides describe, and it no longer applies. Use the path above for the current app.