Delete Log Files on Mac: What to Keep and What to Remove

Deleting logs is worth considering when you have found a large, identifiable log, not simply because Mac storage is low. A log records what happened, and removing it discards evidence that may explain a crash or repeated error. Measure the folders first, keep reports for unresolved problems, and change one thing at a time.

Find the Log Before Deciding What to Remove

Apple's Library directory reference identifies Logs as a place for diagnostic records, not a folder to remove wholesale. Its Console guide distinguishes app reports, system reports and the legacy system log.

Apple engineers also point to the user DiagnosticReports folder when investigating crashes. The exact location of a report is better evidence than a guessed filename: select it in Console and use the documented option to reveal it in Finder.

The unified log uses compressed binary storage. Emptying a text log folder does not therefore erase all logging on a Mac. Leave unified-log storage under system management during ordinary housekeeping.

Measure Without Deleting Anything

The following Terminal commands only report sizes. Apple's published du manual documents the summary and readable-size options.

du -sh "$HOME/Library/Logs" /Library/Logs /private/var/log
du -sh "$HOME/Library/Logs/DiagnosticReports" /Library/Logs/DiagnosticReports

The second line measures children already included in the first, so do not add all five values together. These totals are occupied space, not a promise of safely reclaimable space.

A missing location is not a fault to repair. If access is denied, the measurement is incomplete, not zero. Do not change permissions or add administrator privileges just to make a bigger cleanup total. Use Console to inspect a report you can access, or leave that location alone.

If logs occupy only a small part of the space you need, stop here. There is no verified typical saving that applies to every Mac. For the different question of regenerable data, use which Mac caches are safe to delete and how to clear cache on Mac, rather than treating logs as caches.

Remove One Old Report and Keep a Recovery Window

Start with an old report whose problem is resolved. Apple's Console guide documents viewing a report and moving a selected report to the Trash, so there is no need to erase a directory. Before removing evidence for an unresolved problem, share the relevant report with the person investigating it, or keep a separate copy.

1. Note the report's app, date, location and size, then read enough to identify the incident.
2. If it belongs to an app you can quit normally, quit that app before changing its files.
3. Move only the unwanted report to the Trash, leaving the Logs folder and neighboring files intact.
4. Reopen the app, repeat the action you care about, and check for the same error and new reports.

Keep the item in the Trash while checking. Restoration from the Trash is available only while the item remains there, and the move alone is not reclaimed disk space. Apple's Trash instructions explain permanent removal and returning an item. If you need it back, quit the related app and restore it before continuing.

A new log cannot reconstruct the old incident. Even when a cache can rebuild from available sources, future logging does not restore deleted diagnostic history. Do not remove unknown lock files, databases or settings simply because they sit next to logs.

When a Log Keeps Growing

Treat repeated growth as a diagnostic clue. Record the same file's size and modification time, quit its app normally, then compare while the app is closed and after reopening it. This is a controlled comparison, not proof that every writer belongs to the app named in the folder.

If growth follows a repeatable action, keep a relevant excerpt and record the app version and trigger for its developer. Check the vendor's instructions before changing a logging setting. Do not stop system services or repeatedly erase their output to hide the symptom.

Deleting a large log can remove accumulated records, but it does not establish why those records were written. If the same error keeps returning, addressing that error is the useful next step.

Where Mole Fits

Mole Mac's Clean view has a Logs section that lists eligible individual files under ~/Library/Logs, rather than selecting entire app log folders. Eligible stale files use a 7-day cutoff and are selected by default when Mole can read them right away. Recently modified log files of at least 50 MiB are separate, unchecked review items: selecting them empties the file in place, with no Trash recovery.

Under System Data, eligible System Logs and Crash Reports rows cover /private/var/log and /Library/Logs/DiagnosticReports. With helper access they are selected by default, while rows shown without it are unchecked for review. Unified Logs is also unchecked for review and permanently erases stored diagnostic history if selected, rather than moving it to the Trash.

PathGuard retains protected app state, including Mole's own logs. It does not blanket-protect every log: /private/var/log is an explicit allowed root, while the unified-log action uses a dedicated system helper. Unchecked means review before selecting, not protected from removal.

FAQ

Can I Delete Everything in Library/Logs?

Do not empty either parent folder. Identify an old report or app log first, preserve evidence for unresolved problems, and remove only the file you have chosen.

Will Deleting Logs Free Much Space?

Measure first. A large individual log can matter, but small measured totals cannot explain a much larger storage shortage, and there is no universal saving to promise.

Will Deleted Logs Come Back?

Future activity can produce new records, but it does not recreate deleted history. If the same file grows again, investigate the writer and repeated error rather than scheduling more deletion.