Sleeping Tabs FAQ


What is sleeping tabs?


To improve memory and CPU utilization of the browser, we've developed a feature called sleeping tabs.


Sleeping tabs in Microsoft Edge makes tabs “go to sleep” after 2 hours of inactivity to free up resources for other areas, such as active tabs, new tabs, and other applications on your device. You can adjust the time interval in Settings by going to edge://settings/system. Tabs that are asleep will fade to indicate they’ve released resources.  To resume a sleeping tab, click on it like a normal tab. The tab will un-fade and your content will be there immediately.




What about the sites I never want to sleep?


To keep you in your flow, we have built in heuristics to detect tabs doing important activity in the background and prevent these tabs from sleeping. You can also add sites you never want to sleep to a block list in Settings by going to edge://settings/system.


What activities prevent a site from going to sleep?


To help you stay on task and limit potential compatibility issues, the following activities prevent sites from going to sleep:


  • The page is currently visible (active tab)
  • The page is currently holding a Web Lock or an IndexedDB transaction
  • The page is sharing its BrowsingInstance with another page
  • The page is your company’s internal (intranet) site
  • The page is currently being inspected by DevTools
  • The page is currently playing audio
  • The page is currently capturing a window or screen
  • The page is currently capturing user media (webcam, microphone, etc)
  • The page is currently being mirrored (casting, etc)
  • The page is on the user’s block list in Settings
  • The page is currently using WebUSB

We will continue to evolve this list as we experiment.


How does the sleeping tabs technology work?


Sleeping tabs builds upon the core of Chromium’s “freezing” technology. Freezing pauses a tab’s script timers, minimizing CPU usage and frees up the operating system to reuse the memory for other open tabs, new tabs, or system applications.


What sleeping tabs group policies will enterprises get?


Currently, we have a group policy to disable the feature. We also plan to have a group policy that blocks certain sites from going to sleep.


Why do others see the feature, but I do not?


We are in the process of deploying this feature, so it may be a little while before you see it in your respective channel and build. 


Can I turn off Sleeping Tabs?


Yes, you can do this by toggling off in Settings under edge://settings/system.


Can I change the amount of time before a tab goes to sleep?


Yes, you can do this by changing the time interval in Settings under edge://settings/system.


How do I send feedback?


With this technology, it is possible that some sites may not work as expected after they go to sleep.  We are eager to get your feedback on sleeping tabs. If you experience a compat issue, please refresh the page and let us know through Microsoft Edge by pressing Shift+Alt+I on a Windows device or going to Settings and more … > Help and feedback > Send feedback.


You can also discuss your experience here on the Microsoft Edge Insider forums and Twitter, or send us your feedback through the browser!


- The Microsoft Edge Product Team

5 Replies
Awesome feature! Thanks a lot!

@Eleanor_Huynh Ooh ! Looks great ! I've been using to suspend (not freeze) through an extension, so this is great news.
Do webpages with form input get frozen as well, though ? I assume freezing won't discard these inputs, if I understood correctly, as opposed to suspending ?

These granular options right in the Edge settings is very convenient.

Hi @AmineI, thanks for reaching out! Glad you are enjoying the feature!

As you might know from your experience with it, the Great Suspender uses tab discarding which remembers some of the state on the tab, but unloads the page completely. Some state can be lost, however. With sleeping tabs, the activities of the tab are just suspended, so no state is lost and there is no reload necessary. Thus, webpages with form inputs should go to sleep as well and not lose any data.  


@HotCakeX, thanks for giving sleeping tabs a try and sharing your feedback!