Ledger Live
Built on Electron, Ledger Live stores Chromium disk cache entries in Cache_Data for downloaded app resources and API responses, V8 code cache files for precompiled JavaScript, and GPUCache data for rendered UI assets and shader-related GPU state. Those files help the portfolio dashboard, account views, and embedded web content load faster, but they can become stale after Ledger Live, Chromium, or graphics driver updates. Kudu removes only these temporary cache directories so Ledger Live can rebuild them cleanly without touching wallets, account data, device pairing information, settings, or recovery material.
Why clean Ledger Live?
- Invalidated V8 code cache after a Ledger Live update can make the app hang longer on the splash screen or feel unusually slow on the first few launches
- Stale Chromium disk cache entries can leave the portfolio page, market data, or account panels showing outdated content until a hard refresh or cache cleanup
- Corrupted Cache_Data files can cause blank sections in the embedded interface, missing images, or endless loading spinners when opening accounts and manager views
- GPU cache data tied to an older graphics driver can become invalid after a driver update, leading to black windows, flickering panels, or choppy transitions in the Electron UI
- Oversized cache folders from repeated asset downloads and API responses can consume hundreds of megabytes and make Ledger Live feel heavier during startup and navigation
- Bad cached web resources can trigger sign-in or device-management pages to render incorrectly, with buttons not appearing or parts of the interface failing to respond
Cache paths Kudu targets
Windows
%AppData%/Ledger Live/Cache/Cache_Data |
%AppData%/Ledger Live/Code Cache |
%AppData%/Ledger Live/GPUCache |
macOS
~/Library/Application Support/Ledger Live/Cache/Cache_Data |
Linux
~/.config/Ledger Live/Cache/Cache_Data |
Common questions about Ledger Live
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.