Online Timer

Yes. It works from a target time rather than counting ticks, so background throttling cannot make it lose time. The tab title keeps showing the remaining minutes and seconds.

In most browsers yes, because audio was already unlocked when you pressed start. Some mobile browsers suspend audio in background tabs; if that matters, keep the tab visible.

Browsers block audio until a user action, and rightly so. Pressing start is that action, which is why the alarm needs no permission dialog and no test button.

Yes. Minutes and seconds are not clamped to 59, so 90 minutes or 150 seconds are both fine. The total is capped at 99 hours.

The timer resets. It deliberately stores nothing, so a shared or public computer keeps no trace of what you were timing.

No — a timer counts down from a duration you set, a stopwatch counts up from zero and records laps. For measuring how long something took, use the stopwatch.

Not directly; this counts a duration. For a specific date and time, the countdown-to-date tool shows the days, hours and minutes remaining until then.

No. Pause banks exactly the seconds that were left and resume continues from there, so a paused-and-resumed timer runs for the full duration.

Remaining time is rounded up on purpose, so a running timer never shows 0. Zero appears at the moment the alarm fires and not a moment before.

One per page, but you can open the tool in several tabs — each keeps its own countdown, and each shows its remaining time in its own tab title.

Once the page has loaded, yes. The timer and the alarm are entirely local, with no network calls after the initial load.

No. There is no account, no sync and no upload — the countdown exists only in this page.