T3 Code Partition Performance Caches
T3 Code stores per-partition performance caches inside its Partitions folders for preview and embedded web content, including Chromium disk cache entries, GPUCache data, Code Cache V8 bytecode, and shader-related blobs. These files exist to speed up reloads, script execution, and graphics initialization across partitioned sessions, including newer v2 profiles, but they can become invalid after app, runtime, or graphics driver changes. Kudu removes only those rebuildable performance caches from T3 Code partitions while leaving partition storage, login sessions, settings, and other user data intact.
Why clean T3 Code Partition Performance Caches?
- Invalidated V8 Code Cache after a T3 Code or Chromium runtime update can make previews open slowly or behave inconsistently until scripts are recompiled
- Stale GPUCache entries from a graphics driver update can cause black panels, flickering previews, or missing accelerated rendering until the shader cache is rebuilt
- Corrupted Chromium disk cache records inside a partition can lead to pages loading with broken styling, incomplete assets, or repeated hard-refresh fixes
- Oversized per-partition cache folders accumulate across old and v2 profiles, consuming noticeable AppData space and making startup scans or preview initialization feel slower
- Outdated shader blobs tied to a previous GPU or driver state can cause stutter the first time interactive previews render, especially after hardware or driver changes
- A bad cache state isolated to one partition can make only certain workspaces or preview sessions fail to load correctly while the rest of T3 Code seems normal
- Resetting these caches is a low-risk way to clear rebuildable performance data without deleting partition cookies, local storage, sessions, saved projects, or account information
Cache paths Kudu targets
Windows
%AppData%/t3code/Partitions |
%AppData%/t3code-v2/Partitions |
Common questions about T3 Code Partition Performance Caches
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.