Claude Desktop Partition Caches
Claude Desktop keeps Chromium partition caches under its Partitions directories so embedded web views can store temporary browser data separately from the main app profile. These partition folders accumulate HTTP disk cache entries, GPUCache data such as compiled shader blobs, Code Cache files for JavaScript bytecode, and other transient network and rendering artifacts that speed up loading the Claude interface and related embedded content. Kudu removes only those preview-partition cache files on Windows, while leaving sessions, IndexedDB, local storage, service worker data, offline content, accounts, and app settings untouched.
Why clean Claude Desktop Partition Caches?
- Corrupted HTTP disk cache entries can make parts of the Claude interface load old assets or fail to refresh, showing broken panels, missing styles, or pages that never finish loading
- Stale GPUCache data after a graphics driver update can invalidate Chromium shader data, causing black flashes, blank surfaces, or choppy scrolling until the cache is rebuilt
- Outdated JavaScript Code Cache bytecode after a Claude Desktop update can slow the first launch and trigger odd UI behavior until fresh bytecode is generated
- Oversized partition caches can consume hundreds of megabytes in AppData, which users usually notice as unexpectedly large Claude folders despite no increase in chat history
- Bad cached responses inside an embedded partition can cause repeated sign-in prompts, stuck loading spinners, or web content that works in a browser but not inside Claude Desktop
- Cache index inconsistencies can lead to unnecessary revalidation and repeated asset downloads, which shows up as slower startup and extra disk activity every time Claude opens
Cache paths Kudu targets
Windows
%AppData%/Claude/Partitions |
%LocalAppData%/Packages/Claude_pzs8sxrjxfjjc/LocalCache/Roaming/Claude/Partitions |
Common questions about Claude Desktop Partition 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.