Apps
Microsoft Teams
Built on web technologies, Microsoft Teams stores Chromium-style disk cache entries for chat views, channel pages, images, scripts, CSS, and API responses so the interface can reopen faster and reuse recently fetched content. When those cached web assets become stale or inconsistent after a Teams update, tenant switch, or sign-in change, users can see loading loops, blank panes, or outdated content. Kudu removes the cached web content in the Teams Cache folder without touching messages, files in Microsoft 365, account sign-ins, or app settings.
Why clean Microsoft Teams?
- Stale cached JavaScript or CSS after a Teams update can leave the window stuck on a white screen or endless loading spinner until fresh assets are downloaded
- Corrupted disk cache entries for chat and channel pages can cause missing conversation history in the view even though the messages still exist on the server
- Old cached API responses after switching organizations or accounts can show the wrong team list, outdated avatars, or channels that fail to refresh
- A bloated Chromium web cache can consume hundreds of megabytes and make Teams slower to open recent chats because it spends longer validating old entries
- Broken cached images and thumbnails can appear as blank profile photos, missing reaction icons, or previews that never load in chat
- Interrupted writes in the cache folder can trigger repeated reloads, sign-in loops, or panes that render partially until the local web content is rebuilt
- Removing obsolete cached web assets forces Teams to fetch current pages from Microsoft 365, often fixing stuck notifications and inconsistent UI state without affecting user files
What gets cleaned
Cache paths Kudu targets
Windows
%AppData%/Microsoft/Teams/Cache |
macOS
~/Library/Application Support/Microsoft Teams/Cache |
Linux
~/.config/Microsoft/Microsoft Teams/Cache |
Frequently asked
Common questions about Microsoft Teams
Free & open source
Download Kudu and reclaim your disk space.
Available on Windows, macOS, and Linux. No account required, no feature gates, no telemetry without consent. All cleaning targets are open source and community-auditable.