Keep Screen On Android keeps your phone's display from timing out by asking the browser to hold a screen wake-lock request while a specific browser tab stays visible. Open the page in the tab you want to remain active, tap Keep screen on, and check that the on-page status reports an active wake lock. The request targets the browser, not the Android operating system, so nothing is installed, no developer option is toggled, and no Android permission is granted. Your display timeout, brightness slider, dark theme, and battery-saver rules remain under Android's control, which is why a wake-lock request can be denied by the browser or quietly released when the tab is no longer the visible page. Hidden video loops, color panels, and audio tricks are deliberately not used because they do not honestly guarantee the display will stay awake. The visible status text always reflects what the browser actually did with the request: accepted, denied, or released, instead of pretending your hardware settings have changed.
Why Android Locks the Screen and What a Browser Can Do
Android's display is designed to turn off after a period of inactivity. That timeout exists to protect the battery, dim the OLED or LCD panel, and lock the phone against accidental touches. The default sits somewhere between 30 seconds and two minutes depending on your device and Android version, and changing it usually means opening Settings, navigating to Display, and choosing a longer Screen timeout. Some Android skins, including Samsung One UI, Xiaomi MIUI, and Pixel UI, hide the setting one level deeper, restrict the available intervals, or require a PIN re-entry to extend it. For a one-off task such as following a recipe, scanning a QR ticket, presenting a slide, or monitoring a timer, fiddling with system settings feels heavier than the moment deserves.
This is the gap that a browser-based screen wake lock fills. The W3C Screen Wake Lock specification defines a JavaScript API that lets a web page ask the browser to keep the display from dimming or locking while the page is visible. Android's Chrome adopted this API and made it available without developer flags. A focused on-page request can therefore interrupt the normal inactivity timer for one task, then release the request when the user is finished. The request does not rewrite system files, does not need root, and does not push advertising or telemetry off your device. It only ever asks the browser for a documented capability and then surfaces the browser's actual response.
How to Keep Screen On Android Using a Browser Tab
In practice, using the tool on an Android phone takes three deliberate steps, plus the implicit step of leaving the tab visible while the task runs.
- Open the Keep Screen On page in the browser tab you actually want to stay active, ideally the same tab already showing the recipe, ticket, instructions, timer, or QR code. The wake lock applies to this tab only and does not blanket the whole phone.
- Tap Keep screen on and read the on-page status line. If the browser accepts the request, the page reports an active screen wake lock. If the browser refuses, the page explains the denial rather than silently pretending the display will stay awake.
- Leave the phone in that visible tab while you cook, present, follow steps, or watch a timer. Switch back to this tab if you briefly leave for another app, because browsers release wake locks when a document is no longer the visible page.
- Tap Turn off when you finish. The browser releases the wake lock, the status changes back to inactive, and Android's normal display timeout resumes from there.
The first tap turns the request on, the second turns it off; there is no auto-stop timer, no schedule, and no recurring re-arm built into the page. For a timed session, pair the request with the Pomodoro Timer, Online Countdown Timer, or Online Stopwatch in the same browser so that the wake lock keeps the screen alive while your timer counts.
Reading the Status Messages on the Page
The status line on the page is the only source of truth about whether the browser accepted the request. Because Android, the browser, and the page each can say no, the messages are split into four honest states rather than one optimistic "enabled" indicator.
| Status on the page | What it actually means on Android |
|---|---|
| Active | The browser accepted the wake-lock request and currently holds a screen wake lock. The display will not dim while this tab is visible. |
| Not active | The browser has no current wake lock. Android's normal display timeout governs the screen. |
| Denied | The browser refused to grant a wake lock. Device settings, private mode, or browser policy blocked the request; nothing has changed on the phone. |
| Released | The browser previously held a wake lock but dropped it, typically because the tab was hidden, the phone locked, battery saver kicked in, or the browser entered a low-power state. |
Choosing to leave the tab open while you work is what keeps the lock in the Active row. Closing the tab, locking the phone, or letting the screen rotate to another app pushes the status to Released, and you will see the change the next time you look at the page.
When the Wake Lock Is Denied or Released
A wake lock is a polite request, not a forceful command. The browser can refuse on first use, and it can release a lock that already started. Recognising the difference prevents you from assuming the page is broken when the phone behaves normally. On Android, the most common reasons for a denial or release include:
- Incognito or private-browsing mode, where wake-lock availability can vary by browser.
- A work profile, managed device, or parental-control policy that restricts the Screen Wake Lock API through a managed browser.
- The browser seeing the page after the device has already entered a low-battery, low-power, or extreme battery-saver mode.
- The tab no longer being the visible top tab, including a pull-down notification shade, picture-in-picture, split-screen, or a system overlay covering most of the page.
- A browser version that does not implement the Screen Wake Lock API at all, which the page reports as an unsupported state.
The right response is the same in each case: return to the visible tab, tap Keep screen on, and let the page request a fresh lock. If the status stays on Denied or Unsupported, the Android browser on that device does not support the API for this session, and the alternative is to extend Android's own Screen timeout from Settings instead. The page never silently re-arms in the background, and it never tries to bypass browser permissions, battery protections, parental controls, enterprise policies, or operating-system sleep rules.
Browser Support and Android-Specific Limits
Browser support on Android has shifted over the last few releases. Most current builds of Chrome, Edge, Samsung Internet, and Firefox handle the wake-lock request, while a small number of alternative browsers, in-app web views, and some older Samsung Internet builds do not. The exact behaviour also depends on whether you are in a standard tab, a private tab, or a managed browser.
| Browser on Android | Wake-lock supported | Notes |
|---|---|---|
| Chrome (recent builds) | Yes | Default browser on most Android phones; works in standard tabs; availability can vary by private-browsing mode. |
| Samsung Internet (recent) | Yes | Built on Chromium; behaviour mirrors Chrome on the same Android version. |
| Firefox for Android | Yes (recent builds) | Implementation can trail Chrome on new APIs, but wake-lock support is present in current releases. |
| Microsoft Edge for Android | Yes | Chromium-based; behaves the same as Chrome on the same Android version. |
| In-app browsers (web views) | Often no | Chat apps, social apps, and many reader apps skip the API even when they appear to render a full page. |
| Private or Incognito tabs | Often no | Many browsers disable the API in private mode to limit fingerprinting and background battery drain. |
If your everyday browser reports Unsupported, try a recent Chrome build from the Play Store first, then re-check whether the same lock works in a non-private tab. WebKit's notes on Safari 16.4 confirm the same Screen Wake Lock API shape across browsers, and the underlying schema is documented in the MDN browser-compat-data Navigator.wakeLock node.
Where Keep Screen On Sits Among Other Android Options
Android offers several ways to keep the display on, each with a different cost. Settings → Display → Screen timeout is the canonical system knob, but every longer timeout applies to the whole phone, drains more battery, and silently persists after the task is finished. Developer options exposes a "Stay awake while charging" toggle that only works while USB power is connected and requires the developer menu unlocked. Samsung devices add a "Keep screen on while viewing" toggle inside Advanced Features that uses the front camera to detect a face, which is unreliable in dim kitchens or when the phone is propped away from you. Third-party Caffeine-style apps install a foreground service that periodically simulates a touch, which works but requires an APK install, a persistent notification, and ongoing battery usage.
The browser tab approach is the lightest of these options. Nothing is installed, no permission is granted, no system file is touched, and reverting is a single tap on Turn off or simply closing the tab. The page that delivers this is the Keep Screen On tool, whose behaviour follows the public contract described in the W3C Screen Wake Lock API: feature-detect the API, request the screen type only from a visible document, retain and listen to the returned sentinel, release it on user stop, and re-request only after a visible-tab transition while the user still wants it on. For a task that matters, keep the phone connected to power when practical and confirm the displayed Active status before relying on it, because the browser and Android remain in charge and can still refuse or release the request at any point.
For a deeper look, see Audio Reaction Time Test on Android: A Realistic Method.
For a deeper look, see Set a Break Reminder on Laptop in a Browser Tab.