Fix Edge Sleeping Tabs Wake Up Despite an Exclusion List

Quick fix: Edge’s sleeping tabs exclusion list applies to direct URL matches, but a tab can wake when a script runs (e.g., a service worker, a video buffering, a websocket reconnect). Add the domain in edge://settings/system → Never put these sites to sleep using [*.]example.com syntax, and disable the site’s service worker via Site Permissions.

You added a few work-critical sites to Edge’s sleeping tabs exclusion. Memory usage was supposed to stay low because non-excluded tabs sleep. But periodically the system slows down and Task Manager shows multiple Edge processes spiking CPU — including tabs that should be sleeping. Sleeping tabs were waking up to do background work despite the exclusion. The exclusion list works for the sleep timer; it doesn’t prevent wake by script execution.

What makes a sleeping tab wake

A tab Edge has put to sleep stays asleep until: (a) you click it, (b) the original page’s service worker schedules a background fetch, (c) a websocket reconnects, (d) a video preload triggers, or (e) memory pressure forces Edge to keep something running. The exclusion list affects only the sleep timer — tabs on the list don’t auto-sleep, but tabs NOT on the list can wake themselves up via the above paths even after going to sleep.

The fix is to limit what scripts the woken tab can run, not to fight Edge’s wake decisions. Service workers and aggressive video preloading are the main culprits.

Method 1: Disable service workers for chronic offenders

1. Identify which tab is waking. Open Edge Task Manager (Shift+Esc inside Edge), sort by CPU. The wake offender is at the top.
2. Note the URL.
3. Open edge://settings/content/all.
4. Search for the domain (e.g., example.com).
5. Click the site’s entry to expand it.
6. Find Service Workers and toggle off, or click the trash icon next to it to remove the registered worker.
7. Reload the page. The service worker no longer wakes the tab.

For sites that depend on service workers (PWAs, offline-capable apps), disabling them breaks functionality. Use this only on sites where you don’t need the offline behavior.

Method 2: Use the “Never put these sites to sleep” list correctly

Edge has two related but different lists. Confirm you’re using the right one.

1. Open edge://settings/system.
2. Find Save resources with sleeping tabs.
3. Make sure Sleeping tabs is on but the inactivity timer is set appropriately (default 2 hours; set to 1 hour or less if you want more aggressive sleeping).
4. Under Never put these sites to sleep, add the sites you want to keep awake. Use the format [*.]example.com to match all subdomains, or just example.com for the apex domain.
5. Note: this list is for sites that should NEVER sleep. Sites NOT on this list will sleep. If you’ve added the site here and the tab still wakes, the wake is from a script (Method 1), not from the sleep timer.

Reading the list’s purpose carefully is important — many users assume it’s a “keep these awake forever” list when it’s actually “don’t auto-sleep these.”

Method 3: Disable background media autoplay and preloading

Video and audio sites often wake to buffer the next segment. Disable autoplay and preload to limit this.

1. Open edge://settings/content/mediaAutoplay.
2. Set the default to Limit (Edge’s most restrictive level).
3. For chronic media offenders, add them under Block.
4. For HTML5 video preloading, disable it per site via Site Permissions → the site → Auto-download = Block.
5. Reload affected tabs.

Limit autoplay also reduces unwanted audio when accidentally clicking sleeping news/video tabs — useful even outside the sleeping tabs context.

How to verify the fix worked

• Open Edge Task Manager (Shift+Esc inside Edge). Sleeping tabs show 0% CPU and reduced memory (typically < 10 MB).
• Wait an hour and check again. CPU stays at 0%.
• Total Edge memory in Windows Task Manager stays stable rather than growing through the day.
• Service workers for the offending site no longer appear in edge://serviceworker-internals.

If none of these work

If specific tabs keep waking despite all three methods, the tab might be running an HTML5 audio element that prevents sleep entirely. Mute the tab (right-click the tab title → Mute tab) — muted tabs can sleep again. For chronic problems with many tabs, consider an extension like Tab Suspender (open source) that has more granular control than Edge’s built-in sleep system. For Edge Beta/Canary channels where sleeping tabs is unstable, switch to stable Edge for the affected workflow.

Bottom line: Sleeping tabs and the exclusion list are separate mechanisms. Adding to the exclusion list prevents sleep but doesn’t prevent wakes from scripts. Service workers, autoplay video, and websockets are the wake culprits — address those at the per-site level for full control.