Apps

Spotify Store Browser Cache

Spotify’s Microsoft Store app embeds a Chromium-based web layer for home, search, artist, playlist, podcast, and merch surfaces, and it writes browser cache data under its LocalCache Browser folder. That cache typically includes HTTP disk cache entries, media and image cache objects, partitioned site data used by embedded web views, GPU shader and rendering caches, and Chromium code cache files for JavaScript-heavy screens. Kudu removes only those disposable browser and partition caches so stale web assets are rebuilt, while leaving your account state, sessions, downloads, IndexedDB, and offline content untouched.

Why clean Spotify Store Browser Cache?

  • Stale HTTP cache entries can keep serving an older web bundle after Spotify updates, which shows up as a blank Home tab, missing cards, or sections that never finish loading
  • Corrupted image and media cache objects cause playlist artwork, artist banners, and podcast thumbnails to appear empty or flicker until the app refetches them
  • Invalidated Chromium code cache after a Store app update can make Search, Browse, or podcast pages open slowly on first use and feel stuck before the scripts rebuild
  • Old GPU and shader cache data from a previous graphics driver version can trigger black panels, flashing UI, or jerky scrolling in hardware-accelerated views
  • Broken partition cache data for embedded web content can leave merch, login-related popups, or external content panes spinning indefinitely even though the rest of Spotify works
  • An oversized browser cache wastes space under LocalCache and can make Spotify repeatedly read bad cached responses instead of downloading fresh page assets
What gets cleaned

Cache paths Kudu targets

Windows

%LocalAppData%/Packages/SpotifyAB.SpotifyMusic_zpdnekdrzrea0/LocalCache/Spotify/Browser
Frequently asked

Common questions about Spotify Store Browser Cache

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.