How to Clear Cache on Teams Without Losing Files

Clearing the Microsoft Teams cache removes temporary files the app stores on your device. Those files help Teams load quickly, but if they become stale or damaged, clearing them may help with problems such as blank screens, sluggish loading, or repeated sign-in prompts. Teams rebuilds the cache as needed.

Cache clearing is different from deleting a chat, removing a file, or uninstalling Teams. It should not erase messages or files stored in Teams or OneDrive, but you may need to sign in again, and local preferences or temporary data can be reset. Save any work and close Teams before beginning. Menu names and locations can differ slightly by app version.

What You’ll Need

A Windows PC or Mac with Teams installed, if clearing the desktop app cache.
Permission to close Teams and remove files from your own user account.
Your work or school sign-in details, in case Teams asks you to authenticate again.
A few minutes while Teams rebuilds its temporary data after relaunching.

Step-by-Step

Identify your version. Check whether you use new Teams or classic Teams. The newer app is generally labeled Microsoft Teams; classic Teams may be named Microsoft Teams classic. If you use Teams in a browser, follow the browser-cache guidance below instead of deleting desktop folders.
Save work and quit Teams. Save drafts or files, then choose your profile menu and select Quit if that option is shown. Also check the notification area on Windows or the menu bar on Mac and quit Teams there. Closing its window alone may leave it running in the background.
Open the appropriate cache location. On Windows, press Windows key + R to open Run, enter the path for your version below, and press Enter. These paths use your Windows user profile; do not substitute another person’s account folder.
For new Teams, enter %LOCALAPPDATA%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams.

For classic Teams, enter %APPDATA%\Microsoft\Teams. If the folder is absent, you may have a different Teams version or installation type; do not delete unrelated Microsoft folders.
Remove the cache contents. In the opened Teams cache folder, select the contents and delete them. You can leave the folder itself in place. If Windows says a file is in use, Teams may still be running; quit it fully and try again. Avoid emptying other folders or deleting the whole Microsoft Teams package.
Use the Mac cache location when applicable. In Finder, select Go > Go to Folder, then enter ~/Library/Group Containers/UBF8T346G9.com.microsoft.teams for new Teams. For classic Teams, enter ~/Library/Application Support/Microsoft/Teams. Open the relevant folder and remove its contents, not unrelated files in Library. If a path is not present, do not create it or guess a substitute.
Restart Teams. Open the app normally and allow it time to rebuild local data. Sign in if requested and check whether the original problem is resolved. The first launch may take longer than usual while temporary files are recreated.
For Teams on the web, clear site data selectively. First sign out of Teams and close its tab. In your browser’s privacy or site-settings controls, find data for the Teams site you use and clear that site’s stored data, or clear cached files if the issue affects other sites too. Browser menus vary by version. This can sign you out, so make sure you can sign in again.

Common Mistakes

Only closing the window: Teams may continue running. Use Quit from the app or its taskbar/menu-bar icon before removing files.
Deleting the wrong folder: Remove contents only from the matching Teams cache location. Do not delete folders for other Microsoft apps, your entire user profile, or the Teams installation package.
Using classic Teams instructions for new Teams: The apps use different storage locations. Check the app version before entering a path; a missing folder does not mean you should delete a similarly named folder elsewhere.
Expecting cache clearing to fix every problem: It helps with local temporary-data issues, not necessarily account permissions, service outages, network problems, or a damaged installation.
Clearing browser data for every site unnecessarily: Start with Teams site data when possible. Clearing all browsing data can sign you out of unrelated websites and remove other saved site information.

Tips

Try a simple restart of Teams first if the issue is brief; cache removal is more useful when a problem persists.
Keep a note of the exact error and when it occurs. This can help your IT administrator distinguish a local app problem from an account or network issue.
Use the official Teams app controls to sign out or update the app. Do not remove credentials or system folders as a substitute for clearing the cache.
If you share the computer, make sure you are working in your own user account. Cache folders are tied to the signed-in computer user.
Allow the app to finish loading after the cleanup before repeating the procedure. Repeatedly deleting files during startup can interrupt the rebuild.

Troubleshooting

The folder does not open or does not exist: Confirm whether you have new or classic Teams and check the path for that version. Some installations use different storage arrangements. If the documented folder is missing, use Teams’ built-in repair or reset options in Windows app settings, if available, or ask your organization’s IT support rather than deleting a guessed location.

Windows or macOS says a file is in use: Quit Teams, then check the taskbar notification area or Mac menu bar for a remaining app process. If needed, restart the computer and try again before opening Teams. Do not force-delete files belonging to another running app.

The problem remains after clearing the cache: Restart the device, check that Teams is updated through your normal app store or organization’s software process, and test the web version or desktop version to see whether the issue is limited to one. If you still cannot sign in or messages fail to load, contact your organization’s IT administrator; the cause may be account access, network configuration, or a service issue.

Teams opens but asks you to sign in again: This can happen after local data is removed. Sign in with the correct work or school account and complete any normal organization authentication prompts. If access is denied, contact IT instead of trying to bypass security controls.

Frequently Asked Questions

Will clearing the Teams cache delete my chats or files?

It removes temporary local app data, not chats and files stored in your Teams account or cloud storage. You may need to sign in again, and unsent drafts or local preferences should not be treated as backed up.

How often should I clear the Teams cache?

There is no routine schedule needed. Clear it when troubleshooting a persistent app problem, rather than deleting it regularly.

Do I need administrator access?

Usually, no: the cache locations above are within your own user account. A work-managed device may have restrictions, so follow your organization’s IT instructions.

Should I clear the cache in the browser or the Teams app?

Clear the cache where the issue occurs. For a browser-only problem, try Teams site data in that browser; for a desktop-app issue, use the matching desktop cache location.

Why is Teams slower after I clear its cache?

Teams has to recreate temporary files, so the first launch can be slower. If performance stays poor after it has had time to reload, investigate app updates, connectivity, or account and service issues.

Further reading: Microsoft Support. Details can change, so check the official page for anything that matters to you. Spotted a mistake? Tell us. How we write an answer.