Are Mac Log Files Safe to Delete?

Updated July 2026 · 3 min read

Short answer: logs in your user folder are safe to delete, system logs mostly manage themselves, and a single log that has grown to several gigabytes is a symptom, not the disease. Here's where Mac logs live, how big is normal, and which ones you can clear without consequences.

Where logs live — and how big is normal

~/Library/Logs — logs written by the apps you run: crash traces, sync diaries, updater output. This is the folder most cleanup advice is really about.
/Library/Logs — the system-wide equivalent, used by background services and apps installed for all users.
/var/log — the operating system's own logs (it's hidden; use Finder's Go → Go to Folder to look). macOS rotates and compresses these automatically with newsyslog, so they rarely grow.
/var/db/diagnostics — the unified logging store that Console reads. It's system-managed with its own size limits. Leave it alone.

On a healthy Mac, all of this together is usually tens of megabytes to a few hundred. If Storage settings shows your disk is full, logs are almost never the reason — unless one has gone rogue, which is easy to check.

Measure before you delete

These commands only read sizes; they change nothing:

# Total size of each log location
du -sh ~/Library/Logs /Library/Logs
sudo du -sh /var/log

# The biggest individual logs in your user folder
du -sh ~/Library/Logs/* | sort -rh | head

If the totals come back in megabytes, there's nothing worth deleting — spend your effort on caches, snapshots, or old backups instead. If one entry is huge, keep reading.

What's safe to delete

~/Library/Logs: safe. Delete any or all of its contents. Apps recreate their logs on next launch; you lose nothing except old diagnostic history. Delete via Finder (drag to Trash) rather than rm — that keeps it reversible until you empty the Trash. The DiagnosticReports subfolder in the same location holds old crash reports and is equally safe to clear.
/Library/Logs: safe, with admin rights. Same idea, but you'll be asked for your password. Skip anything belonging to security or backup software you actively rely on if you might need its history.
/var/log: leave it. The system rotates these itself, daemons hold some of them open, and yanking files out from under them causes confusion for near-zero space gain.
/var/db/diagnostics: don't touch. It's the unified log database, not a folder of disposable text files. macOS caps its size on its own.

A multi-gigabyte log means an app is misbehaving

When a single log file hits gigabytes, some process is writing the same error thousands of times a minute — typically a background helper stuck in a crash-and-retry loop. Deleting the file buys you space for a day; the log will regrow until you fix the writer. Open the file in Console (or any text editor) and look at what's repeating, then update, reinstall, or remove that app. The filename itself usually names the culprit, so you rarely have to dig far to know which app to blame.

While you're under the hood

Poking around ~/Library is power-user territory. Mainspring makes the rest of it easy — 90+ hidden macOS settings as labelled, reversible toggles instead of scattered defaults commands.

Try Mainspring free →

Signed & notarized by Apple · 1-day free trial · $29 once

Logs are a small slice of System Data

If you came here because the Storage pane shows a giant "System Data" bar, logs are one of its smallest ingredients. Caches, Time Machine snapshots, and old device backups are the usual heavyweights — our guide to shrinking System Data storage walks through them in order of payoff.