OFF
- Remaining
- —
- Held
- 00:00:00
- Coverage
- 0%
Hold for
This browser
Chromium desktop and Android expose Screen Wake Lock. Other browsers: trust the detection on this page, not a version table.
- navigator.wakeLock checking
- navigator.getBattery checking
Keep the screen on in this tab — prevent the screen from sleeping with a screen wake lock. No sleep online; coverage shown when the tab is backgrounded.
Nothing is uploaded. The wake lock is requested in this tab and released when you stop or leave.
OFF
Hold for
Chromium desktop and Android expose Screen Wake Lock. Other browsers: trust the detection on this page, not a version table.
Keep the screen on in this tab without installing anything. This page calls navigator.wakeLock.request("screen") — the Screen Wake Lock API — so the display stays awake while you read, present, or watch a recipe. It is a no sleep online switch: one click, a countdown if you want one, and a release when you are done.
The browser always drops a screen wake lock when you leave the tab. Coming back, this page reacquires it automatically (unless the timer has already finished) and shows coverage: the share of the time you asked for that was actually held. That is the honest number — prevent the screen from sleeping only works while this tab is visible.
A screen wake lock stops the screen turning off. It does not keep the CPU awake, and it cannot override a system lock screen, battery saver, or a policy that forces sleep. If the OS wants the laptop to sleep, it still will.
Pick 10 minutes, 30 minutes, an hour, two hours, or hold until you press stop. The countdown is wall-clock from the moment you start — switching away does not pause it. When Battery API is present, charge level and charging state sit next to the lock so you can see the cost of keeping the panel lit.
Detection runs after the page mounts. Chromium desktop and Android expose Screen Wake Lock; treat the detection line on this page as the source of truth, not a version table. About and FAQ render in every browser, including ones that cannot take the lock.
No. The browser releases the screen wake lock as soon as this tab is hidden. When you come back, this page reacquires it (if you still want it and the timer has not finished) and coverage drops to match the time it was actually held.
No. It only asks the browser to keep the *screen* awake. CPU sleep, the OS lock screen, and battery-saver policies are outside what a page can do.
Coverage is held time divided by the time you asked for. If you asked for 30 minutes and spent 10 of them in another tab, coverage is about 67%. When you stop, the ratio freezes at whatever it had reached — a finished session neither keeps decaying nor jumps up to a flattering number.
Chromium desktop and Android Chrome expose navigator.wakeLock. Other browsers should trust the detection line on this page. Firefox and Safari visitors still get the about text and FAQ — the page does not disappear.
No. The lock, the timer, and the battery reading (when the Battery API exists) all stay in this tab. There is no account and nothing is uploaded.
Dead pixels, backlight bleed, banding, gamma, ghosting, refresh rate.
Buttons, double-click chatter, scroll notches, polling rate.