How the Screen Wake Lock API Works (and What It Can't Do)

If you've ever followed a recipe on your phone while your hands were covered in flour, you know the problem. You look away for a minute, the screen dims, and then it locks. Now you're unlocking your phone with your knuckle.

Some websites quietly fix this for you. The screen just stays on while the page is open. That's the Screen Wake Lock API at work, and it's also what powers WakeMode's Keep Screen Awake tool. It's a small piece of browser technology, but it has some rules worth knowing, because they explain almost every "why did my screen turn off anyway?" moment.

What a screen wake lock actually is

A screen wake lock is a request a web page makes to the browser. In plain words, it says: "I'm showing something the person is using. Please don't let the screen dim or lock while I'm on screen."

The browser can say yes or no. If it says yes, it hands the page a kind of receipt. While the page holds that receipt, the display stays on. When the page is done, it hands the receipt back and the screen goes back to its normal timeout. Nothing is installed and no settings are changed. It's a temporary agreement between one page and your browser.

The rules browsers enforce

Browsers are careful with this, and that's a good thing. Here are the rules that matter.

The tab has to be visible. The moment you switch tabs, minimize the window, open another app or lock your phone, the browser cancels the wake lock automatically. A page in the background can't keep your screen on. When you come back, the page has to ask again. Good tools do this for you without a click, but this is the number one reason people see their screen turn off.

The page has to be secure. Wake locks only work on pages served over HTTPS. You won't notice this on any modern site, but it's why the feature can fail on old or local test pages.

The site embedding it has to allow it. If a page sits inside another site's frame, the outer site can block wake locks entirely.

The browser can say no. If your battery is low or a power saving mode is on, some browsers refuse the request or release an existing lock. It's their call, not the website's.

What a wake lock can't do

This is where a lot of online advice gets it wrong. A screen wake lock keeps your display awake while you're looking at the page. That's it.

It doesn't change your system settings. Your screen timeout stays exactly as you set it, and it applies again as soon as the page lets go.

It doesn't stop you locking your device. Press the power button or close the laptop lid and the device sleeps as usual.

It doesn't work in the background. If you want your screen on while you watch something in another app, a browser wake lock won't help.

It may not beat company policies. On some managed work computers, security rules can still lock the screen after a set time, whatever a web page asks for.

Which browsers support it

Chrome and Edge have supported screen wake locks since 2020. Safari added support in 2023, and Firefox followed in 2024. On iPhone and iPad, every browser uses Safari's engine underneath, so support depends on your iOS version rather than which browser app you use. For a long time, wake locks didn't work reliably in websites saved to the iPhone home screen. Apple fixed that in iOS 18.4. 

In practice, any reasonably up-to-date phone, tablet or computer supports it. If yours doesn't, a well-built tool should tell you plainly instead of failing silently.

Is it safe, and does it drain the battery?

It's one of the most harmless features a browser offers. Most browsers don't even show a permission prompt for it, because there's nothing to leak. The page learns nothing about you, and the lock ends when you leave.

The wake lock itself uses no meaningful power. What uses power is the screen staying on, which is the whole point. A bright screen running for two hours will use the same battery whether a wake lock kept it on or you kept tapping it. If battery matters, turn the brightness down and set a duration rather than leaving it on indefinitely.

The old tricks it replaced

Before this API existed, websites got creative. The most common trick was playing a tiny invisible video on a loop, because phones keep the screen on during video playback. It mostly worked, but it wasted battery, sometimes used data, and broke whenever browsers tightened their autoplay rules. On computers, people installed small utilities or even bought USB "mouse jigglers" that nudge the cursor to fake activity.

The wake lock API replaced all of that with one honest request the browser understands. No fake video, no fake mouse movement, and the browser stays in control.

When to use a wake lock and when to change your settings

A screen wake lock is ideal for temporary needs: following a recipe, reading a long document, giving a presentation, watching a dashboard, or keeping a timer or clock on screen. You start it when you need it, and everything goes back to normal when you close the page.

If you want your screen to stay on for longer every day, change the display timeout in your device's settings instead. That's a permanent change, and it doesn't depend on a browser tab staying visible.

For everything in between, open the Keep Screen Awake tool, pick a duration and get on with what you were doing.