# Can I delete all the log files on my Mac?

Is it safe to delete? · Library and system · Updated 21 November 2026. By Mohit Nippanikar, who makes SiftMac.

## The short answer

- **Yes, your old ones.** Log files record what apps and installers did, and once they’re a week or so old nobody reads them unless something has gone wrong. Clearing old files from your own `~/Library/Logs` is harmless.
- **What it costs you:** the history you’d want when chasing a problem. Keep recent logs, and any report a developer has asked you for.
- **Does it come back?** New logs appear as apps keep writing; the old ones are gone for good. “All logs” isn’t something you can or need to delete: macOS’s main log is managed by macOS, which trims it itself.
- SiftMac’s verdict: Safe

## 1. What it is

A Mac keeps logs in several places, and they aren’t all the same kind:

- **`~/Library/Logs`**: text logs apps write for your account, one file or folder per app, plus your crash reports in `DiagnosticReports`.
- **`/Library/Logs`**: logs from installers, background services and apps that run for every account, with the system’s own `DiagnosticReports`.
- **`/private/var/log`**: older-style system logs such as `install.log` and `system.log`. macOS rotates these itself, compressing old ones and capping how much it keeps.
- **The unified log**: since macOS 10.12, most messages from macOS and apps go into a compressed store macOS keeps in `/private/var/db/diagnostics`, not into text files. You read it with the Console app or the `log` command.

Apple describes `Library/Logs` as the place for log files of the console and system services, which you can also read in the Console app.

## 2. Where they are

```
~/Library/Logs
/Library/Logs
/private/var/log
```

Console gathers them in one window: open it from Applications › Utilities and look under Reports. An administrator sees the system’s reports as well as their own; other accounts see only theirs.

## 3. How big they get

Measure your own logs, biggest last:

```
du -sh ~/Library/Logs/* 2>/dev/null | sort -h | tail -10
```

For the system-wide folders, add `sudo`: `sudo du -sh /Library/Logs /private/var/log`. A single file that keeps growing by gigabytes means one app or service is stuck logging the same thing; update or remove that app, or the file just fills up again.

## 4. How to delete old logs safely

1. Quit the app whose logs you’re clearing, so it isn’t writing to them.
2. In Finder, open `~/Library/Logs` with Go › Go to Folder and move old files, or a whole app’s folder, to the Trash. Leave the `Logs` folder itself.
3. For reports, use Console: select one under Reports and choose File › Move to Trash.
4. Empty the Trash.

In Terminal, first list the files in your own logs that haven’t changed for over a week, then delete exactly those:

```
find ~/Library/Logs -type f -mtime +7 -print
find ~/Library/Logs -type f -mtime +7 -delete
```

Leave `/Library/Logs` and `/private/var/log` to macOS unless one file there has run away; then remove that file in Finder once you’ve dealt with whatever writes it. Don’t try to clear the unified log: Apple says that when its store passes a set size, macOS purges the oldest messages to make room.

## 5. What happens afterwards

- Apps start new log files the next time they run, and work exactly as before.
- Crash reports you’ve deleted can’t be sent to a developer later, so keep the ones you’ve been asked for.
- Console lists fewer old reports, which makes a new one easier to spot.
- How much space comes back depends on your apps; the `du` command showed you before you started.

## Questions

### Can I delete all logs on a Mac?

Your own old logs, yes. Not every log: the unified log, where macOS and most apps record events, is managed and trimmed by macOS, and the text logs in `/private/var/log` are rotated automatically. Deleting those by hand gains little and loses the record you’d need to diagnose a fault.

### Is it safe to delete DiagnosticReports?

Old crash reports, yes. [What’s in DiagnosticReports](https://siftmac.com/safe-to-delete/diagnostic-reports) explains which ones to keep.

### Do logs slow down a Mac?

No. They take space, and only a log that grows without stopping deserves attention, as a sign that something keeps failing.

### Can I delete install.log?

Leave it. macOS rotates and compresses it by itself, and it’s the record you’ll want if an update or an installer goes wrong.

## How SiftMac handles it

Its Old logs category goes through your `~/Library/Logs` folder by folder and picks only files older than a week, since something may still be writing newer ones. It deletes them rather than shelving them, lists crash reports as their own line, and doesn’t touch `/Library/Logs`, `/private/var/log` or macOS’s unified log.

Download: https://siftmac.com/SiftMac.dmg (scanning is free, and so is the first 2 GB of cleaning).

## Sources

- [Apple: View reports in Console on Mac](https://support.apple.com/guide/console/cnsl664be99a/mac)
- [Apple Developer: Logging (the unified logging system)](https://developer.apple.com/documentation/os/logging)
- [Apple Developer: Generating log messages from your code (storage limits)](https://developer.apple.com/documentation/os/generating-log-messages-from-your-code)

## Related

- [Is it safe to delete crash reports in DiagnosticReports?](https://siftmac.com/safe-to-delete/diagnostic-reports)
- [Is it safe to delete ~/Library/Caches on a Mac?](https://siftmac.com/safe-to-delete/library-caches)
- [How to clear System Data on a Mac, safely](https://siftmac.com/guides/system-data-on-mac)
- [How to clear cache on a Mac: app, browser and system caches](https://siftmac.com/guides/how-to-clear-cache-on-mac)

Canonical: https://siftmac.com/safe-to-delete/library-logs
