Keep the Screen Awake While a Timer Runs
By Mark Fulton · 2026-09-15 · 13 min read
To keep the screen awake while a timer runs, use a timer that requests a screen wake lock and keep its tab visible, or lengthen the device's own display timeout: Auto-Lock on iPhone and iPad, Screen timeout on Android, the screen and sleep timeouts on Windows, the Lock Screen display settings on a Mac, and the Power settings on a Chromebook. But first check which problem you actually have. A screen that went dark is a display setting, and the timer behind it is usually still counting correctly. A device that locked or went to sleep is different: the browser treats the page as hidden, can pause it, and the chime may not play until you wake the screen. A dark screen is only annoying. A sleeping device is the one that can make you miss the end of the timer.
Most advice on this treats the two as one problem and hands you a single keep-awake button. That button helps with the first problem. It does very little for the second, and it can't help at all once a phone is in your pocket with the screen locked. So this post takes them one at a time, gives the actual setting on each device, and says plainly where no web page can help.
Why does the screen turn off while a timer runs?
Because nothing told the device you were still using it. Every phone, tablet and laptop runs an idle timer that has nothing to do with the countdown on your screen. It counts time since your last touch, click or keypress. When that runs out, the device dims, then turns the display off, and on phones and tablets it locks as well.
A countdown timer is the kind of page that trips this timer every time. You set it, step back, and do the thing you were timing. You are looking at the screen, but you aren't touching it, and a device can't tell looking from leaving. Apple describes the iPhone as dimming and then locking "when you look away for a while", which is a better guess than a plain countdown but still a guess.
Batteries make the defaults short. Microsoft's own guide to power settings in Windows 11 lists new defaults for modern standby PCs of three minutes to screen-off on battery and five minutes plugged in. Phones are often shorter still. And power-saving modes cut them further without telling you: Apple's Low Power Mode sets Auto-Lock to 30 seconds while it is on, which is why a phone that stayed awake all yesterday dims after half a minute today.
Does a dark screen mean the timer stopped?
Usually not, and this is the distinction that matters most.
There are three different things a device can do when you stop touching it, and they have very different effects on a timer running in a browser:
- The display dims or turns off, and nothing else happens. This is the normal behaviour of a laptop or desktop with the screen timeout set shorter than the sleep timeout. The computer is fully awake, the browser is running, the tab is still the visible tab. The countdown carries on and the chime plays on time. You just can't see it.
- The phone or tablet locks. On iPhone, iPad and Android, turning the screen off and locking happen together. The browser now counts the page as hidden, the same as a tab you switched away from, and mobile systems are quick to pause hidden pages. A well-built timer still knows the right remaining time when you come back, because it reads the clock instead of counting ticks. The sound is the part you can't rely on.
- The computer goes to sleep. Everything stops. Nothing runs, so nothing makes a sound, until something wakes the machine.
So the screen going dark on a laptop is a cosmetic problem, and on a phone it is a real one. We covered the full picture of hidden, frozen and discarded tabs in whether online timers keep running in background tabs. The short version is that the count survives almost everything and the alarm does not.
A quick way to tell which case you are in: if you come back and the timer shows the right time and its chime starts the moment the screen lights up, the page was paused, not broken. If the number is wrong, you are using a timer that counts its own ticks, and no display setting will fix that.
How do you stop the screen sleeping on each device?
Here is every device with the setting that causes the problem, the fix, and whether the timer itself was ever in danger. The menu paths match each vendor's own support documentation as of September 2026. Menu names on Android differ between brands, so the Android row uses Google's Pixel wording and a note on other phones follows the table.
| Device | What turns the screen off | The fix | Was the timer at risk? |
|---|---|---|---|
| iPhone | Auto-Lock, and Low Power Mode, which forces Auto-Lock to 30 seconds | Settings, Display & Brightness, Auto-Lock, then choose a longer time. Turn off Low Power Mode, or charge past 80 percent, which turns it off automatically | Yes. A locked iPhone hides the page, so the count stays right but the chime may wait until you wake the screen |
| iPad | Auto-Lock, plus Low Power Mode | Settings, Display & Brightness, Auto-Lock. If you can't change it, Guided Access may be on, and Guided Access disables Auto-Lock while it is active | Yes, same as iPhone |
| Android (Pixel) | Screen timeout, and Adaptive timeout, which turns the screen off early when it thinks you aren't using it | Settings, Display & touch, Screen timeout. Turn off Adaptive timeout there. On Pixel 4 and later, turn on Screen attention, which keeps the screen on while you are looking at it | Yes. When the screen times out the phone locks and the page is hidden |
| Android (any, while charging) | The normal timeout still applies on the charger | Enable Developer options (tap Build number seven times), then turn on Stay awake, which keeps the screen on while the device is plugged in | Not while plugged in with Stay awake on |
| Windows 11 | Two separate timers: screen-off and sleep | Settings, System, Power & battery, Screen, sleep & hibernate timeouts. Lengthen "Turn my screen off after" and "Make my device sleep after", on battery and plugged in separately | Screen off: no, the timer keeps running and chiming. Sleep: yes, everything stops |
| Mac | Display-off time in Lock Screen settings, and sleep | Apple menu, System Settings, Lock Screen: "Turn display off on battery when inactive" and "Turn display off on power adapter when inactive". On a laptop, Battery, Options, turn on "Prevent automatic sleeping on power adapter when the display is off". On a desktop Mac the same switch is under Energy | Display off alone: no. Sleep: yes |
| Chromebook | Idle power settings, and closing the lid | Select the time at the bottom right, Settings, System preferences, Power. Set "While inactive and plugged in" and "While inactive and on battery" to Keep display on. Turn off "Sleep when lid is closed" if you need the lid shut | Display off: usually not. Sleep or a closed lid with sleep on: yes |
For your own reference: Apple documents the iPhone path in keeping the iPhone display on longer, and notes that delaying or preventing Auto-Lock may increase power consumption. That note applies to every row in the table, which is why the plugged-in settings are the better ones to change on a laptop.
On non-Pixel Android phones the screen timeout lives under Display in Settings on most models, but the exact label varies by brand and Android version. If you can't find it, search Settings for "timeout". Developer options are a real, documented part of Android, but they are not meant for everyday use. Stay awake is harmless. Leave the other switches in that screen alone.
What is a screen wake lock and when does it work?
A screen wake lock is a request a web page can make that says: while I'm on screen, please don't dim, turn off or lock the display. It is a standard browser feature, described in MDN's Screen Wake Lock API documentation, and it's how an online timer can keep your screen on without you changing a single setting.
It is well supported now. Per MDN's compatibility data, Chrome and Edge have had it since version 84, Firefox since 126, and Safari on the Mac since 16.4. Safari on iPhone and iPad added it in 16.4 but with a gap: it didn't work in web apps saved to the Home Screen until iOS 18.4, which is when full support arrived. Samsung Internet has had it since version 14. caniuse's tracker put global browser support at about 94 percent when I checked in September 2026. Older devices with older browsers simply ignore the request.
Its limits are the important part, because they explain almost every "it didn't work" report:
- Only a visible page can hold one. Switch tabs, minimise the window or lock the phone, and the browser releases the lock automatically. It doesn't come back by itself. The page has to ask again when you return.
- The system can refuse or take it back. MDN lists power-save mode and a low battery as reasons a request can be rejected, or an existing lock released. So a phone in Low Power Mode may ignore it.
- It holds the screen, not the whole device. It stops the idle timer from switching the display off. It doesn't stop you pressing the power button, closing a laptop lid, or the system sleeping for a reason of its own.
Here is exactly what our countdown timer does with it, since that is the tool this post is about. The moment a timer starts counting, the site requests a screen wake lock. It holds the lock for as long as any timer is running, including one you started and then left the page to use another tool. If you switch away and come back, it asks for the lock again as soon as the tab is visible. When you pause the timer, or once it finishes, the lock is let go and your normal display timeout applies again. If the browser doesn't support wake locks or turns the request down, nothing breaks. The timer runs as usual and the screen follows your device settings.
The night clock works the same way, except it holds the lock for as long as the page is open, because a clock you can't see is not much of a clock. If you're setting up a spare device to show it all night, turning an old phone into a bedside clock walks through that setup.
Why does a locked phone behave differently?
Because a laptop with its display off is still a running computer, and a locked phone is a device that has decided you have left.
When a phone locks, every open page counts as hidden. The wake lock is released on the spot, since only a visible page can hold one. Then the mobile system starts managing the browser's power use, which can mean running the page's timers rarely, pausing it entirely, or unloading it to free memory. None of that is a browser bug. It is the phone doing its job of stretching the battery through a day in your pocket.
What survives is the count. A timer that stores its end time and compares it against the clock will show the right remaining time, or the right "time's up", the moment you look again. Ours also saves that end time in the browser, so even a reload picks the countdown up where it really is. What doesn't survive is the guarantee that the chime plays at the exact moment, because a paused page can't make a sound.
A phone's built-in alarm app is different in kind, not just in quality. The operating system itself wakes it up. A web page can't sign up for that, and any page that says otherwise is overselling. That is the honest boundary: keep the screen on and a browser timer is dependable, lock the phone and it is correct but no longer an alarm.
When should you rely on sound instead of sight?
More often than you'd think. The whole reason the screen keeps going dark is that you are doing something other than watching it, and a timer you have to watch isn't doing much for you.
The better design for most timing is: keep the page awake and the screen on, then stop looking at it. Let the chime do the work. A few cases where that matters:
- Cooking, workouts and focus blocks. Put the device where it can be heard, turn the volume up before you start, and treat the display as a backup. When our timer finishes, the chime repeats until you dismiss it, so stepping out of the room for a minute doesn't mean missing it.
- Presentations and talks. Keep the screen awake with a wake lock page or a longer timeout, because here you do need to glance at it. Plug the laptop in and change only the plugged-in values.
- Anything with a real consequence. Picking someone up, taking medication, catching a train. Use your phone's built-in alarm. That isn't a knock on web timers. The operating system can wake a locked phone, and a web page can't.
One habit makes the visual side easier too. While a timer runs, ours shows the time it ends underneath the countdown, and the remaining time sits in the browser tab title. If the screen dims, one tap and one glance tell you exactly when to expect the chime.
If you want the simplest version of all of this, open the countdown timer, press start, and leave the tab in view with the volume up. It requests the wake lock for you, shows you when it ends, and chimes until you stop it. It's free, there's no account and nothing to install, and no timer, clock or alarm on this site ever sits behind a paywall. Keep it in view, but trust the chime, not the screen.
Frequently asked questions
Can a website stop my screen turning off?
Yes, while the page is visible. Modern browsers let a page request a screen wake lock, which stops the display dimming, turning off or locking for as long as that tab stays on screen. Chrome, Edge, Firefox and Safari all support it in current versions. It stops the moment you switch tabs, minimise the window or lock the phone, the system can refuse it in power-saving modes, and a website can't stop you closing a lid or pressing the power button. For anything a web page can't cover, change the device's own timeout.
Does a timer keep running with the screen off?
On a laptop or desktop where only the display turned off, yes: the computer is awake, the countdown carries on and the chime plays on time. On a phone or tablet, the screen turning off also locks the device, which pauses or slows the page. A well-built timer still shows the correct remaining time when you look again, but the sound may not play until you wake the screen. If the whole computer went to sleep, nothing runs until it wakes.
How do I keep my laptop awake without changing settings permanently?
Use a page that holds a screen wake lock, such as a running timer in a visible tab. The lock only lasts while the page is on screen and ends when you close the tab, so nothing about your system changes. If you'd rather use a setting, Windows, macOS and ChromeOS all keep separate values for battery and for plugged in. Lengthen only the plugged-in values and your laptop keeps its normal battery behaviour the rest of the time.
Why does my phone dim even while charging?
Because on most phones the display timeout applies whether or not the phone is plugged in. An iPhone's Auto-Lock timer doesn't change on the charger. If Low Power Mode is on, it holds Auto-Lock at 30 seconds, and Apple turns Low Power Mode off automatically only once the battery is charged to 80 percent or higher. On Pixel phones, Adaptive timeout can switch the screen off early. Android does have a keep-on-while-charging option, called Stay awake, but it lives inside Developer options, which you enable by tapping Build number seven times.