How the stopwatch measures elapsed time
A stopwatch measures an interval, not a time of day. On this page the calculation is: saved elapsed time plus the difference between the current performance timestamp and the timestamp captured when you pressed Start. Pressing Pause adds that difference to the saved elapsed value. Resume records a new starting timestamp, keeping the earlier total. Reset stops measurement and clears both values. This avoids adding a guessed amount every time the display refreshes.
For example, suppose you run for twelve seconds, pause for a conversation, then resume for eight seconds. The result is approximately twenty seconds, because time spent paused is excluded. If you want to measure the entire conversation as well, leave the stopwatch running. Decide what counts as part of the activity before you begin; changing that rule halfway through makes comparisons less useful.
What the digits mean
The reading is minutes, seconds, and hundredths of a second. At one minute and five seconds you will see a value around 01:05.00. Minutes continue upward for longer sessions; this standalone display does not change into a separate hours field. The last two digits make short intervals easier to compare, but they are display precision, not a certification of measurement accuracy. Human reaction time, input processing, and screen refresh all affect a manually started or stopped result.
The page requests a display update every 50 milliseconds while running. A browser can deliver it later when busy. You therefore will not see every possible hundredth on screen. This is expected: the elapsed-time calculation and the visible refresh rate are different things. Press Pause before writing down a result so you are copying a stable reading.
Timestamp differences versus counting callbacks
Imagine a timer that adds 0.05 seconds each time a callback runs. If the browser delays ten callbacks, that implementation can fall behind real elapsed time. Our stopwatch instead recalculates the timestamp difference. A delayed callback changes when you see the updated number, rather than requiring the page to replay all the updates it missed.
The underlying performance.now() API is monotonic: ordinary changes to the system’s wall clock do not move it backward. However, browser and operating-system behavior during sleep differs. A running stopwatch is not a guarantee that suspended-device time is included consistently. Keep the device awake for measurements you want to compare. The MDN performance timestamp reference explains this distinction and documented sleep limitations.
Practical timing examples
- Presentation rehearsal: start on your first spoken word, pause at the end, and record the result with the draft version. Repeat using the same start and finish rule.
- Practice task: measure one attempt, write down the time, then reset. This page has no saved history or export.
- Demonstration: give the operator a clear start signal. A second person can write down observations while the operator controls the stopwatch.
If you need lap readings during an uninterrupted activity, use the stopwatch in the homepage workspace. The standalone stopwatch above intentionally offers only Start, Pause, Resume, and Reset. It does not provide a lap button, finish alarm, or automatic stop at a target duration. For a signal after a known interval, choose a countdown instead.
Before leaving the page
This standalone stopwatch keeps its measurement in the current page’s memory. Reloading, closing the tab, or navigating away resets it. It does not restore this reading from browser storage. Copy any result you need before leaving. Two open stopwatch tabs measure separate sessions; starting one does not control the other.
For informal timing, a quick rehearsal is useful: start, wait a few seconds, pause, resume, and reset once before the actual activity. Check that the controls remain visible at your chosen text size. For official competition, scientific measurements, or any timing where small errors have consequences, use appropriate dedicated equipment and the applicable timing procedure. This browser tool is designed for everyday practice and planning.
By Ed Vaquerano · Updated September 24, 2026 · Editorial policy