How to Clear Cache in Microsoft Teams (When It’s Acting Strange)

Summary

This guide explains how to clear the local Microsoft Teams cache when the app is behaving oddly, such as failing to load chats, showing blank screens, not updating presence, or getting stuck during sign-in. Clearing the cache forces Teams to rebuild local files, which often fixes day-to-day glitches without needing a full reinstall.

Assumptions

You’re a standard user (not an admin) with permission to close Teams and restart your computer if needed. These steps apply to the Microsoft Teams desktop app on Windows or macOS and will not delete your chat history (that data lives in Microsoft 365), but you may need to sign in again.

Quick Guide

Fully quit Teams, remove the local cache folders, then reopen Teams and sign back in if prompted. If the issue is tied to a corrupted local profile or an outdated client, clearing cache usually resolves it. If it doesn’t, the next best step is updating Teams or reinstalling the app.

Step-by-Step Instructions

1. Confirm you’re using the desktop app (not just a browser) If Teams is only misbehaving in a browser, clearing your browser cache or switching browsers is often the better fix. If the desktop app is acting strange, continue below.

2. Fully quit Microsoft Teams On Windows, right-click the Teams icon in the system tray (near the clock) and select Quit. On Mac, right-click Teams in the Dock and choose Quit, or use Command + Q while Teams is active. Make sure Teams is not still running in the background before deleting cache files.

3. Clear cache on Windows (classic and most common path) a. Press Windows + R to open Run b. Paste this and press Enter: %appdata%\Microsoft\Teams c. Delete the contents inside this folder (not your entire user profile), focusing on common cache folders such as: Cache, Code Cache, GPUCache, IndexedDB, Local Storage, tmp d. Close File Explorer

4. Clear cache on Windows (new Teams) If you’re on the “new Teams” app, the cache location is different. a. Press Windows + R b. Paste this and press Enter: %localappdata%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache c. Delete the contents of the LocalCache folder. If that folder doesn’t exist, you’re likely not on the new Teams build or it’s installed differently in your environment.

5. Clear cache on macOS a. Open Finder b. Click Go in the menu bar, then Go to Folder… c. Enter: ~/Library/Application Support/Microsoft/Teams d. Delete the contents inside that Teams folder, especially folders like Cache, Code Cache, GPUCache, IndexedDB, Local Storage, tmp e. Also check and remove related cache files here if present: ~/Library/Caches/com.microsoft.teams

6. Reopen Teams and sign in. Launch Teams again. It may take a little longer on first startup while it rebuilds local data. If prompted, sign in and complete MFA if required.

7. Test the problem you were seeing Try the specific action that was failing (opening a chat, joining a meeting, loading a channel, searching, etc.). If it’s improved, you’re done.

8. If the issue persists, do a quick update check Teams updates quietly most of the time, but if you’re stuck on a buggy build, updating can matter. If you have access, check for updates in Teams settings, or close Teams and reopen it to trigger an update cycle. If your organization controls updates, IT may need to assist.

Troubleshooting

If Teams won’t fully quit, it can keep cache files “locked” and prevent a clean reset. On Windows, open Task Manager and end any Teams processes, then repeat the cache steps. On Mac, use Activity Monitor and force quit Teams if needed. If Teams keeps signing you out repeatedly after cache clearing, the issue may be tied to device sign-in state, conditional access, or a corrupted Windows credential entry, which usually needs IT support. If the problem only happens in one team or channel, it may be a service-side issue or a permissions problem rather than cache corruption, so clearing cache won’t change it.

Security / Business Considerations

Clearing Teams cache is a safe first-line fix because it removes local artifacts, not your actual Microsoft 365 data. That said, it can remove stored sign-in tokens and locally cached content, which is helpful when a device is behaving unpredictably but also means you should only do this on a trusted, managed workstation. If a user is on a shared or unmanaged device, unexpected sign-in prompts or MFA failures after cache clearing can indicate broader identity policy issues that IT should validate.

When to Contact IT Support

Contact IT if the issue returns immediately after cache clearing, if you cannot sign back in, if you’re repeatedly prompted for credentials or MFA in a loop, or if Teams fails to launch at all. Also escalate if multiple users are experiencing the same symptoms at the same time, which can point to a Microsoft service incident or an org-wide configuration change rather than a local cache problem.

About MET Florida

MET Florida helps businesses keep everyday IT systems stable, secure, and easy to use. We focus on practical support for Microsoft 365, devices, identity, and connectivity with processes designed for real business operations. If Teams issues are recurring, we can help identify whether the root cause is the device, the account, or the tenant configuration.