What is usernoted, and why is it using CPU on my Mac?
Last reviewed: 19 November 2026. Path, account, launchd job, man page and Notifications settings labels checked on macOS 26.3.1.
usernoted is the macOS daemon that provides notification services: it receives notifications from apps and websites, applies your notification settings, and hands them to Notification Center to show. It uses CPU when many notifications arrive and should be near idle otherwise. Turning off notifications from apps that send a lot is the most effective fix.
usernoted at a glance
| usernoted | |
|---|---|
| Made by | Apple (part of macOS, notifications) |
| Type | Launch agent |
| Location | /usr/sbin/usernoted |
| Runs as | your user |
| Started by | launchd job com.apple.usernoted |
| Can you quit it? | Not usefully. Its launchd job keeps it alive and starts it again. |
What is usernoted?
The man page describes usernoted as the Notification Center daemon that provides notification services on the system. Apps post notifications through Apple's User Notifications framework, either generated locally or pushed from a server; usernoted is where they arrive. It checks each one against the app's settings (whether notifications are allowed, the alert style, sounds, badges and previews) and passes it on to the NotificationCenter process, which draws the banner.
launchd starts it at login for your user through the com.apple.usernoted job and keeps it alive.
Is usernoted safe?
Yes. usernoted is part of macOS, signed by Apple, and stored in /usr/sbin on the read-only system volume. It runs as your user.
Why does usernoted use so much CPU and memory?
- Apps that send many notifications. Chat, mail, monitoring and build tools can post notifications in quick succession, and each one is processed and stored.
- Notifications from iPhone. With iPhone notifications shown on the Mac, notifications from the phone arrive in Notification Center as well.
- A large backlog. Notifications you never clear are kept, so a long history of delivered notifications grows what it has to manage.
- Badges and sounds. Apps that update their badge count often keep usernoted passing those updates on.
How much CPU is normal for usernoted?
Near 0% CPU between notifications. Short bursts when notifications arrive are typical.
Memory use is typically in the tens of megabytes and grows with a long backlog of notifications.
How do you stop usernoted from using so much CPU?
- Find the noisy app. Open Notification Center by clicking the date and time in the menu bar and see which app has the most notifications stacked.
- Turn off or limit that app's notifications. Open System Settings > Notifications, select the app, and turn off Allow notifications, or turn off Play sound for notification and Badge application icon.
- Clear the backlog. In Notification Center, use Clear All on stacks you no longer need.
- Turn off notifications from iPhone. If you do not need them on the Mac, turn off Allow notifications from iPhone in System Settings > Notifications.
When should you worry about usernoted?
Look closer if usernoted stays above about 10% CPU with no notifications arriving. One app posting notifications in a loop is the usual cause; turning off that app's notifications should stop it.
It should run only from /usr/sbin/usernoted as your user.
How do you check usernoted in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), and type usernoted 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 usernoted process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'usernoted' | grep -v grep
How can Thrum help with usernoted?
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 usernoted 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. Click usernoted in the list for its PID, threads and memory, and Quit or Force Quit it after a confirmation.
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 usernoted
What is the difference between usernoted and NotificationCenter?
usernoted receives and manages notifications; NotificationCenter draws the banners, alerts and the panel.
Can I disable usernoted?
No. launchd keeps it running because apps rely on it to deliver notifications. Turn off notifications per app instead.
Sources
- usernoted(8) man page: run man usernoted in Terminal
- Apple Developer: User Notifications
- Apple Support: Use Notification Center on Mac