SystemRequires admin/root
System Logs
macOS writes system-wide diagnostic and service logs under /Library/Logs, including plain-text daemon logs, crash and spin reports, installer logs, and app support logs created by background services and components running for all users. These files exist to help troubleshoot launches, updates, hardware events, and system services, but they can accumulate long after the original issue is gone; Kudu removes stale log files from /Library/Logs without touching user documents, accounts, settings, or passwords.
Why clean System Logs?
- Runaway crash or daemon logs can grow into gigabytes after a repeating failure, and users usually notice missing free space and a constantly expanding /Library/Logs folder
- Old installer and update logs keep piling up across macOS and app updates, making disk usage look unexplained even though the updates finished long ago
- Excessive logging from a misbehaving background service increases write activity, which can show up as persistent disk churn, warmer laptops, and reduced battery life until the underlying issue is fixed
- Large collections of crash, spin, and diagnostic reports make manual troubleshooting harder because current failures are buried under obsolete reports from months earlier
- Verbose service logs often preserve errors that no longer apply after a patch or reconfiguration, leading admins to chase stale messages instead of the present problem
- Some third-party system components write rotating logs poorly and leave behind old archives, so cleaning removes abandoned log history while leaving the actual software, settings, and user data intact
What gets cleaned
Cache paths Kudu targets
macOS
/Library/Logs |
Frequently asked
Common questions about System 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.