Spotify Store Shared Caches
Spotify's Microsoft Store build keeps a separate LocalCache area for Chromium-based web assets and compiled code used by the player shell, including Cache_Data HTTP objects, V8 Code Cache files, Shared Dictionary entries, component and extension CRX archives, and several GPU shader caches such as GPUCache, GrShaderCache, ShaderCache, DawnCache, DawnGraphiteCache, DawnWebGPUCache, and GraphiteDawnCache. These files speed up loading the Home view, search, lyrics, widgets, and hardware-accelerated interface rendering, but they can become stale after app or graphics-driver updates and leave behind large crash dumps and launcher logs. Kudu removes those rebuildable caches, widget and launcher logs, and Crashpad reports while preserving the Data and offline-storage trees so downloads, account state, settings, and personal library data stay intact.
Why clean Spotify Store Shared Caches?
- Corrupted Cache_Data entries can leave Home, Search, or artist pages loading forever or showing blank sections because Spotify keeps reusing bad cached web responses.
- Invalidated V8 Code Cache after a Spotify update often causes an unusually slow first launch, delayed tab switching, or a briefly unresponsive interface until bytecode is rebuilt.
- Stale GPUCache, GrShaderCache, or ShaderCache files from a graphics driver update can cause black panels, flickering album art, or choppy animations in the hardware-accelerated UI.
- Outdated DawnCache, DawnGraphiteCache, DawnWebGPUCache, or GraphiteDawnCache blobs can trigger rendering glitches in newer interface components, with missing gradients, broken lyrics effects, or stutter when opening views.
- Damaged Shared Dictionary cache content can make compressed web resources decode incorrectly, which shows up as incomplete text, missing cards, or repeated reload attempts in the app shell.
- Old component_crx_cache and extensions_crx_cache packages can leave embedded Spotify components stuck on mismatched versions, causing features to fail to appear or repeatedly re-download at startup.
- Launcher and DashboardWidget logs plus Crashpad reports can accumulate after repeated startup failures or widget crashes, wasting disk space without affecting your playlists, downloads, saved songs, or login data.
Cache paths Kudu targets
Windows
%LocalAppData%/Packages/SpotifyAB.SpotifyMusic_zpdnekdrzrea0/LocalCache/Spotify/Default/Cache/Cache_Data |
%LocalAppData%/Packages/SpotifyAB.SpotifyMusic_zpdnekdrzrea0/LocalCache/Spotify/Default/Code Cache |
%LocalAppData%/Packages/SpotifyAB.SpotifyMusic_zpdnekdrzrea0/LocalCache/Spotify/Default/GPUCache |
%LocalAppData%/Packages/SpotifyAB.SpotifyMusic_zpdnekdrzrea0/LocalCache/Spotify/Default/DawnCache |
%LocalAppData%/Packages/SpotifyAB.SpotifyMusic_zpdnekdrzrea0/LocalCache/Spotify/Default/DawnGraphiteCache |
%LocalAppData%/Packages/SpotifyAB.SpotifyMusic_zpdnekdrzrea0/LocalCache/Spotify/Default/DawnWebGPUCache |
%LocalAppData%/Packages/SpotifyAB.SpotifyMusic_zpdnekdrzrea0/LocalCache/Spotify/Default/Shared Dictionary/cache |
%LocalAppData%/Packages/SpotifyAB.SpotifyMusic_zpdnekdrzrea0/LocalCache/Spotify/component_crx_cache |
%LocalAppData%/Packages/SpotifyAB.SpotifyMusic_zpdnekdrzrea0/LocalCache/Spotify/extensions_crx_cache |
%LocalAppData%/Packages/SpotifyAB.SpotifyMusic_zpdnekdrzrea0/LocalCache/Spotify/GraphiteDawnCache |
%LocalAppData%/Packages/SpotifyAB.SpotifyMusic_zpdnekdrzrea0/LocalCache/Spotify/GrShaderCache |
%LocalAppData%/Packages/SpotifyAB.SpotifyMusic_zpdnekdrzrea0/LocalCache/Spotify/ShaderCache |
%LocalAppData%/Packages/SpotifyAB.SpotifyMusic_zpdnekdrzrea0/LocalCache/Spotify/DashboardWidget/logs |
%LocalAppData%/Packages/SpotifyAB.SpotifyMusic_zpdnekdrzrea0/LocalCache/Spotify/DashboardWidget/Crashpad/reports |
%LocalAppData%/Packages/SpotifyAB.SpotifyMusic_zpdnekdrzrea0/LocalCache/Spotify/Launcher/Logs |
%LocalAppData%/Packages/SpotifyAB.SpotifyMusic_zpdnekdrzrea0/LocalCache/Spotify/Launcher/Crashpad/reports |
Common questions about Spotify Store Shared Caches
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.