T3 Code Partitions
T3 Code stores per-partition Chromium preview caches under its Partitions directory so isolated webviews can keep their own compiled and temporary browser data. These partitions accumulate items such as Code Cache V8 bytecode, GPUCache shader and command caches, Service Worker CacheStorage data, network cache entries, and IndexedDB or Local Storage used by preview panes and embedded web content. Kudu removes only the disposable preview-partition cache files that can go stale or grow unexpectedly, while leaving partition sessions, storage, workspace state, accounts, settings, and other user data intact.
Why clean T3 Code Partitions?
- Invalidated Code Cache bytecode after a T3 Code or embedded Chromium update can make preview panes open slowly or show a one-time lag while scripts recompile
- Stale GPUCache data from an older graphics driver can cause blank embedded previews, black panes, or choppy rendering until Chromium rebuilds the cache
- Corrupted network cache entries inside a partition can leave docs, auth pages, or extension-hosted previews stuck loading old content even after a hard refresh
- Overgrown Service Worker CacheStorage and HTTP cache files can make the Partitions folder consume hundreds of megabytes or more, especially after repeated previewing of large web apps
- Broken partition cache state can produce white screens, missing styles, or JavaScript errors in web-based preview tabs even though the underlying project files are fine
- SQLite databases inside partition storage can become page-fragmented over time; VACUUM rewrites the file to compact free pages without deleting rows, which helps when cache databases stay large after content was removed
Cache paths Kudu targets
Windows
%AppData%/t3code/Partitions |
Common questions about T3 Code Partitions
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.