How to Clear Microsoft Teams Cache on Windows & Mac

Introduction: When Teams Acts Weird, the Cache May Be the Mischief

Microsoft Teams is supposed to be the reliable conference room, chat desk, file cabinet, whiteboard, and “quick question” machine of modern work. Most days, it does the job. But sometimes Teams starts behaving like it had three cups of coffee and forgot what meeting it joined. Profile photos refuse to update. Chats look stale. Images do not load. Status gets stuck. The app opens slowly, freezes, or insists that something is wrong without offering anything more helpful than a digital shrug.

That is where clearing the Microsoft Teams cache can help. The cache is a local collection of temporary files that Teams stores on your computer to make the app faster. It may include images, thumbnails, app data, sign-in details, local web content, database files, and other bits of information Teams uses so it does not have to download everything again every time you open the app. In normal life, that is helpful. In troubleshooting life, those files can become stale, damaged, or confused.

The good news: clearing the Teams cache on Windows or Mac is usually safe, quick, and surprisingly effective. It does not delete your Teams chats, meeting history, shared files, channels, or Microsoft 365 data from the cloud. It simply forces the desktop app to rebuild its local files the next time it launches. Think of it as asking Teams to clean its desk before starting work again.

This guide explains how to clear Microsoft Teams cache on Windows and Mac, including the correct paths for new Teams and classic Teams, when to use a reset instead of manual deletion, what problems cache clearing can fix, and what to try if Teams still refuses to behave.

What Is Microsoft Teams Cache?

The Microsoft Teams cache is a set of local files stored on your computer. Teams uses those files to load content faster, remember app behavior, display images, speed up searches, and reduce repeated downloads. Since Teams is deeply connected to Microsoft 365, SharePoint, OneDrive, Outlook, Exchange, and your organization’s directory, caching helps keep the app responsive.

In simple terms, cache is Teams saying, “I have seen this before, so I will keep a copy nearby.” That is wonderful until Teams keeps the wrong copy nearby. A stale cache can cause old profile pictures, outdated display names, missing users, broken images, login loops, sluggish loading, frozen windows, or differences between the Teams desktop app and Teams on the web.

Common Signs You Should Clear Teams Cache

• Teams is slow to open or switch between chats.
• Your profile photo or someone else’s photo is outdated.
• Chats, teams, channels, or users are missing in the desktop app.
• The Teams desktop app shows different information than the web version.
• Images, GIFs, avatars, or meeting backgrounds do not load correctly.
• Teams gets stuck on loading, signing in, or updating.
• Audio, camera, or device settings behave strangely.
• Status does not update properly.
• You see repeated app errors even after restarting.

Clearing the Teams cache is not magic, although it occasionally feels like it. It will not fix a company-wide outage, a bad internet connection, an expired password, or a missing license. But for local desktop app problems, it is one of the best first troubleshooting steps.

Before You Clear the Cache: Do These Quick Checks

Before deleting files, take a few simple steps. They can save time and prevent confusion.

1. Confirm Whether You Use New Teams or Classic Teams

Microsoft Teams has had two desktop experiences: classic Teams and new Teams. The cache locations are different. New Teams on Windows uses a package folder under AppData\Local\Packages, while classic Teams uses the older %appdata%\Microsoft\Teams folder. On Mac, new Teams uses newer container folders, while classic Teams uses the older Microsoft Teams application support folder.

2. Quit Teams Completely

Closing the Teams window is not always the same as quitting the app. Teams may keep running in the background like a tiny office ghost. On Windows, right-click the Teams icon in the system tray and choose Quit. On Mac, right-click the Teams icon in the Dock and choose Quit, or press Command + Q.

3. Know What Will Be Removed

Clearing cache removes local app files. Your cloud data remains safe. However, some personal app preferences may reset, especially if you use the Windows reset method for new Teams. That may include settings such as theme preferences, appearance choices, and other local personalization.

4. Expect the First Restart to Take Longer

After clearing the cache, Teams has to rebuild local files. The next launch may be slower than usual. Do not panic. Teams is not sulking; it is rebuilding its furniture.

How to Clear Microsoft Teams Cache on Windows

The steps depend on whether you are using new Teams or classic Teams. Most current Windows users are on new Teams, but many workplaces still support mixed environments. If you are not sure, start with the new Teams method. If the folder does not exist, check the classic Teams path.

Method 1: Reset New Microsoft Teams in Windows Settings

This is the easiest option for many Windows 10 and Windows 11 users. It clears app data through the Windows Settings interface.

1. Quit Microsoft Teams completely.
2. Click the Windows search box and type Settings.
3. Open the Settings app.
4. Go to Apps > Installed apps.
5. Search for Microsoft Teams.
6. Find New Microsoft Teams, click the three-dot menu, and choose Advanced options.
7. Scroll to the Reset section.
8. Click Reset.
9. Open Teams again and sign in if prompted.

This method is clean and beginner-friendly. The tradeoff is that it may remove personalization settings. If your Teams theme suddenly returns to default and your carefully curated dark-mode cave disappears, that is why.

Method 2: Manually Delete New Teams Cache Files on Windows

If you prefer the folder method, use the new Teams cache location below.

1. Quit Microsoft Teams completely.
2. Press Windows + R to open the Run dialog box.
3. Copy and paste this path:

4. Click OK.
5. Select all files and folders inside the directory.
6. Delete them.
7. Restart Microsoft Teams.

Do not delete random Windows folders outside the Teams path. The goal is to clean Teams cache, not give your operating system a surprise haircut.

Method 3: Clear Classic Teams Cache on Windows

If your organization still uses classic Teams, use this older cache path.

1. Quit Microsoft Teams completely from the taskbar or system tray.
2. Press Windows + R.
3. Enter this path:

4. Click OK.
5. Delete all files and folders in the Teams directory.
6. Restart Teams.

Classic Teams may include folders such as Application Cache, Cache, blob_storage, databases, GPUCache, IndexedDB, Local Storage, and tmp. You do not need to memorize those folder names. Delete the contents of the Teams cache directory, restart Teams, and let the app rebuild what it needs.

How to Clear Microsoft Teams Cache on Mac

Mac users can clear Teams cache with Terminal commands. That may sound intimidating if Terminal makes you feel like you accidentally opened the cockpit of a spaceship, but the process is straightforward. The key is using the correct command for your Teams version.

Clear New Microsoft Teams Cache on Mac

Use these steps for new Teams on macOS.

1. Quit Microsoft Teams completely. Right-click the Teams icon in the Dock and choose Quit, or press Command + Q.
2. Open Finder.
3. Go to Applications > Utilities.
4. Open Terminal.
5. Copy and paste the first command below, then press Return.
6. Copy and paste the second command below, then press Return.

7. Close Terminal.
8. Restart Microsoft Teams.

The rm -rf command removes the specified folder and its contents. That is why it is important to copy the path carefully. Used correctly, it clears the Teams cache. Used creatively, it can ruin your afternoon.

Clear Classic Teams Cache on Mac

If you are using classic Teams on macOS, use this command instead:

After running the command, restart Teams. The app will recreate the necessary files when it opens.

Mac Finder Alternative for New Teams

If your organization prefers not to use Terminal, you may be able to remove the same folders through Finder:

1. Quit Teams completely.
2. Open Finder.
3. Press Command + Shift + G.
4. Enter this path:

5. Move the contents to Trash.
6. Repeat the process for:

7. Restart Teams.

If macOS blocks access to certain folders, your organization’s security settings may be involved. In managed workplaces, contact IT before changing privacy, security, or Full Disk Access settings.

Will Clearing Teams Cache Delete My Chats or Files?

No. Clearing the Microsoft Teams cache does not delete your cloud-based chats, channels, files, meetings, or shared documents. Teams stores those items in Microsoft 365 services such as Exchange, SharePoint, OneDrive, and Teams itself. Cache files are local copies and temporary data used by the desktop app.

However, you may notice a few temporary changes after clearing cache:

• Teams may take longer to open the first time.
• You may need to sign in again.
• Some local preferences may reset.
• Images, avatars, and chat content may take a moment to reload.
• Offline or recently viewed content may need to download again.

In most cases, those small inconveniences are worth it if the app becomes usable again. A refreshed Teams client is much better than one that stares blankly at you five minutes before a meeting.

When Clearing Teams Cache Helps Most

Clearing cache is especially helpful when the problem appears only in the desktop app. For example, if Teams on the web works correctly but Teams on Windows or Mac does not, local cache is a strong suspect.

Example 1: Profile Picture Not Updating

Profile pictures can linger in cache longer than users expect. You may upload a new photo in Microsoft 365, see it correctly in the browser, and still see the old image in the Teams desktop app. Clearing the cache forces Teams to download fresh profile data.

Example 2: Teams Shows Old Names or Contact Details

Display names, phone numbers, and other user information can be cached. If someone changes departments, gets a new title, or updates directory information, Teams may not display the change immediately. Signing out and back in can help, and clearing cache is a stronger refresh.

Example 3: Images or Backgrounds Do Not Load

When images appear broken, meeting backgrounds disappear, or avatars look wrong, cached image files may be corrupted. Clearing cache gives Teams a fresh start.

Example 4: Teams Is Slow or Freezing

Large or damaged local files can make the desktop app sluggish. Clearing cache removes old temporary data and may improve performance, especially on older computers or heavily used workstations.

Example 5: Login Loops or App Launch Errors

If Teams keeps asking you to sign in, fails to launch, or displays vague errors, clearing cache may remove the local data causing the loop. If the issue continues, the next step is usually updating, repairing, reinstalling, or contacting IT.

Teams Cache vs. Browser Cache: What Is the Difference?

Clearing Teams desktop cache affects the installed Teams app on Windows or Mac. Clearing browser cache affects Teams on the web, such as when you use Teams in Microsoft Edge, Chrome, Safari, or Firefox.

If the desktop app is broken but Teams works fine in the browser, clear the desktop cache. If Teams on the web has trouble loading, clear your browser cache or try an InPrivate or Incognito window. If both desktop and web versions fail, the issue may involve your Microsoft account, network, license, service status, or organization settings.

A good troubleshooting trick is to test teams.microsoft.com in a browser. If the web version shows the correct data, the desktop app probably needs a local cleanup. If the web version shows the same problem, cache may not be the main villain.

What to Do After Clearing Microsoft Teams Cache

After you clear the cache and restart Teams, give the app a few minutes to rebuild. Then test the original problem. Do not judge it in the first five seconds, especially if your device is older or your connection is slow.

Checklist After Restarting Teams

• Sign in again if prompted.
• Wait for chats, teams, and channels to reload.
• Check whether profile photos or user information updated.
• Open a recent chat and confirm images load.
• Join a test meeting if your issue involved audio, camera, or devices.
• Compare the desktop app with Teams on the web.

If everything works, congratulations: you have successfully persuaded Teams to stop hoarding digital crumbs. If the issue remains, continue with the next troubleshooting steps.

If Clearing Cache Does Not Fix Teams

Cache clearing is a strong first move, but it is not the only move. If Teams still misbehaves, try these steps.

Update Microsoft Teams

Outdated app versions can cause bugs. Open Teams, check for updates if the option is available, or restart the app so it can apply pending updates. In managed organizations, updates may be controlled by IT.

Restart Your Computer

Yes, it is the classic IT suggestion. Yes, it still works. A full restart clears stuck background processes, refreshes network connections, and gives Windows or macOS a chance to stop pretending everything is fine.

Try Teams on the Web

Use the web version to confirm whether the problem is local to your desktop app. If the browser version works, the issue is probably on your device. If the web version fails too, the problem may be account-based, service-based, or organization-wide.

Check Your Internet Connection

Teams depends on stable connectivity. Weak Wi-Fi, VPN conflicts, proxy rules, firewall restrictions, and DNS issues can all create symptoms that look like app problems.

Repair, Reset, or Reinstall Teams

On Windows, the app settings page may offer repair or reset options. If those do not help, uninstalling and reinstalling Teams can replace damaged application files. On Mac, removing and reinstalling Teams may help if cache clearing is not enough.

Contact Your IT Team

If you use a work or school account, your organization may manage Teams policies, device settings, sign-in rules, conditional access, security tools, and update channels. When in doubt, contact ITespecially before deleting advanced identity, keychain, or managed container data.

Best Practices for Keeping Teams Healthy

You should not need to clear the Teams cache every day. If you do, something deeper may be wrong. Still, a few habits can keep Teams running smoothly.

• Quit Teams fully once in a while. Letting it run for weeks can make small problems pile up.
• Keep your operating system updated. Teams relies on Windows and macOS components.
• Use a stable internet connection. Video meetings and file previews dislike shaky Wi-Fi.
• Avoid running too many heavy apps during meetings. Teams, twenty browser tabs, a giant spreadsheet, and a screen recorder may not become best friends.
• Compare desktop and web versions. This quickly tells you whether a problem is local.
• Do not delete unknown folders. Stick to documented Teams cache paths.

Quick Reference: Teams Cache Locations

New Teams on Windows

Classic Teams on Windows

New Teams on Mac

Classic Teams on Mac

Save these paths somewhere safe if you support multiple users. They are especially useful for help desk teams, remote workers, students, freelancers, and anyone who has ever joined a meeting only to find that Teams has decided the camera is a decorative object.

Real-World Experiences: What Clearing Teams Cache Feels Like in Daily Work

In real office life, Teams cache problems rarely announce themselves politely. They usually arrive five minutes before a client call, right after someone says, “This should only take a second.” One common experience is the mysterious profile-photo delay. A user updates their picture in Microsoft 365, sees it correctly in Outlook, checks Teams, and there it is: the old photo from three haircuts ago. Waiting may eventually solve it, but clearing the Teams cache often makes the desktop app fetch the latest information sooner.

Another familiar situation is the “Teams works in the browser but not in the app” puzzle. This is one of the clearest signs that the desktop cache deserves attention. For example, a project manager may open Teams on the web and see all channels, files, and messages correctly. Then the desktop app shows missing chats, frozen content, or a blank space where a file preview should be. In that case, clearing the local cache is not a random guess. It is a targeted way to remove stale desktop data and make the app rebuild from Microsoft 365.

On Windows, the reset method is usually the least stressful for nontechnical users. It is visual, it stays inside Settings, and it avoids copying long folder paths. For IT teams, the manual folder method can be faster because it goes straight to the cache location. The important detail is quitting Teams first. If Teams is still running in the system tray, some files may be locked, and the cleanup may not fully work. That tiny tray icon has caused more troubleshooting confusion than it deserves.

On Mac, the experience can feel a little more technical because Terminal is involved. The command itself is simple, but users should copy it carefully. A cautious approach is best: quit Teams, paste one command at a time, press Return, then restart Teams. In managed company environments, some Mac users may run into permission restrictions. That does not mean the steps are wrong; it may mean the device is protected by security policies. In that case, IT support should handle the cleanup.

Clearing cache is also useful after switching between multiple organizations or guest tenants. People who work with vendors, clients, schools, or partner companies may notice that Teams gets confused about accounts, avatars, notifications, or workspaces. Signing out helps, but clearing cache can provide a deeper refresh. It is like telling Teams, “Forget the messy local notes and ask the cloud again.”

One practical lesson: do not clear cache during a rush unless you have a few minutes to reopen and sign in. The first launch after cleanup can be slower because Teams has to recreate files. If you have a meeting in thirty seconds, use Teams on the web as a temporary escape hatch. Clear the cache afterward when you are not under the emotional pressure of a blinking meeting reminder.

The best mindset is to treat cache clearing as regular troubleshooting, not a dramatic emergency procedure. It is safe when done correctly, it solves many desktop-only problems, and it gives Teams a clean local start. Just remember that repeated cache problems may point to something bigger, such as outdated software, device management conflicts, network filtering, or account synchronization issues. Clear the cache when needed, but do not let it become a daily ritual unless you enjoy living in IT Groundhog Day.

Conclusion

Knowing how to clear Microsoft Teams cache on Windows and Mac is one of those small tech skills that can save a surprising amount of frustration. When Teams shows old profile pictures, loads slowly, misses chats, breaks images, freezes, or behaves differently from the web version, cached local files may be the cause. For new Teams on Windows, you can reset the app through Settings or delete files from the new Teams cache folder. For classic Teams, the older %appdata%\Microsoft\Teams path still applies. On Mac, new Teams uses modern container folders, while classic Teams uses the older Microsoft application support directory.

Clearing Teams cache does not remove your cloud data. It simply makes the desktop app rebuild local files. The first restart may take longer, and some preferences may reset, but the payoff is often a cleaner, faster, less cranky Teams experience. If the problem continues, update Teams, restart your device, test the web version, check your connection, or contact your IT team. Teams may be a collaboration powerhouse, but sometimes even powerhouses need a broom.