Claude Logs
Claude Desktop and Claude Code write diagnostic log files to platform log folders and to ~/.claude/logs and ~/.claude/debug so crashes, extension failures, renderer errors, CLI session problems, and network diagnostics can be inspected later. These folders typically contain rotating plain-text log streams, error traces, debug output, and crash-related records that accumulate over time but are not required for your saved conversations or project content. Kudu removes only Claude log files older than one week, leaving conversations, projects, file history, session data, settings, and account information untouched.
Why clean Claude Logs?
- Verbose debug logging left enabled after troubleshooting can grow into hundreds of megabytes or more, and users usually notice Claude taking unexpected disk space even when they have not added new conversations or files
- Large accumulated renderer and backend logs make manual diagnosis harder because current startup or sync errors are buried in old traces, so the symptom is opening a log folder full of stale entries that obscure the real problem
- Repeated crash loops can produce many timestamped stack traces and rolling log files, leaving behind disk churn and a constantly growing Logs folder long after the original bug has passed
- Old CLI debug logs in ~/.claude/debug and ~/.claude/logs can expose obsolete warnings from previous versions, causing users to chase errors they no longer have when reviewing command output or support bundles
- On systems with small SSDs or roaming profiles, ever-growing diagnostic logs can contribute to low-space warnings, slower profile sync, or backup jobs copying large numbers of irrelevant text files
- After a Claude Desktop or Claude Code update, historical logs often reflect previous builds and dependency states, so users may see outdated Electron, renderer, or network errors that no longer match the current installation
- Cleaning week-old logs reduces clutter without affecting conversations, projects, file history, or session state, so users regain space and keep only recent diagnostics that are actually useful for troubleshooting
Cache paths Kudu targets
Windows
%AppData%/Claude/logs |
%LocalAppData%/Claude/Logs |
%LocalAppData%/Packages/Claude_pzs8sxrjxfjjc/LocalCache/Local/Claude/Logs |
~/.claude/debug |
~/.claude/logs |
macOS
~/Library/Logs/Claude |
~/.claude/debug |
~/.claude/logs |
Linux
~/.claude/debug |
~/.claude/logs |
Common questions about Claude Logs
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.