Apps

Termius Beta

Built on Electron, Termius Beta stores Chromium disk cache entries, V8 Code Cache bytecode, GPUCache data, DawnCache shader and pipeline blobs, and Crashpad crash-report files under its Windows profile. These files speed up rendering the terminal UI, web-based account screens, and GPU-accelerated interface elements, but they can become stale after a beta update, Chromium runtime change, or graphics driver change. Kudu removes only those temporary caches and old crash-report artifacts while leaving saved hosts, credentials, synced data, local databases, sessions, and other storage untouched.

Why clean Termius Beta?

  • Invalidated V8 Code Cache after a Termius Beta update can make the first launch feel unusually slow while the app recompiles interface scripts
  • Stale Chromium Cache_Data entries can cause broken styling or incomplete account and settings pages, showing blank panels or UI elements that never finish loading
  • GPUCache created against an older graphics driver can conflict after a driver update, leading to black flashes, missing text, or sluggish redraws in the terminal window
  • Outdated DawnCache shader and pipeline blobs can cause stutter when opening hardware-accelerated views, especially right after a beta build or GPU change
  • A swollen browser cache can consume hundreds of megabytes over time, making the Termius Beta profile folder much larger than expected even though hosts and sessions have not grown
  • Crashpad report files accumulate after repeated crashes or failed starts, wasting disk space and leaving behind old diagnostic dumps long after the underlying issue is fixed
What gets cleaned

Cache paths Kudu targets

Windows

%AppData%/Termius Beta/Cache/Cache_Data
%AppData%/Termius Beta/Code Cache
%AppData%/Termius Beta/GPUCache
%AppData%/Termius Beta/DawnCache
%AppData%/Termius Beta/Crashpad/reports
Frequently asked

Common questions about Termius Beta

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.