Your Mac fails to sleep primarily because background processes, peripheral interference, or system settings prevent the operating system from entering low-power states. To resolve this, you must identify active preventers using terminal commands, disconnect external devices, and verify energy saver configurations in System Settings.
Identify Active Preventers
The most reliable way to determine why your Mac is refusing to sleep is to query the power management daemon directly. macOS provides a command-line tool calledpmset that lists all current reasons preventing sleep. Open the Terminal application, which you can find in Applications > Utilities, and enter the following command:
pmset -g assertionsTime Machine, network utilities, or media servers such as QuickTime Player. If you see a specific application name here, that app is likely keeping your Mac awake. You can quit that application to see if the issue resolves immediately.
If the output shows no active assertions but the Mac still won't sleep, the problem may lie with hardware peripherals or deeper system configurations rather than software requests.
Check External Peripherals
External devices often send signals that keep the computer active. This is particularly common with Ethernet adapters, USB hubs, and older Thunderbolt displays. When a device is connected, it may request power or maintain a network connection that prevents idle sleep. Start by disconnecting all non-essential peripherals. Remove USB drives, external hard drives, docking stations, and dongles. If your Mac sleeps normally after unplugging everything, reconnect them one by one to identify the offending device. Once identified, check the manufacturer’s website for firmware updates or drivers compatible with your version of macOS. Additionally, ensure that your router and modem are not causing network activity to trigger wake events. Some routers broadcast packets that can be interpreted as user activity. If possible, test sleeping with Wi-Fi turned off temporarily to rule out network-related interference. For users experiencing persistent issues with specific hardware, reviewing how to manage system-level configurations might help isolate the root cause, similar to troubleshooting other macOS stability issues found in our guide on Mouse/Trackpad Click Registers Release Instead of Press on macOS Sonoma 14.5.Verify Energy Saver Settings
macOS includes built-in features designed to manage power consumption, but these settings can sometimes conflict with modern usage patterns. Navigate to System Settings (or System Preferences on older versions) and select Battery or Energy Saver. Ensure that Automatic graphics switching is enabled if your Mac has dual GPUs. This allows the system to switch to the more power-efficient integrated graphics when high performance is not required, facilitating sleep. Also, check the setting for Put hard disks to sleep when possible. While this usually affects storage rather than system sleep state, disabling it can sometimes reduce latency in waking up, though it rarely prevents sleep entirely. On laptops, verify that Wake for network access is disabled if you do not need to use features like AirDrop or remote login while the machine is asleep. Enabling this feature keeps the Wi-Fi adapter active even when the screen is off, which can drain battery and prevent deep sleep states.Reset NVRAM and SMC
If software checks and peripheral disconnections fail to resolve the issue, resetting the Non-Volatile Random-Access Memory (NVRAM) and the System Management Controller (SMC) can clear corrupted power management data. These components store information about display resolution, startup disk selection, and power behavior. For Intel-based Macs, shut down the computer completely. Turn it on and immediately press and hold Option + Command + P + R for about 20 seconds. Release the keys and allow the Mac to restart. This process resets various hardware settings to their defaults. For Apple Silicon Macs (M1, M2, M3), the procedure is simpler. Simply shut down the Mac, wait ten seconds, and then turn it back on. The power management controller resets automatically during the boot sequence on these newer chips. After performing these resets, observe whether your Mac enters sleep mode correctly.Review Scheduled Tasks and Login Items
Scheduled tasks run by the operating system or third-party apps can interrupt sleep cycles. Check System Settings > General > Login Items to see which applications launch at startup. Disable any unnecessary items that might initiate background processes immediately upon boot, potentially triggering wake events later. Furthermore, some maintenance scripts run periodically viacron or launchd. While less common on modern macOS, certain developer tools or database services might have cron jobs set to run every hour. If you suspect a scheduled task, you can inspect the /var/log/system.log file for entries related to sleep/wake transitions around the time the failure occurs.
For advanced users who have modified firewall rules, ensuring those rules do not block essential power management daemons is crucial. Incorrectly configured security policies can sometimes interfere with system communications, much like the issues discussed in Can't Delete Firewall Rules on macOS 15 (Sequoia) - Tech Support. Always verify that your security software allows system-level power events to pass through without restriction.
Frequently Asked Questions
How do I stop my Mac from waking up due to network activity?
You can disable this feature by going to System Settings > Battery > Options and turning off Wake for network access. This prevents the Mac from responding to network requests like AirDrop or remote login while it is in sleep mode. Disabling this ensures the Wi-Fi radio powers down completely during idle periods.Why does my Mac wake up randomly at night?
Random wakes are often caused by scheduled backups, software updates, or peripheral activity. Checkpmset -g to see if any timers are set for automatic wake-ups. Additionally, ensure no external devices are sending signal pulses that trick the Mac into thinking user input occurred.