You can keep your screen on when not in use by opening a page that asks the browser for a screen wake lock in the visible tab you need, then leaving that tab in front of you until the task is finished. The wake lock is a documented browser capability, not a hidden video trick: the page asks the system to prevent the display from dimming or locking while the document is visible, and the page itself tells you when the request is active, denied, or released. Your operating system, browser, and battery settings still have the final say — they can refuse the request, drop it when the tab is hidden, or hand control back when power-saving mode kicks in — so the active status on the page is a confirmation of what the browser agreed to do, not a guarantee that the device will stay on forever. For reading a recipe, following written instructions, watching a timer, presenting on a stand, or leaving a QR code visible for someone else to scan, this is the narrowest honest answer to how to keep screen on when not in use, because it stays inside the browser's standard capability rather than fighting your device's power controls.
Why Your Display Sleeps When You Are Reading, Cooking, or Presenting
Every phone, tablet, and laptop ships with an inactivity timer. The operating system assumes that a display sitting on the same image for a minute or two is being ignored, so it dims, then locks, then sleeps — partly to save battery, partly to reduce screen wear, partly so a forgotten device does not stay unlocked. That assumption is exactly wrong when you are looking at the screen the whole time but not touching it: your hands are covered in dough, your eyes are on the camera during a presentation, you are leaning over a tablet to read a recipe at the stove, the laptop lid is propped on a stand and the keyboard is folded away.
The fix most guides reach for first is to dig into system settings and bump the inactivity timer to five minutes, ten minutes, or "never". That works, but it is a global change — every other app on the device now keeps the screen awake too, including the one that forgot to log out last night. It also does not survive a reboot, a corporate policy reset, or a kid who borrowed the phone. A browser-based wake lock does the opposite: it targets only the tab that needs to stay visible, and it stops the moment you turn it off or hide the tab.
What a Browser Screen Wake Lock Actually Does
The Screen Wake Lock API is a small, documented browser capability that lets a web page ask the browser, "please keep this screen awake while my document is visible." The browser is allowed to say no. If it says yes, it returns a sentinel object the page holds on to; the moment the page releases the sentinel, the browser resumes normal sleep behavior. The browser compatibility data for Navigator.wakeLock is published in the MDN browser-compat-data Navigator node, which is how the supported-browser list is normally assembled, and Safari added the API in version 16.4.
This is narrower than "make the screen bright" and narrower than "stop the device sleeping forever." Three things the request does not do:
- It does not change your hardware brightness, your auto-lock timer, your battery saver mode, or any other device preference.
- It does not keep the screen on when the tab is hidden, minimized, or covered by another window.
- It does not promise the wake lock will survive until you turn it off — the browser can release it on its own if system policy, battery level, or power state changes.
The honest tool design reflects those limits. A page that asks for the wake lock, shows whether the request is currently active, and turns the indicator off the moment the browser releases it gives you the truth. A page that runs a hidden video, loops an audio file, paints a fullscreen color, or claims to "force" the display awake is doing something else entirely and is usually lying about whether your device will actually stay on.
How to Keep Screen On When Not in Use
Use the Keep Screen On request when you want a single browser tab to remain visible for a recipe, a presentation, a long-form read, a cooking timer, or any task where your eyes are on the screen but your hands are not.
- Open the page in the exact tab you want to remain visible. If the task involves a different page (a recipe site, a slide deck, a video player), keep the wake-lock page open in this same visible tab — opening the wake-lock page in its own tab and switching away to a task tab would hide it, and a screen wake lock can be held only by a visible document.
- Select Keep screen on. The status line should change to confirm that the browser accepted the request. If the status instead says the request was denied, your browser did not allow the wake lock for this document and your device settings are unchanged.
- Leave the tab visible while you work. Keep your eyes on the screen and your hands free — that is the point of the request.
- Select Turn off on the page when you are finished, or simply hide, close, or switch away from the tab. The normal display timeout resumes immediately.
For a focused work session, pair this request with a timer in a separate tab — the wake lock on the page you are actually reading keeps your eyes on the content while the timer tab keeps counting.
When the Browser Will or Will Not Honor the Request
The Screen Wake Lock API is supported in most modern browsers, including Safari 16.4 and later, but real-world availability still depends on browser version, private-browsing mode, installed web-app mode, device policy, and current power state. An unsupported browser receives an explicit message on the page; nothing is requested and nothing changes on your device.
Even when the request is accepted, four conditions commonly release the wake lock without you doing anything:
- The tab is hidden, the browser is minimized, or another window covers it.
- The device locks, sleeps, or enters a power-saving mode.
- Battery level drops below the threshold your browser or operating system uses.
- A parental control, enterprise policy, or other system policy takes priority.
The honest page reflects each of these as a state change. If you select Keep screen on and then return to the tab after hiding it, the page requests a fresh lock — it does not retry silently in the background, it does not attempt to bypass permissions, and it does not extend the lock past what the browser is willing to give. If a lock was active and is now released, the status flips immediately rather than leaving an inaccurate "on" indicator.
Common Scenarios Where a Wake Lock Helps Most
A wake lock is the right tool when ordinary inactivity would be inconvenient but not dangerous. The table below compares the most common tasks for which readers ask how to keep screen on when not in use, the rough duration of each, and the practical reason a targeted wake lock beats a system-wide change.
| Scenario | Typical duration | Why a targeted wake lock helps |
|---|---|---|
| Reading a recipe while cooking | 15 to 45 minutes | Hands are wet or holding utensils; a global inactivity bump affects every other app |
| Following written instructions (assembly, repair, knitting, crochet) | 30 minutes to 2 hours | The screen is being watched, not touched, for the whole task |
| Presenting a browser tab on a stand or second screen | 5 to 60 minutes | Auto-lock resets the presentation every time the timer fires |
| Watching a long countdown or stopwatch | Several minutes to a few hours | The display is the information source, not a control surface |
| Leaving a QR code visible for someone else to scan | 1 to 5 minutes | A second person needs to read the code at human pace |
| Reading a long article or PDF without scrolling | 10 to 30 minutes | Touch input is rare on long-form reading, so inactivity fires early |
For each row, the page you need to stay awake is the visible tab. If the task is itself a timer, pair the wake lock with the Online Stopwatch in a second tab.
How This Differs from Older Keep-Awake Workarounds
Three older workarounds still appear in search results, and it helps to know why an honest wake lock is the better answer to how to keep screen on when not in use.
- Hidden video or audio loop. A page can play a silent video in the background to "trick" some devices into thinking content is active. This works inconsistently, can fail silently when the browser throttles background tabs, drains more battery than a wake lock, and produces no useful status — you cannot tell whether the trick is currently keeping the screen on.
- Fullscreen color panel. Some sites paint the page a single bright color and fullscreen it. This does not request a wake lock at all; it only maximizes brightness on that page. The device will still sleep on schedule.
- Permanent system auto-lock change. Raising the inactivity timer or disabling auto-lock in settings changes the behavior of every app on the device, including ones that should sleep, and does not reset cleanly across reboots, profiles, or mobile-device-management policies.
A wake lock is narrower, more honest, and easier to reverse. The page that requests it shows whether the request is active, whether the browser denied it, and whether the browser later released it. Nothing is uploaded, no account is required, and no background service runs.
Practical Habits That Make a Wake Lock More Reliable
A few habits make the request succeed more often and fail more gracefully when it does not.
First, connect the device to power when practical. A wake lock is more likely to be honored while a laptop is plugged in than while a phone is at four percent.
Second, confirm the on-page status before relying on it. The page should report an active state; if it reports denied, your device settings are unchanged and you can try a different browser or close private-browsing mode.
Third, return to the tab if you switched away. The browser is required to release the lock when the document is hidden. Coming back prompts a fresh request; the page does not retry on a hidden schedule.
Fourth, do not try to combine this with fullscreen tricks or a separate auto-lock tweak in the same session. Either the wake lock is enough on its own, or the device policy you are up against will not respect a wake lock at all.