powerd on Mac: the power manager, why it is using CPU, and what is really keeping your Mac awake

What powerd does

Eclectic Light's long explainer on power management describes the Power Manager's role as managing the transition between different power states: awake, display sleep, system sleep, and the lighter states in between. powerd is that manager. It reads the battery, watches the lid and the charger, applies the settings from the Battery or Energy pane, and enforces thermal and low power mode limits with help from kernel_task.

Its most important job is less obvious: it keeps the list of power assertions. An assertion is a request from an app to keep the Mac or the display awake. Video players, Zoom, a download in progress, Time Machine, a Keynote presentation, and plenty of background services all make them. powerd collects these, and as long as one is active the Mac does not sleep, even though, as Eclectic Light notes, the Energy Saver pane may allow it. That is why a Mac that refuses to sleep is nearly always a question for powerd's list, not for the settings.

It also runs the schedule. If you have ever set the Mac to wake or sleep at a certain time, powerd is what carries it out. It runs as root, starts at boot, and macOS relaunches it instantly if it stops.

What normal looks like

powerd is one of the quietest processes on a healthy Mac, which makes any sustained load easy to spot:

The first thing to understand is that powerd at 100 percent is a symptom. Some process is asking it to do something thousands of times a second, usually creating and releasing power assertions, and powerd is dutifully processing each request. The CPU is charged to powerd. The fault is elsewhere.

Why powerd is using CPU right now

1. An app is creating and dropping assertions in a loop. A browser tab with a broken video player, a media app that keeps starting and stopping, a conferencing app after a call ended badly. This is the common case. Quitting the app ends it instantly.
2. A sleep or wake schedule is stuck. Several reports, including one with powerd at around 100 percent, were fixed by setting a sleep schedule in System Settings and then cancelling it, which rewrites the schedule powerd holds.
3. A charger or display is flapping. A loose cable, a faulty hub or a display that keeps reconnecting generates endless connect and disconnect events. Each one is a power state change.
4. Battery reporting is confused. After a battery service or on an aging battery, powerd can be stuck re-reading a value. Shutting down fully for a minute and restarting resets it.
5. Right after a macOS update. Power settings are migrated and the first wake or two is busier. This clears within an hour.
6. A background helper that cannot sleep. Some third-party menu bar tools poll the battery or thermal state many times a second. Turning them off in Login Items shows whether one is responsible.

How to see what is keeping your Mac awake

Open Activity Monitor and click the Energy tab. Look at the column called Preventing Sleep. Every app with Yes in that column holds an assertion right now. That list is powerd's list, shown to you. If a video player, a browser, or a conferencing app is there with nothing actually playing, that is your culprit. Quit it.

If nothing obvious is listed, sort by Energy Impact. The app at the top is doing the most work and is the next suspect. Browser tabs count as part of the browser; the which tab is using memory guide shows how to find the specific tab.

For the overnight version of this problem, where the Mac wakes repeatedly while the lid is closed, the battery draining fast guide reads the wake reasons from the log. sharingd and other network listeners are usually behind those.

Is it safe to quit powerd?

No, and it does not help. powerd runs as root, Activity Monitor asks for your password, and launchd restarts it within a second. During that second the Mac has no power manager: the battery percentage may vanish from the menu bar, sleep requests are ignored, and any app that was looping on assertions carries straight on with the new powerd. You would end up exactly where you started.

The safe actions are all one level up. Quit the app that is preventing sleep. Change a setting in the Battery pane. Restart. Those address the thing that is making powerd busy.

The checker above says the same for every root daemon on this site: leave it, fix the sender.

What to do, in order

1. Check Preventing Sleep in the Energy tab

   Activity Monitor, Energy tab, look for Yes in the Preventing Sleep column. Quit each app listed that is not actually doing something. Check powerd again after thirty seconds.

2. Quit the browser, then reopen it

   A single tab with a stuck video or audio element is the most common source. Quitting the whole browser clears it. If powerd drops, reopen the browser and watch which tab brings it back.

3. Reseat cables and hubs

   Unplug the charger, any hub, and external displays. Wait ten seconds. If powerd settles, plug them back one at a time to find the one that was flapping.

4. Reset the sleep schedule from settings

   Open System Settings, Battery (or Energy on a desktop), click Schedule, add a wake time, save, then open it again and remove it. This rewrites the schedule powerd keeps and has cleared the 100 percent case in several reports.

5. Turn off suspect login items

   System Settings, General, Login Items & Extensions. Turn off battery monitors, fan controllers and similar helpers one at a time. See Mac background items for a walkthrough.

6. Shut down fully, wait a minute, start up

   A full shutdown rather than a restart lets the power system reset its battery and charger state. On Apple silicon this is also what replaces the old SMC reset.

7. Run battery diagnostics if it persists

   If powerd is still high after all of this with no third-party software running, the battery or charging hardware may be reporting badly. Run Apple Diagnostics by holding the power button at startup on Apple silicon, and contact Apple if it reports a battery issue.

When to worry

powerd itself is not a security or data concern. The worry is what high powerd implies: the Mac is not sleeping properly, which means heat, battery wear and a laptop that is warm in a bag. Act when:

• The Mac will not sleep with the lid closed or wakes every few minutes overnight.
• powerd stays high across a full shutdown with nothing third-party running, which points at hardware.
• The battery percentage jumps around or the Mac shuts off above zero percent, which is a battery health problem, not a software one.

Everything short of that is a stuck app or a stuck schedule and clears with the steps above.

The hard part is catching which app started the storm, since by the time you look, powerd is the only name that stands out. Safe to Quit keeps a timeline of every process and every sleep-blocking assertion, so you can scroll back to the minute powerd jumped and see what else did.