What is logd_helper on my Mac?
Last reviewed: 19 November 2026. Path, account, launchd job and man page checked on macOS 26.3.1.
logd_helper is a helper daemon that performs services for logd, the macOS unified logging daemon, and is intended only for logd's use. It is started on demand and is often not running at all. It is part of macOS and needs no action.
logd_helper at a glance
| logd_helper | |
|---|---|
| Made by | Apple (part of macOS, unified logging) |
| Type | System daemon (helper) |
| Location | /usr/libexec/logd_helper |
| Runs as | root |
| Started by | launchd job com.apple.logd_helper |
| Can you quit it? | Not usefully. launchd starts it when logd needs it. |
What is logd_helper?
The man page says logd_helper "is a helper daemon that performs various services for logd(8). logd_helper should not be invoked directly. It is intended only for use by logd(8)." Apple does not list those services, so this page does not guess at them.
It runs as root from the com.apple.logd_helper launchd job. On this Mac it was not running when checked, which is normal for an on-demand helper.
Is logd_helper safe?
Yes. It lives in /usr/libexec on the read-only system volume next to logd and is signed by Apple.
Why does logd_helper use so much CPU and memory?
- Work for logd. It runs when logd hands it a task. Its activity follows logd's: heavy logging on the Mac makes both busier.
- Started on demand. launchd starts it when needed, so it can appear for a moment and then go away again.
- Small footprint. As a narrow helper it uses little memory while running.
How much CPU is normal for logd_helper?
Usually not running or idle. Short appearances are normal.
How do you stop logd_helper from using so much CPU?
- Check logd. If logd_helper keeps appearing, check logd's CPU at the same time; the steps there find the process that is logging too much.
- Confirm it is Apple's. Run
ps -axo user,pid,comm | grep logd_helper. The path should be/usr/libexec/logd_helperand the user root. - Restart if it stays busy. Continuous activity is not expected for this helper. A restart starts the logging system fresh.
When should you worry about logd_helper?
Sustained CPU from logd_helper is unusual; note the time and check what logd and other processes were doing.
A copy outside /usr/libexec would not be Apple's.
How do you check logd_helper in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type logd_helper in the search field. The CPU tab shows its % CPU. The Memory tab shows its Memory. Double-click the row for its parent process, memory details and open files.
In Terminal, the first command lists every logd_helper process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'logd_helper' | grep -v grep
How can Thrum help with logd_helper?
Thrum keeps a live CPU graph in the menu bar. One click shows the eight processes using the most CPU, so you can see when logd_helper is among them and how much it takes. An optional alert tells you when a process stays above a CPU level you choose (50 to 200% of one core) for 1 to 10 minutes. macOS does not let apps quit processes owned by root or other users, so Thrum shows them for information and leaves stopping them to the steps above.
Thrum is $4.99 once with a 14-day free trial and no account. It requires macOS 26 Tahoe on Apple silicon or Intel.
Questions about logd_helper
Why is logd_helper not running on my Mac?
It is started only when logd needs it. Most of the time there is nothing for it to do.
Can I run logd_helper myself?
No. Its man page says it should not be invoked directly and is intended only for use by logd.
Sources
- logd_helper(8) man page: run man logd_helper in Terminal