How to Read MacBook Sleep and Wake Logs
Use pmset and macOS unified logs to build a time-bounded timeline, interpret common fields, and avoid overclaiming what a power event proves.
A practical guide to pmset -g log and log show, with time windows, wake reasons, privacy, and limits of attribution.
When a MacBook appears to wake unexpectedly, write down the local time and time zone, whether the display actually turned on, whether the lid was open, whether the Mac was on battery, and what accessories were attached. Also note recent changes: a macOS update, new dock, backup schedule, network setting, or an app that requests background work. A useful review starts with one reproducible event. Searching without a time range can surface unrelated maintenance messages and make ordinary system activity look alarming.
Capture power history
Open Terminal and run pmset -g log | tail -250. The pmset manual describes the command as a way to read and manage power-management settings and logs; output details can vary across macOS releases. Scan the excerpt around the timestamp for a sleep transition, wake transition, reason field, and later return to sleep. Save the unedited excerpt locally before trying configuration changes. The command reports what the system recorded; it does not automatically identify a responsible user-level app. pmset(1)
Query unified logging
Use the macOS log show command to add context, for example log show --last 1h --style compact --predicate 'process == "powerd"'. Adjust the interval to cover the event, using local log show --help for supported date syntax. A powerd filter is a starting point, not a complete trace: kernel or driver messages may use other process names. Some values are redacted, and older records may no longer be retained. Avoid collecting a whole diagnostic archive when a short time window answers the question.
Correlate, then test one variable
Build a timeline from last known sleep to the next visible wake. A reason that mentions network, maintenance, USB, Bluetooth, a timer, or SMC is a clue about the system’s report, not necessarily the original source. A process active after wake may simply be responding. DarkWake denotes a limited power capability state; it does not prove a script ran or that a particular app initiated the event. Apple’s open-source PowerManagement source shows internal state distinctions, but internal code is not a promise that all Macs expose identical events. PowerManagement source
If a dock seems relevant, disconnect only the dock, repeat the same sleep interval, and compare. Keep power source, lid position, network, and workload stable. Then reconnect and repeat if useful. Changing several things at once weakens the evidence. pmset -g assertions is a snapshot of active requests now; it cannot reconstruct every request that existed overnight. Capture it while a suspected task is running and compare before and after the task.
Protect personal information
Logs can expose account names, device names, network addresses, file paths, and usage patterns. Review every excerpt before sharing it. Remove identifiers and include only lines around the event, along with Mac model, macOS version, and relevant conditions. Do not post passwords, full home-directory paths, or a full diagnostic archive to a public forum.
FAQ
Does pmset -g log list every wake? It lists available power-management history, but not every related subsystem message or complete cause chain.
Does DarkWake prove an app was running? No. It cannot establish that a third-party app or lid-angle utility caused the wake. Read DarkWake vs. FullWake.
Why are older entries missing? Unified log retention is finite and varies. Capture evidence soon after reproducing the event.
Make the result reproducible
Keep a small note with the event date, Mac model, macOS version, battery or adapter state, attached devices, and the exact action that preceded the wake. A second occurrence under similar conditions is stronger evidence than a single line. If you are comparing before and after a setting change, use the same observation window and avoid running a different workload. System power behavior changes with OS updates and model capabilities, so include the version instead of assuming another person’s log will look identical. This short record helps Apple Support or a technician ask focused follow-up questions without needing an unfiltered diagnostic archive.
For the paired battery measurement, read closed-lid battery drain.
Check your Mac before choosing a fix
mac lid close assists sleep and wake using available signals. It does not repair damaged hardware or rewrite Apple part authentication.