A slow wake has a particular frustration: you open the lid, nothing happens, the screen stays dark. When things finally appear, apps are briefly unresponsive. Most of the time it is a software state problem. Once you understand the three main causes, fixing it is straightforward.
What "wake from sleep" actually involves
When your Mac enters sleep, it does not simply pause. A sequence of things happens that determines how fast it can come back.
RAM contents are preserved. The most important thing sleep needs to do is keep everything you had open ready to resume. In normal sleep (sometimes called "safe sleep light" or just "sleep"), the Mac keeps the contents of RAM powered at very low voltage. Your open apps, browser tabs, and documents stay in memory. On wake, macOS restores the CPU and GPU state and hands control back to those processes. When this works cleanly, wake is nearly instant.
The display handshake happens. Waking the display is not as simple as turning a light back on. macOS has to re-establish a connection with every connected screen. For the built-in display on a MacBook, this is fast. For an external monitor connected via HDMI or DisplayPort, the Mac and the monitor have to negotiate resolution, colour profile, refresh rate, and HDR capabilities before anything appears. That negotiation can take several seconds on its own.
Peripherals are re-enumerated. Every USB and Bluetooth device connected to your Mac receives a reset signal on wake. The Mac asks each device to identify itself and report what it can do. Keyboards, mice, and audio interfaces all go through this process. Most modern devices do it in under a second. Some older or poorly-designed devices take much longer, and if a device stalls, it can hold up the rest of the wake sequence.
These three phases can overlap, but they all have to complete before the system is fully usable. If any one of them is slow, the whole wake is slow.
Memory pressure at sleep time
Of the three causes, memory pressure is the most common and the least visible.
When you have many apps open and RAM is nearly full, macOS starts moving the contents of inactive apps to a swap file on your SSD. This is called paging. The swap file is on disk, which is slower than RAM even on a fast NVMe drive. When you look at the Memory Pressure graph in Activity Monitor and it is yellow or red, your Mac is actively paging. For a full explanation of what that graph means, see what memory pressure means on Mac.
The connection to sleep is direct. If your Mac went to sleep while already under memory pressure, some of what it needs to restore is on disk rather than in RAM. On wake, before your apps are responsive, macOS has to read that data back. The more that was paged out, the longer the wake takes. This is why a Mac with 8 GB of RAM running ten apps wakes noticeably slower than a Mac with 16 GB running the same ten apps: the 8 GB machine has been paging; the 16 GB machine probably has not.
There is also a deeper sleep state to consider. When plugged in for a long time, macOS may switch to hibernation mode: writing the entire contents of RAM to disk and cutting RAM power entirely. Waking from hibernation is much slower because the full RAM image has to be read back. Apple's energy and sleep documentation explains the different modes.
For most people, the practical fix is the same: reduce memory pressure before you put the Mac to sleep. Quitting apps you are not using is the fastest way to do that. Not closing their windows: actually quitting them so the memory is freed.
External display drama
If your Mac is connected to an external monitor via HDMI, the wake delay is often caused by the display handshake, not memory.
HDMI in particular has a negotiation protocol called EDID (Extended Display Identification Data) that the monitor uses to tell the Mac what it supports. On every wake, the Mac re-reads this data and re-establishes the video signal. Most monitors complete this in one to two seconds, but older or cheap monitors can take five to ten seconds. During that time, your Mac screen is black even though the system has already woken up internally.
DisplayLink adapters (the kind that let you connect multiple monitors via USB-C or Thunderbolt docks) are especially prone to this. DisplayLink runs a driver that has to reinitialise on every wake, and the driver sometimes takes longer to come back than the system itself. If you use a DisplayLink dock, check whether there is a firmware or driver update available.
USB-C hubs that carry video output over DisplayPort Alternate Mode are generally faster than DisplayLink, but they still go through a negotiation. If your hub has multiple video outputs, each one adds to the total time.
A quick test: disconnect your external display, sleep the Mac, and wake it. If wake is suddenly fast, the display or adapter is the bottleneck. Try a different HDMI cable first, then check whether your hub or adapter has a firmware update.
Peripheral enumeration
USB hubs, audio interfaces, and Bluetooth devices are all re-enumerated on wake. For most devices this is invisible: it happens in under a second and you never notice. But some devices are slow, and a slow device can block the wake sequence.
USB hubs with many devices are the most common culprit. Every device on the hub gets a reset signal on wake. If you have a hub with a hard drive, an audio interface, a card reader, and a webcam, all four of those go through enumeration in sequence. A powered hub handles this more reliably than an unpowered one, because powered hubs can supply stable current to all devices simultaneously rather than waiting for each to negotiate power.
Audio interfaces often have complex firmware that takes several seconds to initialise. If your Mac wakes slowly only when a specific audio interface is connected, the interface is likely the cause. Some audio interface manufacturers have released firmware updates specifically to fix slow wake behaviour; check their support pages.
Bluetooth devices reconnect on wake too. If your keyboard takes five seconds to pair after sleep, that registers as a five-second wake delay even if the Mac itself woke instantly.
To isolate a peripheral, disconnect everything except what you need to see the screen, then reconnect devices one at a time until the delay returns. The last device added is the one to investigate, similar to how you would narrow down a spinning beach ball to a single slow resource.
Practical fixes: three things to test this week
1. Check memory pressure before you close the lid. Open Activity Monitor (Command-Space, type "Activity Monitor", press Return) and click the Memory tab. Look at the Memory Pressure graph at the bottom. If it is yellow or red when you are about to sleep your Mac, quit some apps first. Browsers with many tabs are the most common cause of high memory pressure. Quitting apps rather than just closing windows is the key distinction: the memory is not freed until the app quits. If memory pressure is consistently high even with apps closed, see what memory pressure means on Mac for next steps.
2. Test wake speed without your external display. Unplug or disconnect your monitor, sleep your Mac, and time the wake. If it is significantly faster, the display path is your issue. Try replacing the cable, especially if it is HDMI. If you use a dock or hub, check the manufacturer's site for a firmware update. Some docks have had wake-delay fixes shipped via firmware in the past year.
3. Isolate your USB devices. If your Mac is connected to a hub with multiple devices, try unplugging the hub entirely before sleeping. If wake is faster, work through the hub's devices one by one to find the slow one. Powered hubs handle enumeration more reliably than unpowered ones: if your hub is unpowered and has more than three or four devices, a powered replacement is worth considering.
One more check: make sure macOS is up to date. Apple ships sleep and wake fixes in point releases. If wake times have been getting progressively worse rather than appearing suddenly, that is worth taking to Apple support. The same diagnostic instinct that applies to Mac freezes applies here: rule out software causes first.