Can I Delete ~/Library/Logs on My Mac? Yes, It's Safe
~/Library/LogsYes, you can delete the contents of ~/Library/Logs. Everything in there is diagnostic log files, and they exist only to help debug problems after the fact. No app stores settings, documents, or anything it needs to run inside this folder. If your Mac is short on space and this folder has grown large, clearing it out is one of the lowest-risk cleanups you can do.
What it is
~/Library/Logs is where apps and parts of macOS write their diagnostic logs. Every time an app starts up, hits an error, crashes, or just wants to record what it did, it can append a line to a log file here. Zoom, the Adobe apps, backup tools, background updaters: most software you run leaves some trace in this folder. macOS itself also keeps crash reports and diagnostic files in the DiagnosticReports subfolder.
The folder grows because most apps never clean up after themselves. A well-behaved app rotates its logs and caps them at a few megabytes. A chatty or buggy one can write the same warning thousands of times a day and quietly build files that reach hundreds of megabytes, sometimes several gigabytes, over months of use. An app stuck in a crash loop is a classic cause of a Logs folder that balloons overnight.
Is it safe to delete?
Deleting log files does not break anything. Apps do not read their old logs to function; they only write to them. The next time an app runs, it creates a fresh log file and carries on. The only thing you actually lose is history: if an app has been misbehaving and you were planning to send its logs to a support team, or you want to check crash reports from last week, that evidence is gone once you empty the Trash.
So the one caveat is timing. If you are in the middle of troubleshooting a specific problem, keep the logs for that app until you are done. Otherwise, clear the folder whenever you like. Diskmack flags ~/Library/Logs automatically and clears it the safe way, contents only, folder left in place.
How to check its size
In Finder: In Finder, choose Go > Go to Folder (or press Cmd+Shift+G), type ~/Library/Logs and press Return. Select everything inside with Cmd+A, then press Cmd+Option+I to see the combined size in the inspector window.
In Terminal:
du -sh ~/Library/LogsThe ~ expands to your home folder, so this measures /Users/yourname/Library/Logs.
How to clean it
- In Finder, choose Go > Go to Folder, or press Cmd+Shift+G.
- Type ~/Library/Logs and press Return.
- Press Cmd+A to select everything inside the folder.
- Press Cmd+Delete to move it all to the Trash.
- If a file refuses to move because it is in use, skip it. An app is writing to it right now. Quit that app and try again, or leave the file for next time.
- Empty the Trash to actually reclaim the space.
Delete the contents, not the Logs folder itself. The folder should stay where it is so apps have a place to write new logs.
Will it come back?
Yes, it comes back. New logs accumulate as apps run, so the folder starts refilling the moment you use your Mac again. Normally that regrowth is slow, a few megabytes here and there, and you will not need to think about it for months. If the folder balloons again within days, that is a signal, not bad luck: some app is logging far too much. Sort the folder by size, find the biggest subfolder, and update or fix that app instead of deleting the same gigabytes every week.
Common questions
Will deleting logs break any of my apps?
No. Logs are write-only from the app's point of view. Apps never depend on old log files to launch or run; they just start a fresh file the next time they have something to write.
What about /Library/Logs, without the tilde?
That is the system-wide version of the same folder, shared by all users on the Mac. Its contents are also just logs, but clearing it asks for your admin password, and the space you get back there is often smaller than in your own ~/Library/Logs. Start with the user folder.
Should I keep logs if something on my Mac is acting up?
Yes. Logs are the main evidence a support team or developer will ask for. Hold off on clearing the logs for the misbehaving app until the problem is solved, then delete freely.
Why is my Logs folder several gigabytes?
Usually one app, not many. An app that logs verbosely without rotating its files, or one stuck crashing and relaunching, can generate huge files fast. Open ~/Library/Logs, sort by size, and the offender will be obvious.