Storage CleanerIs it safe to delete ~/Library/Logs on Mac?
Short answer: yes. ~/Library/Logs holds text logs and crash reports that apps write for troubleshooting. Nothing needs them to run, and apps start new logs when they next write one. It's rarely big (17 MB on our test Mac), unless an app is logging in a loop, so check the largest files first.
What's inside
| What | Where | Safe to delete? |
|---|---|---|
| App logs | ~/Library/Logs/<App> | Yes |
| Crash and hang reports | ~/Library/Logs/DiagnosticReports | Yes, unless you're about to send one to a developer |
| Xcode and simulator logs | ~/Library/Logs/CoreSimulator, ~/Library/Developer/Xcode/…/Logs | Yes |
| System-wide logs | /Library/Logs, /private/var/log | Leave to macOS; it rotates them itself |
| Unified log | log show (not files you manage) | Managed by macOS; nothing to delete |
Find a runaway log
du -sh ~/Library/Logs
find ~/Library/Logs -type f -size +100M -exec ls -lh {} \; 2>/dev/nullA single log of several GB usually means an app is stuck in an error loop. Delete the file, then update or reinstall the app, or it will grow back.
Clear it
In Finder, press ⇧⌘G, go to ~/Library/Logs and move what you don't need to the Trash. Keep the Logs folder itself.
Logs are small; developer tools aren't. If your Mac is full, logs are rarely the cause. Storage Cleaner finds the big ones: AI models, Xcode data, node_modules and caches, with Undo.
Try Storage Cleaner freeFrequently asked
Will deleting logs break anything? No. Apps create new log files the next time they write one.
Should I delete crash reports? Only after you've sent any you need to a developer; they help diagnose crashes.
Are logs part of System Data? Yes, a small part. See why System Data is so large for the big parts.
Related: Is ~/Library/Caches safe to delete? · What's safe in ~/Library/Developer.