MacBook DarkWake vs. FullWake: What the Power States Mean

A MacBook can record a wake-related event even when you did not open the lid or see the display turn on. Two terms that appear in macOS power logs are DarkWake and FullWake. They describe different power capabilities during a wake period; they are not simple labels for “bad wake” and “normal wake,” and neither term alone names the process responsible.

What DarkWake means

DarkWake is a limited wake state used for some background system activity. Depending on hardware and macOS, the system may bring up selected capabilities while keeping the display and ordinary user session inactive. The machine can later return to sleep or transition into a fuller wake. The details are platform-dependent; do not expect every Mac to support identical wake types or expose identical log wording.

Apple’s public IOKit definitions distinguish system capabilities such as CPU, graphics, and audio. Apple’s open-source PowerManagement headers also define internal state flags for sleep, DarkWake variants, and FullWake. That source is useful evidence that power management distinguishes these states, but internal implementation names are not a user contract and can change between releases. Apple’s PowerManagement source is not a promise that a particular Mac will use each state.

What FullWake means

FullWake generally means that the system has restored capabilities associated with a normal, user-visible wake, such as graphics and interaction. The display can remain dark in some circumstances, so even “full” in a log should be read in context. Check the surrounding lines, event time, wake reason, and whether the display actually illuminated. A single state word cannot describe the whole user experience.

The difference matters when diagnosing battery drain. One short background wake may be expected. Repeated or long periods of activity can contribute more energy use, but a log label alone does not quantify the battery impact. Compare battery percentage over a measured interval under similar conditions, and note whether the Mac was on battery or power adapter.

Do not infer a specific cause from the state name

Wake reasons may mention network access, maintenance, scheduled events, peripherals, or hardware signals. They are clues, not definitive attribution. For example, DarkWake does not prove that a third-party app or a “lid angle sleep” script woke the Mac. macOS and firmware coordinate power transitions, and one event can involve several components. Likewise, a process shown near a wake does not automatically prove it initiated that wake.

Apple documents PreventSystemSleep as an assertion that can let the system remain in DarkWake rather than sleep. It also says assertions are requests that the OS honors only as circumstances allow; low power or thermal emergencies can still lead to sleep. This does not mean every DarkWake was caused by that assertion. Apple’s API reference states the assertion’s behavior and limitation.

A practical way to inspect a wake

Capture a short interval around the event rather than searching logs without a time range:

pmset -g log | tail -200
log show --last 1h --style compact --predicate 'process == "powerd"'

The pmset history often presents sleep and wake transitions in a compact form. Unified logging can provide additional messages, subject to macOS privacy, retention, and log availability. A powerd predicate narrows the search; it may miss related events logged by another subsystem. See how to read sleep and wake logs for a repeatable workflow and privacy-conscious sharing tips.

Record the clock time, whether the screen lit, whether the lid was open, power source, attached devices, and recent schedule or network changes. Compare more than one event. If a pattern appears only with a specific dock, USB device, or network setting, disconnect one variable at a time for a short, controlled test. Avoid changing several pmset values at once because that makes the result difficult to interpret.

Common questions

Does DarkWake mean the Mac is fully awake?

No. It refers to a limited capability state in Apple’s power-management terminology. Exact behavior varies by platform and macOS version.

Does a DarkWake mean an app ran while the Mac was asleep?

Not necessarily. The state name does not identify an app, and app behavior during background wake is constrained. Use event logs and reproduce the issue before drawing a conclusion.

Can I disable every DarkWake?

There is no safe universal switch for all background wakes. System settings such as network wake or Power Nap availability vary by Mac and macOS. Disable only a setting that is actually present and relevant, then observe the result.

If the display turns on unexpectedly, see MacBook sleep vs. display off. For suspected battery loss while the lid is closed, use the closed-lid battery drain guide and consult the compatibility guide and FAQ. A diagnostic utility can organize evidence, but it cannot certify a hardware repair or override Apple’s power-management decisions.