What is notifyd, and why is it using CPU on my Mac?
Last reviewed: 19 November 2026. Path, account, launchd job and man page checked on macOS 26.3.1.
notifyd is the server behind notify(3), a lightweight system that lets programs post named signals, such as a network change, and lets other programs react to them. It is normally idle, and CPU use means many notifications are being posted or many processes are registered for them. You can watch notifications with notifyutil to see which ones are busy.
notifyd at a glance
| notifyd | |
|---|---|
| Made by | Apple (part of macOS) |
| Type | System daemon |
| Location | /usr/sbin/notifyd |
| Runs as | root |
| Started by | launchd job com.apple.notifyd |
| Can you quit it? | Not usefully. launchd starts it at boot and restarts it if it exits. |
What is notifyd?
The notifyd(8) man page says it is the server for the notification system described in notify(3), and that launchd starts it automatically during system startup. A program posts a notification by name, such as com.apple.system.config.network_change, and every program registered for that name is told. Some notifications also carry a small state value.
notify is used throughout macOS, including by launchd itself: many launchd jobs are started when a named notification is posted. It is separate from distributed notifications (distnoted) and from the banners in Notification Center.
Is notifyd safe?
Yes. notifyd is part of macOS at /usr/sbin/notifyd, runs as root and is started by launchd at boot.
Why does notifyd use so much CPU and memory?
- A burst of system changes. Network changes, waking from sleep, locking or unlocking the screen and power events all post notifications that many services listen for.
- A process posting in a loop. A program that posts the same notification many times a second makes notifyd deliver each one to every registered process.
- Many registrations. Every process that registers for notifications adds entries that notifyd keeps track of, so its memory grows with the number of running processes.
How much CPU is normal for notifyd?
Typical: near 0% CPU, with short bursts around wake, network changes and login.
Steady CPU use of several percent or more while the Mac is idle means something is posting notifications continuously.
How do you see which notifications keep notifyd busy?
- Watch a suspect notification. In Terminal,
notifyutil -v -w com.apple.system.config.network_changeregisters for that name and prints a time stamp each time it is posted, until you press Control-C. Lines arriving many times a second confirm a flood. notifyutil watches named keys only, so try the names of events you suspect, such as network changes. - Look for a busy partner process. In Activity Monitor, sort by CPU. A process that is busy at the same time as notifyd is usually the one posting or reacting to the notifications.
- Quit recently installed tools. Quit or remove recently installed utilities and background helpers one at a time, starting with ones that watch the network or system state, and check notifyd after each.
- Restart the Mac. A restart clears all registrations. If notifyd is busy again soon after, the source starts at boot or login.
When should you worry about notifyd?
Worry if notifyd holds high CPU for a long time while nothing is changing on the Mac; that is not its normal behavior and points to a program posting in a loop.
A notifyd outside /usr/sbin would not be Apple's.
How do you check notifyd in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type notifyd 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 notifyd process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'notifyd' | grep -v grep
How can Thrum help with notifyd?
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 notifyd 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 notifyd
What is the difference between notifyd and distnoted?
notifyd carries very small named signals, sometimes with a number attached. distnoted carries distributed notifications, which can include more information. Both are internal and separate from on-screen notifications.
Does notifyd show the notification banners I see?
No. Banners and alerts are handled by usernoted and NotificationCenter.
Sources
- notifyd(8) man page: run man notifyd in Terminal
- notify(3) man page: run man 3 notify in Terminal
- notifyutil(1) man page: run man notifyutil in Terminal