A browser does not promise to redraw a countdown every second while its tab is hidden. It can reduce background work to save power. That explains why a display may appear to jump when you return, even when the timer uses the correct finish time.
Display updates are not elapsed time
Imagine a ten-minute countdown started at 2:00. Its target is 2:10. If the browser does not update the page between 2:03 and 2:05, a timer that subtracts one second per callback could fall behind. A target-time countdown instead compares the current time to 2:10 when it gets another chance to run.
AlarmClock.live’s countdowns use that target-time approach. It helps the visible number recover after delayed updates. It does not make the browser execute code at a moment when the operating system has suspended it.
What you can and cannot expect
Switching tabs may delay visual updates. A discarded tab or sleeping device may stop execution more completely. Closing a page removes its active timer code. The directory timer saves its session locally when storage is available so that it can show the remaining time after a reload. A restored session asks you to enable sound again.
If the deadline passed while the page was closed, reopening shows that the session finished. It cannot retroactively deliver a sound at the original deadline. A browser timer also depends on the device clock; large manual clock changes can affect a wall-clock deadline.
Use a visible workspace for an important session
- Start the timer with an intentional click or tap.
- Press Test sound and confirm the output device.
- Leave Keep screen awake enabled if your browser supports it.
- Keep the page visible when possible, especially on mobile devices.
- Use a native backup when missing the alert would cause a problem.
Fullscreen helps visibility but is not a power-management guarantee. A wake-lock request may also be refused or released, so read the status message rather than assuming a checked option proves it is active.
A useful way to compare setups
Run a short trial with the timer visible, then another while you use a different tab. Note whether the sound arrives, whether the screen stays on, and what the display shows on return. Compare the result on the actual device you use for work, not only on a different computer. If a timer is unreliable in the background, keep it visible or change tools.
For specific silent-alert steps, use the sound checklist. For closed lids, read the laptop sleep explanation.
Sources and further reading
These sources explain the underlying browser or data behavior. The setup examples above describe AlarmClock.live.
Continue exploring
Browse all guides · Choose a countdown · Browser reliability
Found a step that no longer matches your browser? Send us a correction.