Countdown Timer: Set It Once, Trust the Alert

Timer or stopwatch? The question decides itself

The two tools are mirror images. A stopwatch counts up and does not know where it ends; a countdown counts down from a duration you choose and knows exactly where it ends. That single difference determines everything else, including whether the tool can alert you.

The test is simple: is the duration the answer or the instruction? "How long did that call take?" is an answer, so it wants a stopwatch. "Steep this for four minutes" is an instruction, so it wants a countdown. If you catch yourself watching a stopwatch and waiting for a particular number to appear, you picked wrong — and you will miss the number, because watching is not a reliable alarm.

Being able to look away is the practical payoff. A countdown can interrupt you; a stopwatch can only be observed.

Setting a duration in one gesture

Presets cover the durations people actually use: 1, 3, 5, 10, 15 and 30 minutes, and one hour. One click sets the timer, which matters more than it sounds — typing three fields to start a five-minute break is enough friction that people simply stop bothering, and then they stop taking the break.

For anything else there are hours, minutes and seconds fields. Type the duration, and the timer arms itself as you type; there is no separate confirmation step to forget.

What happens at zero

At zero the timer alerts you twice over, on two different channels, because one channel is never enough.

• Sound — a three-tone sequence, two high notes and a lower one, distinct enough not to be mistaken for a notification from something else.
• Vibration — on phones and tablets that support it, so the timer still reaches you in a room where sound would be rude or useless.

The sound can be muted with the speaker button, and it is worth knowing why you might want to. Browsers block audio until the page has been interacted with at least once, as a defence against pages that blare at you unprompted. Starting the timer counts as that interaction, so in normal use the alert works. But if you loaded the page and never clicked anything, a timer started some other way could be silent. Pressing the speaker button plays a short confirmation tone, which is the quickest way to prove the audio path works before you rely on it.

The obvious advice still applies: if the alert genuinely matters, do not put the tab on a muted device in another room and hope.

Overrun: the number most timers throw away

When it reaches zero, this timer does not stop. It alerts, then keeps counting — into overrun — until you pause or reset it. Most kitchen timers simply stop and sit there, which quietly discards genuinely useful information.

Overrun answers a question you cannot otherwise answer: how late was I? You set fifteen minutes for a break and come back to a timer showing four minutes of overrun. That break was nineteen minutes, not fifteen. A timer that stopped at zero would have told you nothing except that fifteen minutes had passed at some point.

This turns out to matter most for the things people are worst at estimating. Meetings, "quick" phone calls, and breaks all reliably run long, and the only way to find out by how much is to let the clock keep going past the boundary. Over a week the overrun figures are usually more interesting than the durations you set.

Leaving the tab and coming back

Elapsed time is computed from timestamps rather than counted tick by tick, so the countdown stays accurate while the tab is hidden or the screen is off. Come back after ten minutes and the remaining time is right.

The alert is a different matter, and this is where expectations need setting. Browsers throttle background tabs aggressively, so a countdown that reaches zero while its tab is buried may fire its sound late — or, on a phone with the screen off and the browser suspended, not at all until you return. The remaining time will be correct; the interruption may not arrive on time.

The practical rule: for a short timer you are actively waiting on, keep the tab visible. For anything you genuinely need to be interrupted by while the phone is in your pocket, use the mobile app, which hands the deadline to the operating system as a scheduled notification and therefore fires whether the app is running or not.

Keeping a record worth having

A finished countdown can be saved with a label, and the saved session records what you actually spent rather than what you intended to spend. That distinction is the whole point of keeping records at all.

Label the intent, not the number: "afternoon break" is more useful than "15 min", because the duration is already stored and the reason is not. Once you have a few weeks of these, the pattern in the overruns tends to be the finding — the fifteen-minute breaks that are reliably twenty, the half-hour task that has never once fit in half an hour.

Without an account, saved sessions are held for the length of your visit. Registering makes the history permanent and carries over anything you saved as a visitor. For repeating sequences of timers rather than single ones, the interval timer and the cooking timers chain steps automatically instead of asking you to reset between each.