Apps
Loom
Built on Electron, Loom stores Chromium disk cache entries in Cache/Cache_Data for web content used by its recorder and library views, along with V8 Code Cache files and GPUCache data on platforms where those folders exist. These caches speed up loading the app shell, thumbnails, previews, and hardware-accelerated rendering, but they can become stale after app or graphics driver changes. Kudu removes Loom's temporary Chromium cache files, Electron V8 code cache, and GPU cache without touching recordings, account sign-in, workspace data, or app settings.
Why clean Loom?
- Corrupted Chromium disk cache entries can leave Loom's Home or Library view stuck on blank panels, missing thumbnails, or endlessly spinning placeholders until the cache is rebuilt
- Invalidated V8 bytecode after a Loom update can make the first launch unusually slow or cause renderer windows to open white before the Code Cache regenerates
- Stale GPUCache data from a graphics driver update can break hardware-accelerated compositing, showing black preview areas, flickering windows, or choppy interface animations
- Cached web assets for Loom's embedded app can get out of sync with the current backend, causing buttons like upload, share, or open library to do nothing until old files are removed
- An oversized Cache_Data folder can consume hundreds of megabytes with old HTTP responses and media fragments, which users notice as Loom taking far more disk space than expected
- Damaged cache entries can trigger repeated reloads of the recorder or library web views, leading to sign-in loops, partial page rendering, or a window that never fully finishes loading
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.