# What is logd, and how much space do Mac logs take?

What is this process? · Updated 22 November 2026. By Mohit Nippanikar, who makes SiftMac.

## The short answer

- **It’s macOS’s logging service.** `logd` collects log messages from every process on the Mac, compresses them and keeps them in memory or on disk. Console and the `log` command read what it stores.
- **When it’s busy:** when some process is logging heavily. `log stats --overview` names the processes writing the most, which is where to look.
- **Space:** the store lives in `/private/var/db/diagnostics`, with format data in `/private/var/db/uuidtext`. Apple says that when the store passes a set size, macOS purges the oldest messages, so it doesn’t grow forever.

## 1. What logd is

`logd` is `/usr/libexec/logd`, a root daemon started by launchd from `/System/Library/LaunchDaemons/com.apple.logd.plist`. Its manual page calls it the part of the unified logging system that handles historical data: processes write log entries into memory pages they share with logd, and logd reads them, combines and compresses them, then keeps them in a ring buffer in memory or writes them to persistent storage, depending on policy.

The unified log has been macOS’s main log since macOS 10.12, replacing most of the old text files. It isn’t the same as the text logs apps write to [~/Library/Logs](https://siftmac.com/safe-to-delete/library-logs) or the [crash reports](https://siftmac.com/safe-to-delete/diagnostic-reports) in `DiagnosticReports`; those are separate files logd doesn’t manage.

What gets kept depends on the level. Apple’s documentation says debug messages stay in memory only, info messages reach disk only when collected with the `log` tool, and default, error and fault messages are written to disk up to a storage limit.

## 2. Why it’s busy

logd’s work is proportional to how much the rest of the Mac logs. It shows up in Activity Monitor when:

- A process is stuck logging the same error many times a second, often after an update or with a misbehaving app or driver.
- Debug or info logging has been turned on to persist, for example by a configuration profile, a developer tool, or someone running `log config`.
- A lot happens at once, such as startup, waking from sleep or a macOS update.
- You’re streaming logs live in Console or with `log stream`, which gives logd messages to deliver as they happen.

On the Mac this page was written on, `log stats` showed WindowServer, runningboardd and airportd writing the most bytes over the past month. Which processes top the list differs from Mac to Mac.

## 3. What to do about it

First, see how big the store is, how far back it goes, and who writes the most. This needs no password and takes a minute on a busy Mac:

```
log stats --overview
```

The top of the output gives the store’s size and its start and end dates; the processes and senders tables rank who’s logging. On disk, with an administrator account:

```
sudo du -sh /private/var/db/diagnostics /private/var/db/uuidtext
```

1. **Deal with the noisy process.** If one app or daemon dominates, update it, change its settings, or remove it. Logging less is the only lasting fix.
2. **Check the logging settings.** `sudo log config --status` shows the system-wide mode. If debug persistence has been switched on and you didn’t mean it, `sudo log config --reset` puts the defaults back.
3. **Restart** if logd’s CPU stays high with nothing obvious logging; a stuck process is often the cause.

You can delete the store with `sudo log erase --all`, which the manual page says removes the main datastore, in-flight data, time-to-live data and fault and error content. It’s rarely worth it: macOS already caps the store, and you lose the history you’d need to diagnose a problem.

## 4. Should you quit or disable it?

No. Force-quitting logd only makes launchd start it again at once. There’s no supported way to switch the unified log off: logd is part of the sealed system volume, and turning off System Integrity Protection to tamper with it would make the Mac less secure and harder to troubleshoot.

Don’t delete files inside `/private/var/db/diagnostics` or `/private/var/db/uuidtext` by hand either. If you must clear it, `log erase` is the supported tool.

If logs are what you want to save space on, the text logs and old crash reports in your own Library are the part you control.

## Questions

### Where are Mac system logs stored?

The unified log is in `/private/var/db/diagnostics`, with supporting data in `/private/var/db/uuidtext`. Older-style text logs are in `/private/var/log`, and app logs in `~/Library/Logs`.

### Can I delete the unified log to free space?

You can, with `sudo log erase --all`, but macOS already purges old messages when the store passes its size limit, so it rarely gains much for long.

### How do I see which process is filling the logs?

Run `log stats --overview`. Its processes table ranks them by events and bytes.

### Is logd related to syslogd?

Both run on current macOS. logd handles the unified log; `syslogd` is the older Apple System Log server, still used by software that logs the old way.

## How SiftMac handles it

SiftMac never touches the unified log in `/private/var/db/diagnostics`, which macOS caps by itself. Its Old logs category goes through your own `~/Library/Logs` instead, picking files older than a week.

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

## Sources

- [logd(8) manual page](https://keith.github.io/xcode-man-pages/logd.8.html)
- [log(1) manual page](https://keith.github.io/xcode-man-pages/log.1.html)
- [Apple Developer: Generating log messages from your code (storage limits)](https://developer.apple.com/documentation/os/generating-log-messages-from-your-code)
- [Apple Developer: Logging](https://developer.apple.com/documentation/os/logging)

## Related

- [Can I delete all the log files on my Mac?](https://siftmac.com/safe-to-delete/library-logs)
- [Is it safe to delete crash reports in DiagnosticReports?](https://siftmac.com/safe-to-delete/diagnostic-reports)
- [How to clear System Data on a Mac, safely](https://siftmac.com/guides/system-data-on-mac)
- [Why is kernel_task using so much CPU on my Mac?](https://siftmac.com/process/kernel-task)

Canonical: https://siftmac.com/process/logd
