Keep Screen On is a browser tool that asks your browser to keep your display awake while a single tab stays visible. It works by requesting the standardized Screen Wake Lock API — the same capability described in the W3C Screen Wake Lock specification — instead of relying on hidden videos, looping audio, fake timers, or fake brightness panels. When you select Keep screen on, the page calls navigator.wakeLock.request('screen') and then shows you whether the browser accepted the request, denied it, or later released it. The request applies only to the tab you have open. Your device's actual power settings, brightness level, and operating-system sleep behavior are not modified in any way. Nothing is uploaded, no account is required, and no background service runs after you close the page. The tool deliberately avoids media-playback workarounds because those techniques do not honestly guarantee that the display stays awake and can create side effects like audible loops, hidden battery drain, or accessibility problems for screen-reader users. Instead, you see a clear active message when the lock is held, and an equally clear message when the browser has refused or released it.
Why your screen keeps timing out in the first place
Phones, tablets, and laptops all ship with an auto-lock or sleep timer that turns the display off after a short idle window. The default is usually 30 seconds to a few minutes, depending on the device, and the timer is there for three real reasons: it saves battery, it prevents burn-in on OLED panels, and it protects unattended screens from showing private information to anyone nearby. Every operating system — iOS, iPadOS, Android, Windows, macOS, ChromeOS, and Linux — exposes this behavior through a settings panel, and most of them let you extend the timer or set it to "Never" on mains-powered devices.
The catch is that "Never" affects the whole device. The moment you set it, every screen, every app, and every idle minute stops timing out, which is great for one task and wasteful for the rest of the day. It also does not exist on every device. Many phones, work laptops, and managed tablets hide the "Never" option behind parental controls, mobile device management policies, or power-saving rules, so changing the setting is not always possible. A browser wake lock solves the narrower problem: keep one specific tab visible for the duration of one specific task without changing a global setting at all.
When keeping the screen on actually helps
A wake lock is the right tool when ordinary inactivity would be inconvenient but the rest of your day should behave normally. The product description calls out the common cases: reading a recipe while cooking, following written instructions, presenting information during a meeting, watching a visible countdown or stopwatch, and keeping a QR code, ticket, or boarding pass on display. Each of those shares the same shape — you are looking at the screen for a known window of time and any interruption forces you to touch the device again.
Other good fits include screen sharing during a quick demo, following a step-by-step repair or knitting pattern, displaying a price tag or menu at a small stall, leaving a focus timer visible across the room, and waiting on a slow file transfer whose progress bar you want to glance at. The tool is a poor fit for "I want my phone to stay awake all day no matter what" — that is a device-level power setting, and the contract is explicit that the request only holds while this tab remains visible.
| Scenario | Wake lock is helpful? | What to combine it with |
|---|---|---|
| Cooking from a recipe on a tablet | Yes — short, visible, hands-free task | A visible countdown for each cooking step |
| Following a multi-step repair guide | Yes — long task, frequent glances | Keep the guide tab in front and switch back as needed |
| Presenting a static dashboard to a room | Yes — no tab switching allowed | Plug the laptop into power before starting |
| Displaying a QR code for scanning | Yes — viewer must stay focused on screen | Confirm the active status before relying on it |
| General phone use all day | No — this is a device setting | Change Auto-Lock in your phone's display settings |
| Background music while you work elsewhere | No — tab will be hidden, lock will release | Use a real audio player or smart speaker |
How to keep your screen on with Keep Screen On
- Open the Keep Screen On page in the tab that you want to remain visible. Do not open it in a background tab — the wake lock can only be held by a document the browser considers visible.
- Select Keep screen on. The page then calls navigator.wakeLock.request('screen') and the button text changes to Turn off. Read the status line underneath the button and confirm it says the screen wake lock is active before you start relying on it.
- Keep the tab in front while you work. Do not minimize the browser, lock the device, switch to another tab, or open a new window in front of it. If any of those happen, the browser may release the lock and the status will change immediately.
- When you are finished, select Turn off. The page releases the wake lock and your device's normal display timeout resumes on its own — there is nothing to undo in your system settings.
What the on-screen status actually means
The button is simple on purpose. There is one control, and the status line beneath it tells you what the browser is actually doing. There are four states you will see, and each one is honest about what it can and cannot promise.
| Status shown | What it means | What you should do |
|---|---|---|
| Screen wake lock is active | The browser accepted the request and is currently holding the lock for this visible tab | Proceed with your task and check back if you switch tabs |
| Screen wake lock was released | The browser or operating system dropped the lock after it was active — common when the tab becomes hidden or battery saver kicks in | Return the tab to the front; the tool can request a new lock |
| Screen wake lock was denied | The browser refused the request — unsupported browser, private mode, installed web app, or restrictive device policy | Try a different browser or relax the policy; your settings were not changed |
| Screen Wake Lock API not supported | This browser does not implement navigator.wakeLock at all | Update the browser or use a current version of Safari, Chrome, Edge, or Firefox |
The visibility rule and why it matters
The Screen Wake Lock specification only allows a screen-type wake lock while the document is visible. Visibility, in browser terms, is stricter than "open in a tab somewhere." The document becomes hidden when you switch to another tab, open a new window that covers it, minimize or quit the browser, lock the device, or move to a different desktop or virtual desktop. As soon as any of those happen, the browser is allowed to release the lock without asking. The status line will change from active to released, so a stale green indicator never lies to you about the current state.
If you come back to the tab and still want the screen to stay on, the page will request a fresh lock the moment the document becomes visible again, provided you have not selected Turn off in the meantime. The contract is explicit on this point: the tool does not repeatedly request a lock in the background, does not attempt to bypass browser permissions, and does not try to evade battery protections or parental controls. It asks once, listens for the sentinel, and reports honestly when that sentinel goes away.
Limits that can still override a wake lock
A wake lock is a polite request, not a guarantee. The browser, the operating system, the battery, and any installed management profile can still take the display back whenever they decide the user or the device needs it. Common release triggers include low battery, an active low-power or power-saving mode, the user locking the device manually, switching focus to another app, an enterprise or parental-control policy, and a system event such as an incoming call or a forced restart. None of these change your settings — they simply end the lock the page is holding.
WebKit's release notes for Safari 16.4 confirm that the Screen Wake Lock API became available on iOS and iPadOS in that version, which is why older iPhones and iPads will show the "not supported" message even with a current browser. Browser support in general is good in current versions of Safari, Chrome, Edge, and Firefox, but actual availability can still vary by browser version, private-browsing mode, installed web-app mode, device policy, and power state, so the only reliable check is the status line on the page itself. Per the W3C Screen Wake Lock specification, the request is supposed to be visible to the user, and the tool leans on that requirement by surfacing every state change.
Tips for keeping the screen on reliably during long tasks
A few habits make the request noticeably more dependable over a long session. First, plug the device into power before you start if the task is longer than an hour — the lock can be released when the battery drops, and a charging device is much less likely to be interrupted that way. Second, disable low-power or battery-saver mode for the duration of the task; most of them will release wake locks by design. Third, switch off auto-orientation lock prompts and notification banners that might steal focus, because a focus change is treated as a visibility change. Fourth, use a single browser window in fullscreen so there is no risk of accidentally clicking past the tab.
If you need a timed block, pair the lock with a visible countdown so the device cannot trick you into thinking the lock is still active. A simple Online Countdown Timer running alongside the lock is a strong sanity check — if the timer keeps counting, the screen is awake. If the screen looks frozen, the lock has been released and you can switch back to the page to request it again. For structured focus work, run a Pomodoro cycle in another visible tab so you always have a clock in front of you and a clear cue to press Turn off when you are done.