Apps
T3 Code
Built on Electron, T3 Code stores several Chromium runtime caches under its profile on Windows to speed up the editor UI and embedded web content. These include HTTP disk cache entries in Cache_Data, V8 compiled JavaScript bytecode in Code Cache, GPUCache metadata, DawnGraphiteCache and DawnWebGPUCache shader and pipeline blobs, and Shared Dictionary cache data used for compressed web responses. Kudu removes only those disposable caches so corrupted or outdated renderer data can be rebuilt, while preserving workspaces, sessions, settings, accounts, and project files.
Why clean T3 Code?
- Stale V8 bytecode in Code Cache after a T3 Code update can make the first launch unusually slow or leave panes blank until scripts are recompiled
- Corrupted HTTP cache entries in Cache_Data can cause the built-in web interface to load old assets, leading to missing icons, broken styling, or buttons that stop responding
- GPUCache data invalidated by a graphics driver update can trigger black windows, flickering panels, or sluggish redraws until Chromium rebuilds the cache
- Outdated DawnGraphiteCache or DawnWebGPUCache shader blobs can cause stutter, rendering glitches, or repeated pauses when hardware-accelerated UI elements are shown
- An overgrown Shared Dictionary cache can waste hundreds of megabytes and sometimes causes content decoding mismatches that show up as incomplete or malformed app views
- Repeated cache churn from many updates and embedded web revisions can leave T3 Code using far more profile disk space than expected even though no user projects were added
What gets cleaned
Cache paths Kudu targets
Windows
%AppData%/t3code/Cache/Cache_Data |
%AppData%/t3code/Code Cache |
%AppData%/t3code/GPUCache |
%AppData%/t3code/DawnGraphiteCache |
%AppData%/t3code/DawnWebGPUCache |
%AppData%/t3code/Shared Dictionary/cache |
Frequently asked
Common questions about T3 Code
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.