How to Delete Log Files on Mac and Reclaim Hidden Gigabytes

If you've ever poked around in Finder and wondered why your Mac's "System Data" category is ballooning, log files are often a major culprit. Knowing how to delete log files on Mac safely — and which ones to leave alone — can free up gigabytes without putting your system at risk. This guide covers exactly where logs hide, which are safe to purge, and how to do it right.

Where Mac Log Files Actually Live

macOS scatters logs across several locations. The three main areas to know are:

1. ~/Library/Logs (User Logs)

This is your per-user log folder. Every app you run can write crash reports, activity logs, and diagnostic output here. Common culprits include browsers, creative apps like Adobe products, and development tools. It's not unusual for this folder to accumulate several gigabytes over months of normal use.

Open it in Finder by pressing Command + Shift + G and typing:

~/Library/Logs

2. /var/log (System Logs)

macOS and its daemons write low-level system logs here — things like the install log, system log rotations, and kernel messages. These are owned by root and require elevated permissions to delete.

/var/log

3. ~/Library/Logs/DiagnosticReports (Crash Reports)

Every time an app or a system process crashes, macOS writes a .crash or .ips report here. These files are invaluable if you're debugging a recurring crash, but old ones from apps you deleted long ago serve no purpose.

~/Library/Logs/DiagnosticReports

4. /Library/Logs (System-Wide Application Logs)

Some apps that run system-wide — installers, backup tools, server software — write logs here instead of your user Library. Requires admin access to manage.

/Library/Logs

Why Mac Log Files Can Take Up So Much Space

Most log files start small, but a few situations cause them to balloon:

• Runaway processes: A daemon stuck in an error loop can write megabytes of log entries per hour. Multiplied over days, this becomes gigabytes.
• Verbose app logging: Developer builds of apps, or apps left in debug mode, log far more than release builds.
• Accumulated crash reports: If you've had a flaky app for months, it may have written hundreds of crash reports.
• Old installer logs: Every macOS update and app install can leave behind detailed logs that never get cleaned up automatically.

Unlike caches, macOS does not aggressively rotate or purge old logs on your behalf. The system does rotate /var/log entries, but user-facing app logs in ~/Library/Logs can persist indefinitely.

Which Log Files Are Safe to Delete on Mac

This is where most guides skip the nuance. Not all log files carry the same risk.

General rule: Logs older than 30 days that belong to apps you still use, or apps you've already deleted, are almost always safe to remove. Logs for the current day or active processes should be left alone.

How to Clear Logs on Mac Manually (Terminal)

If you're comfortable with Terminal, you can delete old log files selectively. These commands are permanent — there is no undo, so read them carefully before running.

Remove User App Logs Older Than 30 Days

find ~/Library/Logs -name "*.log" -mtime +30 -delete

This finds all .log files in your user Logs folder that haven't been modified in over 30 days and removes them. It does not touch files currently open by a running process.

Clear Old Diagnostic Reports

find ~/Library/Logs/DiagnosticReports -name "*.crash" -mtime +30 -delete
find ~/Library/Logs/DiagnosticReports -name "*.ips" -mtime +30 -delete

Remove Rotated System Log Archives (Safe)

In /var/log, rotated logs have names like system.log.0.gz. These are compressed archives of old logs and are safe to remove:

sudo find /var/log -name "*.gz" -delete
sudo find /var/log -name "*.0" -delete

You will be prompted for your admin password. Do not delete the base files like system.log or install.log — those may be actively written to.

Clear System-Wide App Logs

sudo find /Library/Logs -name "*.log" -mtime +30 -delete

Using Crumb to Clear Logs Automatically and Safely

The manual approach works, but it requires care and some comfort with Terminal. Crumb — a native macOS menu-bar cleaner — handles this automatically as part of its one-click Clean operation. What makes it particularly useful here is that it distinguishes between safe-to-purge log files and logs that are actively in use by running processes, rather than blindly deleting everything in ~/Library/Logs.

If you're unsure about a specific folder, Crumb's built-in "Is this safe to delete?" AI can explain what any log directory contains and what the risk of removing it is — without ever sending your file contents anywhere. You can download Crumb and try one cleanup free, no account required.

Logs You Should Not Delete

A few categories of logs are worth preserving:

• Recent crash reports for apps you're actively troubleshooting — if you're reporting a bug to a developer, they will ask for these.
• Logs from backup software (Time Machine, Carbon Copy Cloner, etc.) — useful to verify backups completed successfully.
• Active /var/log/system.log — the live system log; do not delete it while the system is running.
• Security logs if your Mac is managed by an employer — your IT team may rely on these for audit trails.

How Often Should You Clear Mac Logs?

For most users, clearing logs once every one to three months is sufficient. If you're a developer running many processes, or you've had an app behaving badly recently, checking monthly makes sense. There's no benefit to clearing logs more frequently than that — the space savings won't be meaningful week to week.

Conclusion

Mac log files hide across ~/Library/Logs, /var/log, and /Library/Logs, and they can quietly accumulate gigabytes over time. The Terminal commands above let you remove old logs selectively and safely. The key principle is simple: old logs from inactive or deleted apps are almost always safe to purge; logs tied to active processes or recent events are worth keeping. Clean carefully, and you'll reclaim the space without disrupting anything your system relies on.