Apps
Loom
Built on Electron and Chromium, Loom stores browser-style disk cache entries, V8 code cache files, and GPU cache data to speed up loading its recorder interface, workspace views, thumbnails, and embedded web content. Those caches can become stale after Loom updates, Chromium changes, or graphics driver changes, leading to launch glitches or broken rendering. Kudu removes Loom's Cache_Data files, Code Cache bytecode, and GPUCache artifacts without touching recordings, account sign-in, workspace data, or preferences.
Why clean Loom?
- Invalidated Electron V8 code cache after a Loom update can make startup hang on a white or blank window until the app recompiles scripts
- Corrupted Chromium disk cache entries can leave the home screen, library thumbnails, or share pages partially loaded even though your recordings still exist online
- Stale GPUCache shader and render data from a graphics driver update can cause black panels, flickering controls, or missing UI elements in the recorder window
- Oversized Cache_Data folders keep old web assets and media fragments around, wasting disk space and making Loom feel inconsistent between launches
- Cached authentication and API responses can fall out of sync with Loom's current web app, producing endless spinners, failed uploads, or pages that never finish refreshing
- Removing old cache files forces Loom to fetch fresh frontend assets, which often fixes broken buttons, layout glitches, and embedded pages that stop responding
What gets cleaned
Cache paths Kudu targets
Windows
%AppData%/Loom/Cache/Cache_Data |
%AppData%/Loom/Code Cache |
%AppData%/Loom/GPUCache |
macOS
~/Library/Application Support/Loom/Cache/Cache_Data |
Linux
~/.config/Loom/Cache/Cache_Data |
Frequently asked
Common questions about Loom
Related cleaners
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.