A Caffeine-style "keep screen on" tool uses your browser's Screen Wake Lock API to ask the operating system to stop dimming and locking the display while a specific tab stays visible. Open the Keep Screen On page, select the button, confirm that the status changes to active, and your display will stay awake as long as you leave that tab in front of you. When you are done, click Turn off and the normal display timeout takes over again. The whole process runs locally in your browser, never uploads anything, and never changes your device's actual brightness or power settings. Because the request is tied to a visible document, switching tabs, locking the screen, or closing the window lets the browser release the lock on its own. This makes the browser method a safer, more reversible alternative to installing desktop utilities that override power settings at the system level.
Anyone who has ever watched a recipe scroll off the screen, lost a QR code at the wrong moment, or had a presentation black out in the middle of a sentence knows why a tool like this exists. The problem is not new, and neither is the name. What has changed is where the request lives. A browser tab can do the same job today using a documented web standard, without leaving the page, the account, or the device behind.
What the Original Caffeine Utility Did and What the Browser Method Does
The original Caffeine utility is a lightweight program for macOS and Windows that issues a command to the operating system so the display and the system itself do not sleep. It is useful when you are reading a long article, following a recipe, presenting information, or watching a timer tick down. The downside is that it has to be installed, it runs in the background, and it overrides a power setting that your operating system normally controls. Once Caffeine is on, it keeps the system awake until you remember to turn it off again, and it has no awareness of which window is actually visible to you.
The browser version of this idea works the same way for any tab that needs to stay visible. Instead of asking the operating system directly, Keep Screen On asks the browser to hold a screen wake lock on your behalf. The browser then negotiates with the operating system for you. This keeps the request scoped to one tab, leaves your system settings alone, and lets you turn it off with a single click the moment you are finished. The wake lock follows the tab: when the page is hidden, the lock is released, and when the page is visible again, a new lock can be requested.
That last point is what makes the browser method different from a system-wide utility. A Caffeine-style desktop program treats the whole machine as awake. A browser wake lock treats only the visible document as awake. The same machine can host a sleeping browser window, an active timer tab, and a music app in the background without any of them fighting for control over the display.
Three Steps to Use a Caffeine-Style Browser Wake Lock
The setup is intentionally short so it works in the middle of any task you want to keep visible.
- Open the Keep Screen On page in the same tab you want to keep visible during your task.
- Select the Keep screen on button and confirm that the status text on the page says the screen wake lock is active in the current browser.
- Leave the tab in the foreground while you read, cook, present, or follow instructions. Select Turn off when you are finished so your normal display timeout can resume.
There is no account, no download, and no background service. The request is initiated only after you press the button, and it is released when you press Turn off or when the browser releases it on its own. If you close the tab or navigate away, the lock drops automatically. The status indicator on the page reflects the actual state of the request: it shows active when the browser has accepted the lock, denied when the browser has refused it, and released when the lock has been dropped, so the displayed message is always a truthful one of what the browser is doing right now.
Where the Browser Method Works and Where It Doesn't
Most modern browsers expose the screen wake lock capability, but real-world support depends on the browser version, the browsing mode, and device-level policies. The table below describes the conditions that determine whether the request is accepted, denied, or released, and it reflects what the W3C specification and current browser documentation actually say.
| Condition | Effect on the Screen Wake Lock |
|---|---|
| A modern browser version on a recent operating system | The browser can accept the request and the status reads active while the tab stays visible. Safari added support in version 16.4 and other engines continue to evolve support over time. |
| Private browsing mode in some browsers | The API may be restricted, so the request can be denied with a clear message instead of going through. |
| Installed web-app mode with reduced permissions | Screen wake lock availability can be limited by the runtime policy of the installed wrapper. |
| Low battery, battery saver, or a power-saving mode is on | The operating system can refuse or release the lock even when the browser has accepted it. |
| Tab is hidden, minimized, or the device is locked | Browser standards allow wake locks only for visible documents, so the lock is released. |
| Enterprise or parental controls on the device | Device policy can take priority and the request can be denied at the system level. |
Per the WebKit release notes, Safari added screen wake lock support in version 16.4, and the broader availability across browsers continues to evolve, so always check the on-page status before trusting the lock for a critical task. If the browser does not support the API at all, the tool surfaces that as an explicit state rather than silently failing or falling back to a workaround.
Limits That Can Override a Screen Wake Lock
A screen wake lock is a polite request, not a permanent override. Your browser, battery state, and operating system remain in charge of the display, and they can decide to refuse the request or release an active lock at any moment. Common triggers include switching to another tab, locking the device, running the browser in the background, the battery dropping below a threshold, or a system power-saving profile turning itself on. Each of these is a layer the wake lock does not control, and each one can win the argument about whether the display stays lit.
The Keep Screen On page is designed to make those moments visible instead of pretending everything is fine. If the request is denied, the status text changes to explain that the browser did not allow it, and your settings are left untouched. If the browser or device releases an active lock, the status changes immediately so you are never looking at an inaccurate "active" indicator while your screen is actually dimming. When you return to the visible tab, the tool can request a new lock, but only after the page becomes visible again. It does not retry silently in the background and does not attempt to bypass the layers above it.
For tasks that demand higher certainty, plug the device into power when practical and verify the active status on the page before relying on it. A wake lock cannot overcome a battery that is about to die or a system policy that says the screen must sleep. Treat the active message as confirmation that the request has been accepted for the current moment, not as a permanent guarantee.
What the Wake Lock Does Not Do
The list of things a wake lock deliberately does not touch is just as important as what it does. It does not change the brightness of your screen, install any software, or modify any system preference. It does not extend the life of a dying battery, override a parental control, or push past an enterprise power policy. It is a single-purpose request scoped to one visible tab, and the browser will refuse to honor it when the document is no longer the foreground page.
This narrowness is intentional. Earlier attempts to keep a display awake inside a browser used hidden video elements, looping audio tracks, full-screen color panels, or other tricks to trick the device into staying awake. Those techniques do not honestly guarantee that the display will remain awake and can create an inaccessible side effect. The Screen Wake Lock API was designed so a page can make the request directly, and Keep Screen On uses that documented path rather than any of the older workarounds.
Pairing the Screen Lock With Focus and Timing Tools
Keep Screen On is intentionally narrow. It asks the browser for the documented wake lock capability and tells you when it succeeds, is denied, or is released. For longer sessions you will usually want a real timer or task tracker running in the same visible tab.
For a timed focus block, you can combine the wake lock with a Pomodoro Timer running in the same tab so your display does not dim between work intervals, or use an Online Countdown Timer when you need a single countdown that you can glance at while cooking, presenting, or supervising a process. Each of these tools runs locally and does not interfere with the wake lock the browser is holding for the Keep Screen On tab.
If you need a gentle visual panel next to a camera during a video call, use the Screen Light tool separately, because changing the page panel does not change your device's actual brightness or sleep behavior. Keep Screen On is the tool for the wake lock itself, and the other browser tools cover the timing and presentation needs around it.
Troubleshooting When the Status Says "Denied" or "Released"
A denied status means the browser or operating system refused the request, so the page leaves your display settings exactly as they were. A released status means the lock was active and then dropped. The fastest checks are also the most common causes.
- Confirm the tab is the active, visible window and is not being covered by another app.
- Disable battery saver or low-power mode if your device is currently using one.
- Try a normal, non-private browsing window, since private mode can restrict the wake lock API.
- Update the browser to the latest stable build, because very old versions do not support the API.
- Check for device policy or parental controls that may block power-related browser features.
If the status switches from active to released after you have been working for a while, the browser is reporting that something on the system side dropped the lock. Switch back to the visible tab to let the tool request a new lock, and confirm that the active message returns before continuing to rely on it. Keep Screen On never tries to bypass browser permissions, battery protections, parental controls, or operating-system sleep rules, so any of those layers can be the reason a request is denied. When in doubt, treat the active status as a snapshot of the current request, not a permanent contract.
Related reading: Online Alarm Clock: Three Inputs, One Browser Tab.