Online Stopwatch
A simple online stopwatch with start, pause and reset, shown to the hundredth of a second. Time comes from the system clock, so it stays right in background tabs.
The interactive tool loads here when JavaScript runs.
About this toolWhat is Online Stopwatch?
The Online Stopwatch counts up from zero with Start, Pause and Reset buttons, and shows minutes, seconds and hundredths (MM:SS.cc). Past an hour it adds the hours in front, for example 1:02:03.04. A fullscreen button gives a large display for a classroom, gym or stage.
Elapsed time is calculated from timestamps, not by counting timer ticks. When you press Start the page records the current time; the display is the difference between now and that moment plus any time banked before a pause. Switching tabs, locking a phone screen briefly or a busy CPU can make the display update less often, but the number you see when you come back is correct.
There are no laps or split times; it is a single start-pause-reset stopwatch.
- Start, pause and reset
- Hundredths of a second, with hours after 60 minutes
- Timestamp-based, so background tabs do not slow it down
- Fullscreen display
- Runs in your browser with nothing to install
Updated
How to use Online Stopwatch
- Press Start to begin counting.
- Press Pause to freeze the time; press Start again to continue from the same value.
- Press Reset to return to 00:00.00.
- Use the expand icon on the card for fullscreen; the minimize icon or Esc leaves it.
Worked examples
Pausing and resuming
Input
Start, wait 10 s, Pause, wait 39 s, Start, wait 2.5 s
Output
00:12.50
Time while paused is not counted. The stopwatch banks 10 s at the pause and adds the 2.5 s from the second run.
Long timing
Input
Run for 1 hour, 2 minutes, 3.04 seconds
Output
1:02:03.04
Hours appear once the count passes 59:59.99, so long sessions do not read as 62 minutes.
Background and insight
A common way to build a browser stopwatch is setInterval(() => time += 10, 10). It looks fine in a quick test and is wrong in practice. The HTML standard clamps nested timers to at least 4 ms, browsers throttle timers in background tabs to once per second, and Chrome's intensive throttling can hold chained timers in a tab hidden for more than five minutes to once per minute. Every missed tick is lost time, so such a stopwatch runs slow, sometimes by a factor of a hundred.
Measuring with timestamps avoids all of that. The interval here exists only to repaint the digits about 30 times a second; even if it fires once a minute, elapsed = now - start is still exact. The page also repaints the moment a hidden tab becomes visible again.
The hundredths digit is truncated, not rounded, as on a sports stopwatch: 1.239 s shows as 00:01.23. Human reaction time on a button is around 0.2 seconds, so the last digit is display precision, not measurement accuracy.
Common use cases
Presentations and talks
Time a rehearsal on a second screen in fullscreen so the number is readable from across the room.
Workouts
Time a plank, a run or rest periods without installing an app.
Classroom activities
Show students how long an exercise has taken on a projector.
Rough benchmarks
Time a build, a page load by eye or a manual process to the nearest second.
Tips and limitations
- Closing or reloading the tab loses the time; it is not saved.
- If your computer sleeps, the stopwatch includes the sleep time when you wake it, because it measures wall-clock time.
- Large system clock corrections (for example a manual clock change) shift the reading; normal NTP adjustments are tiny.
- For code benchmarks, use performance.now() or a profiler instead of a human-operated stopwatch.
Sources and further reading
- HTML Standard: Timers, WHATWG. Where nested timers are clamped to at least 4 ms
- Heavy throttling of chained JS timers beginning in Chrome 88, Chrome for Developers. Intensive throttling of hidden tabs to once per minute
- Performance: now() method, MDN Web Docs. Monotonic timestamps for measuring elapsed time
Frequently asked questions
Does the online stopwatch keep running if I switch tabs?
Yes, and it keeps correct time. The stopwatch stores the moment you pressed Start and computes elapsed time from the clock, so a background tab that updates rarely still shows the right value as soon as you return to it.
How accurate is a browser stopwatch?
This one is as accurate as your system clock, which is typically within milliseconds over an hour. The display shows hundredths of a second, but pressing a button by hand adds about 0.2 seconds of human reaction time, which is far larger than any timing error.
Why do some online stopwatches run slow?
They add a fixed amount on every timer tick. Browsers delay ticks under load and throttle them in background tabs, sometimes to once a minute, and each delayed tick is lost time. This stopwatch measures the difference between timestamps instead, so missed ticks do not matter.
Does this stopwatch have lap times?
No, it has start, pause and reset only. For splits, note the displayed time at each point or pause and write it down. Lap and split recording may be added later.
Can I use the stopwatch in fullscreen on a projector?
Yes. Click the expand icon on the stopwatch card and the browser enters fullscreen with large digits and the Start and Reset buttons. Press Esc or the minimize icon to return.
Is there an in-depth guide to Online Stopwatch?
Yes. “Stopwatches, Countdown Timers and Clocks in the Browser: Why Time Drifts” covers the background, how it works, common pitfalls and worked examples. Read the full guide.
Related Tools You May Like
Free, in-browser tools that pair well with this one.