Skip to content

Stopwatch

Start, pause, and resume. Elapsed time is always recomputed from when you started, not incremented tick by tick.

00:00
Need to count down instead of up? See Timer.

Worked example

Started, then checked again 90 seconds later, elapsed time reads exactly 1:30, recomputed fresh from the original start moment rather than accumulated tick by tick. Pause it right at that 90-second mark, wait an untracked 5 minutes, then resume, and the display still reads 1:30 at the moment of resuming, since the entire paused interval is excluded from the running total.

Common mistakes

  • Expecting the stopwatch to keep running if the tab is closed. It only tracks time while the page stays open, whether in the foreground or backgrounded.
  • Assuming a long gap between checks introduces drift. Elapsed time is recomputed fresh from the original start each time, so no amount of backgrounding causes it to fall behind.

Limitations

This is a browser-local utility, not a precision timing instrument suited to competitive or scientific use. A refresh clears the running total completely, since nothing about it is saved between page loads.

Frequently asked questions

Does pausing lose time?
No, the paused duration is excluded from the elapsed total entirely, so resuming picks up exactly where it left off rather than continuing to accumulate time silently.
Why does the display stay correct after switching to another tab and back?
Because elapsed time is recomputed fresh from the original start moment every time the display updates, rather than incremented tick by tick, so a long gap in updates while the tab was hidden does not throw off the total.