What Are System Logs on Mac (and Is It Safe to Delete Them)

You're poking around your Library folder trying to free up space, and you hit a wall of files with names like install.log, system.log, and a folder of .diag bundles from dates you don't remember. They look like junk. They sound like junk — "logs," nobody needs logs, right?

Mostly true. But logs are also the single most useful thing on your Mac when something breaks, and clearing them is one of those cleanup tasks that's more ritual than result. Let me make sure you do it for the right reasons.

What logs actually are

A log is just an app or the system jotting down what it did, with a timestamp. "Started at 09:14." "Failed to reach the update server at 09:31." "Crashed, here's the memory dump." macOS and every app on it write these constantly, for two reasons:

• For you (or a support tech) to debug problems. When an app keeps quitting, the log is where the why is. That's the whole reason the Console app exists.
• For the system to report crashes to Apple and developers. Those .diag, .panic, and .ips files are diagnostic reports — the thing that pops up "app quit unexpectedly, send to Apple?"

They're append-only diaries. They grow over time, they're safe to delete in the sense that deleting a log never loses you a document or a photo, and — this is the key part — they immediately start growing again, because your Mac can't stop taking notes.

Where they live

Three main spots:

• ~/Library/Logs/ — per-user logs, the app-specific ones. This is the one you'll actually see filling up.
• /Library/Logs/ — system-wide logs (installer logs, server-ish stuff).
• /var/log/ and /private/var/log/ — the OS's own logs, plus asl/log store. Mostly managed by macOS itself.

Crash and diagnostic reports live in ~/Library/Logs/DiagnosticReports/ and /Library/Logs/DiagnosticReports/.

To reach the user one: Finder → Go → hold Option → Library → Logs.

The honest truth: this is rarely your space problem

Here's where I'll talk you out of a mission. On a normal Mac, the Logs folder is tens or a couple hundred megabytes. Deleting it is fine, but it will not meaningfully change your free space, and the folders refill within days. If you're hunting gigabytes, logs are almost never the culprit — a real disk usage analysis will point you at the actual fat (one huge folder, browser caches, old iOS simulators), not this.

So when is clearing logs worth doing?

• A specific app is misbehaving and spewing — a runaway logger can balloon one file to multiple GB. If you open ~/Library/Logs, sort by size, and one app's log is absurdly huge, that's a genuine (if small) win and a hint the app has a bug.
• You're troubleshooting and want a clean slate — deleting old logs so the next crash's log is unambiguous.
• DiagnosticReports has hundreds of old crash files — safe to clear; they've already been sent or ignored.

The one thing I'd not do: delete logs right before contacting support about a recurring issue. You'll erase the evidence that would've explained it. Grab the relevant log first, then clean.

How to clear them (two ways)

By hand, for the user folder: open ~/Library/Logs, and you can select-all and move to Trash. macOS will just recreate the folder structure as apps log again. For DiagnosticReports, same idea — those are disposable once you don't need them.

Don't bother trying to purge the system /var/log store manually; modern macOS manages that through the unified logging system, which auto-rotates and caps its own size. There's a log command with retention settings, but you almost never need it and messing with it is not a cleanup task, it's a sysadmin task.

Through a cleaner, if you'd rather not sort Library folders by size at all: the System Logs cleanup in CleanDiskGo sweeps the log and diagnostic-report locations in one pass and shows you the size breakdown first — so you can see whether logs are even worth your time before deleting anything. (Spoiler: it's usually a modest number. That's fine. It's an honest number.)

The value here isn't the megabytes. It's glancing at the list and confirming logs aren't your problem, so you can go fix what actually is.

The bigger picture

Logs are the classic "looks like the mess, isn't the mess." Clear them if they're genuinely huge or you're debugging, but if your real goal is free space, spend your energy where the space actually is: junk and caches, leftover files from uninstalled apps, and the giant folders a disk scan reveals. Your system.log was never the villain.