What is powerd, and why is it using CPU on my Mac?
Last reviewed: 19 November 2026. Path, bundle, account, launchd job and man page checked on macOS 26.3.1.
powerd is the macOS power management daemon: it applies your Energy and Battery settings, decides when the Mac and display sleep, and keeps track of power assertions that apps create to keep the Mac awake. It is busy around sleep and wake, power source changes, and when apps create and release many assertions. It is part of macOS and cannot be turned off.
powerd at a glance
| powerd | |
|---|---|
| Made by | Apple (part of macOS, power management) |
| Type | System daemon |
| Location | /System/Library/CoreServices/powerd.bundle/powerd |
| Runs as | root |
| Started by | launchd job com.apple.powerd |
| Bundle ID | com.apple.powerd |
| Can you quit it? | No. launchd keeps it running; sleep, wake and battery handling depend on it. |
What is powerd?
Its man page describes powerd simply as the "Daemon that manages Energy Preferences." It is a bundle named "PowerManagement configd plugin" in /System/Library/CoreServices, runs as root from the com.apple.powerd launchd job, and is kept alive at all times. The job registers services including com.apple.PowerManagement.control and com.apple.powerd.lowpowermode.
The settings it manages are the ones in System Settings > Battery (Energy on desktop Macs) and the ones pmset changes. The pmset man page explains that processes may override these settings with power assertions; pmset -g assertions lists them by owning process, and on this Mac powerd itself owned one, a short-lived assertion named com.apple.powermanagement.delayDisplayOff.
Is powerd safe?
Yes. powerd is part of macOS in /System/Library/CoreServices on the read-only system volume. It runs constantly and normally uses very little CPU.
Why does powerd use so much CPU and memory?
- Sleep and wake. Going to sleep, waking, closing or opening the lid and display sleep are all handled by power management, which shows as short bursts.
- Apps creating and releasing assertions. Audio playback, video calls, downloads and tools such as caffeinate create assertions that stop sleep. Apps that create and drop them many times a minute add up.
- Power source and battery changes. Plugging in, unplugging, and battery level changes update power state and can switch the energy mode.
- Always resident. As a daemon that is always running, it stays in memory. About 7 MB was observed on this Mac.
How much CPU is normal for powerd?
Near 0% CPU, with brief activity at sleep, wake and power changes.
How do you stop powerd from using so much CPU?
- See what is keeping the Mac awake. Run
pmset -g assertionsin Terminal. The list by owning process shows which apps hold assertions such as PreventUserIdleSystemSleep. - Check the Energy tab. In Activity Monitor, open the Energy tab and look at the Preventing Sleep column, which Apple says shows whether an app is preventing the Mac from going to sleep.
- Quit apps that hold assertions. Pause media, end calls and quit apps you are not using that appear in the assertions list.
- Review sleep settings. Open System Settings > Battery (Energy on desktop Macs) and look for settings such as Prevent your Mac from automatically sleeping when the display is off and Wake for network access, which change when the Mac sleeps.
- Read the sleep and wake history. Run
pmset -g log | tail -50to see recent sleep, wake and assertion events.
When should you worry about powerd?
powerd itself rarely uses much CPU. If it does for a long time, look at pmset -g assertions for an app creating assertions in a loop.
A Mac that will not sleep is almost always an assertion held by an app, not a fault in powerd.
How do you check powerd in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type powerd 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 powerd process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'powerd' | grep -v grep
How can Thrum help with powerd?
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 powerd 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 powerd
Can I quit powerd?
No. launchd keeps it running, and the Mac could not manage sleep or battery without it.
Is powerd the same as pmset?
No. pmset is the command-line tool for reading and changing power settings; powerd is the daemon that applies them.
Sources
- powerd(8) and pmset(1) man pages: run man pmset in Terminal
- Apple Support: View energy consumption in Activity Monitor on Mac
- Apple Support: About Power Modes on your Mac