Learn
AwakeTab docs
How AwakeTab keeps a screen awake, where a web page stops, and what each browser supports.
Start here
What AwakeTab does, where a browser stops, and the questions people ask most.
- How AwakeTab worksAwakeTab asks your browser for a screen wake lock and shows what the browser answered: seven states, one pill, and a timer that follows the lock.Read the guide
- Honest limitsA wake lock holds the display while its tab is visible. It cannot beat a closed lid, change your Teams status or stop system sleep. Here is each limit.Read the guide
- FAQStraight answers about AwakeTab: hidden tabs, closed lids, Teams status, iPhone Auto-Lock, faces, sounds, notes, battery, price and your data.Read the guide
Reference
Which browsers hold the screen, and the API underneath.
- Browser support matrixScreen Wake Lock support: Chrome and Edge 84, Firefox 126, Safari 16.4 and more, checked against docs and engine source. Device results are pending.Read the guide
- Screen Wake Lock APIHow navigator.wakeLock.request('screen') works, why it throws NotAllowedError, how to re-acquire after visibilitychange, and support as of September 2026.Read the guide
Behaviour
What a battery saver or a chat app does to a screen kept awake.
- Do battery savers block a wake lock? Mostly, noNo browser engine refuses a wake lock for battery saver; Firefox stops at 5 % battery. iPhone Low Power Mode does cap Auto-Lock at 30 seconds.Read the guide
- Teams status and wake locksNo. Teams shows Away after about 5 minutes without keyboard or mouse input, and Slack after 10, even with the screen on. Here is what sets your status.Read the guide
Trust
Support claims come from browser documentation and automated tests. Real-device results appear in the matrix once recorded.
How support is checkedSupport claims come from browser documentation and automated tests. Real-device results appear in the matrix once recorded.