Browsers

Thorium

Built on Chromium, Thorium stores a browser disk cache for HTTP resources, GPUCache data for Skia and WebGL shader state, Code Cache bytecode for JavaScript and WASM, and media caches for streamed audio and video under its User Data profile. These files speed up page loads and rendering, but they can become stale after browser, site, or graphics driver changes and start causing broken page assets, playback glitches, or rendering oddities. Kudu removes Thorium's disposable cache directories while leaving bookmarks, saved passwords, cookies, history, extensions, and other personal profile data untouched.

Why clean Thorium?

  • Stale HTTP cache entries can serve old CSS, JavaScript, or images after a site update, which shows up as broken layouts, missing icons, or pages that only work after a hard refresh
  • Invalidated Code Cache bytecode after a Thorium update can make sites feel stuck on first load, with blank sections or delayed interactivity until scripts are recompiled
  • Old GPUCache data from a previous graphics driver version can conflict with Chromium's rendering pipeline, causing black boxes, flickering, or corrupted WebGL content until the cache is rebuilt
  • Oversized media cache files can keep damaged partial video or audio segments around, leading to buffering loops, failed seeks, or streams that restart unexpectedly
  • A bloated disk cache can consume several gigabytes in the profile folder and make profile backups, roaming, or SSD space usage noticeably worse
  • Corrupted cached service worker and resource data can leave web apps loading outdated offline assets, so sites open with the wrong version or fail to sync until local cache state is cleared
What gets cleaned

Cache paths Kudu targets

Windows

%LocalAppData%/Thorium/User Data

macOS

~/Library/Application Support/Thorium

Linux

~/.config/thorium
Frequently asked

Common questions about Thorium

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.