Stopwatch & Timer

How this stopwatch measures time

Many online stopwatches work by adding one to a counter every hundredth of a second. That approach drifts: if the browser is busy or the tab is pushed to the background, some of those ticks are delayed or skipped, and the displayed time falls behind real time. This page does it differently. When you press Start it records the current clock reading, and every time the display refreshes it shows now minus start, plus whatever time was banked before the last pause. A skipped refresh therefore does no harm, because the next one recomputes the correct value from the clock.

The clock source in the code is Date.now(), the system wall clock in milliseconds. It is not the monotonic performance.now(). In practice that means the reading follows your device's clock, so if the operating system steps the time (for example a manual change or a network time correction) while a run is in progress, a measurement could in principle jump. Daylight-saving switches do not matter, because the value is a count since a fixed UTC moment. For everyday timing this is rarely noticeable, but it is a real property of the method and a reason not to use the page for anything that needs certified accuracy.

The display shows hundredths of a second, but the screen is refreshed roughly every 30 milliseconds, so the last digit is there to be read by eye rather than to claim instrument-grade precision. Your own finger reaction when pressing a button usually adds 0.1 to 0.3 seconds, which is larger than anything the display could resolve. Treat the tool as good for time management at the scale of seconds and for comparing your own results from one attempt to the next. Do not use it for official race times or as legal evidence.

Why the countdown stays accurate

The timer uses the same idea. At the moment you press Start it stores end time = now + remaining time, and every 250 milliseconds it computes the remaining seconds from that end time, rounded up. Browsers often throttle timers in background tabs, sometimes to about one call per second or less, but because the display is derived from the stored end time, the right figure appears as soon as you return to the tab. While the countdown runs, the remaining time is also shown in the browser tab title so you can see it from another tab.

There are limits. If a phone screen turns off or the browser discards the tab to free memory, the page may not get a chance to play the alarm. For anything that matters, such as medication or a meeting, use your device's built-in alarm as well.

Reading laps and splits

Pressing Lap records two numbers. The split is the time from the previous lap (or the start) to this lap. The total is the elapsed time since you started. On a track, the split is one lap's time and the total is the running clock. Once you have three or more laps, the fastest split is shown in green and the slowest in red, which makes an uneven pace easy to spot. The line above the list shows the number of laps and the average split. Copy times puts the lap number, split and total on separate lines separated by tabs, so it pastes cleanly into a note or spreadsheet. The list is newest first.

The code does not cap the number of laps. Every new lap redraws the list from the beginning, so a very long session with thousands of laps may feel slower, but ordinary use is fine. Laps are only recorded while the stopwatch is running.

Example 1: pacing five laps of a 400 m track

Suppose you run 2,000 m on a 400 m track and press Lap each time. Your splits are 92.4, 90.1, 91.8, 93.5 and 89.7 seconds. The running totals are 92.4, 182.5, 274.3, 367.8 and 457.5 seconds, which is 7 minutes 37.5 seconds. The average split is 457.5 / 5 = 91.5 seconds. A kilometre is 2.5 laps, so the average pace is 91.5 x 2.5 = 228.75 seconds, about 3:48.8 per kilometre. The fastest lap was the fifth at 89.7 seconds and the slowest the fourth at 93.5, a spread of 3.8 seconds. That pattern, fading on lap four and finishing hard, suggests starting a touch more conservatively to even things out.

400 m lap time converted to pace per kilometre

The table multiplies one lap by 2.5 for a kilometre and by 12.5 for five kilometres, computed when the page is built. In reality most people slow down over longer distances, so treat the 5 km column as an optimistic ceiling rather than a forecast. For pace conversions of any distance, try the Running Pace Calculator.

Example 2: turning minutes and seconds into total seconds

The timer converts what you type into total seconds with total = minutes x 60 + seconds. Three minutes 20 seconds is 3 x 60 + 20 = 200 seconds, and 12 minutes 45 seconds is 12 x 60 + 45 = 765 seconds. If you type more than 59 into the seconds box, say 90, the timer carries it over instead of rejecting it, so 0 min 90 s becomes 1 min 30 s. The maximum is 999 minutes 59 seconds, about 16.7 hours.

Ways to use it

• Rest between sets. Heavy lifting is commonly rested for two to three minutes or more, and moderate-intensity work for one to two, though the right length depends on the exercise and the person. The 1 and 3 minute presets are quick to reach.
• Cooking. Pasta, eggs and steamed dishes change texture within a minute. Set the time from the recipe, press Start, and let the end beep be your cue.
• Focused work. The 25 minute preset gives you a single focus block. If you want automatic cycles of work and break, the Pomodoro Timer switches for you.
• Speech practice. Set the talk length on the timer, then use laps on the stopwatch to log how long each slide takes and see which part runs long.
• Countdown to a date. For events days or weeks away, the D-Day Countdown Calculator is a better fit than a timer.
• Converting durations. The Unit Converter handles time units and many others.

Common mistakes and limits

• Lap is not stop. Lap leaves the clock running and just notes the moment. Press Stop to pause. Laps cannot be added while the watch is stopped.
• Reset erases everything. It clears the time and every lap. Use Copy times first if you want to keep them. Refreshing or closing the page also loses the data, because nothing is saved to a server or to the browser.
• No sound. A muted device, a silent switch or a browser autoplay block can prevent the beep. Watch for the "Time's up!" message and the tab title change as a backup.
• Keyboard shortcuts. Space starts and stops the stopwatch and L records a lap, but only when the focus is not in a number box, a drop-down or on a button. After you click a button with the mouse, the focus stays on it, so click an empty part of the page first if the shortcut seems dead.
• Not for millisecond work. Official athletic or swimming times need dedicated timing hardware.

Making the numbers useful

Measurements pay off when you keep and compare them. Timing the same route or routine each week and noting the result shows your improvement over a month, and aiming to shrink the gap between your fastest and slowest lap is a simple way to practise even pacing. For work, logging how long a task really took improves your next estimate. If you guessed one hour for a report and the stopwatch said 100 minutes, a fair correction is to allow about 1.7 times your first guess on similar tasks (100 / 60 is about 1.67). A few such measurements make a schedule far more realistic.

Frequently Asked Questions