Apps
JetBrains IDE Logs
JetBrains IDEs write rotating log files, thread dumps, fatal error reports, performance snapshots, and other diagnostic output under the JetBrains folders in LocalAppData to record indexing activity, plugin exceptions, UI freezes, and JVM events. Those files are meant for troubleshooting and can accumulate across updates, crashes, and repeated background tasks long after the underlying problem is gone. Kudu removes settled JetBrains log and diagnostic files older than one week, without touching projects, IDE settings, plugins, accounts, or saved passwords.
Why clean JetBrains IDE Logs?
- Repeated indexing, Gradle sync, and plugin startup errors can generate large idea.log archives that quietly consume gigabytes, which users usually notice only when C: runs low on free space
- Crash loops and forced terminations leave behind multiple thread dumps and fatal error reports, so the diagnostics folder keeps growing even after the IDE starts working normally again
- Verbose logging enabled for troubleshooting can continue writing detailed VFS, Kotlin, Maven, or debugger traces long after the issue is fixed, leading to unusually heavy disk activity while the IDE is open
- Old log rollover files make it harder to find the current exception or freeze event, so users searching for today's problem end up sifting through stale stack traces from previous versions
- Plugin exceptions recorded on every startup can produce a new burst of diagnostic output each session, and the visible symptom is a sluggish launch paired with ever-expanding log archives
- After updates, obsolete logs from earlier IDE builds and retired plugins remain on disk even though they no longer help the running version, leaving behind clutter with no effect on your code or settings
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.