Apps
JetBrains IDE Logs
JetBrains IDEs write rotating log files, thread dumps, freeze reports, crash diagnostics, Java error logs, and plugin diagnostic output under the JetBrains folders in LocalAppData. These files are created by the IntelliJ Platform and bundled JetBrains Runtime to record indexing stalls, UI freezes, plugin exceptions, VFS watcher events, and startup failures, but old settled diagnostics often accumulate long after the problem is gone. Kudu removes diagnostic logs older than one week while leaving projects, IDE settings, caches, account data, and passwords untouched.
Why it matters
Why clean JetBrains IDE Logs?
- Weeks of idea.log rotations, thread dumps, and plugin exception traces can quietly consume hundreds of megabytes, and users usually notice only when the C: drive starts running low
- Repeated startup failures or plugin crashes generate fresh hs_err_pid logs and freeze reports every session, so old diagnostics pile up and make the JetBrains folders look abnormally large
- Very large log directories slow down manual troubleshooting because recent errors are buried under stale indexing, VFS, and updater messages from problems that were already resolved
- Long-running IDE installs that have seen many plugin updates often keep obsolete diagnostic output for old plugin versions, which confuses support checks when users open the latest logs
- Settled thread dumps and performance snapshots from past UI freezes are useful only temporarily, and keeping them indefinitely wastes disk space without improving indexing or editor behavior
- After antivirus, file watcher, or JBR issues have been fixed, the old warning spam remains on disk and users may mistake historic errors for current breakage when reviewing logs
What gets cleaned
Cache paths Kudu targets
Windows
%LocalAppData%/JetBrains |
Frequently asked
Common questions about JetBrains IDE Logs
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.