Spotify Store Browser Cache
Spotify’s Microsoft Store build embeds a Chromium-based browser layer that stores HTTP disk cache entries, media thumbnails, JavaScript bundles, CSS, service worker resources, and partitioned site data under its Browser cache directory. Those files speed up loading for the Home feed, search, artist pages, ads, and embedded web UI, but they can become inconsistent after app updates or server-side changes. Kudu removes only this Store browser cache so Spotify can fetch fresh web assets again, while leaving account state, downloads, sessions, IndexedDB, and offline data untouched.
Why clean Spotify Store Browser Cache?
- Stale cached JavaScript or CSS from an older Spotify web bundle can leave the Home tab blank or partially unstyled until fresh assets are downloaded
- Corrupted Chromium disk cache entries cause album art, podcast thumbnails, or banner images to show as gray placeholders even though playback still works
- Expired service worker resources in the Store app’s browser layer can make search results or artist pages load old content, spin indefinitely, or fail with generic loading errors
- An oversized browser cache accumulates thumbnail and API response files, wasting LocalAppData space and making the Spotify package unexpectedly large in Windows storage settings
- Mismatched cached API responses and frontend code after a Spotify rollout can break buttons such as Like, Follow, or queue actions until the browser cache is rebuilt
- Bad partition cache data can trigger repeated reloads, missing recommendation carousels, or storefront sections that never populate even on a stable connection
Cache paths Kudu targets
Windows
%LocalAppData%/Packages/SpotifyAB.SpotifyMusic_zpdnekdrzrea0/LocalCache/Spotify/Browser |
Common questions about Spotify Store Browser Cache
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.