How to Use a Stopwatch: Laps, Splits and How Accurate Hand Timing Is

A stopwatch answers one question: how long has it been since I pressed Start? It counts up from zero, shows minutes, seconds and hundredths of a second, and measures elapsed time, not the time of day. That makes it the right tool for finding out how long something takes, and the wrong one for being told when something is done.

Start, stop, lap and reset#

The Timelive stopwatch has three buttons and three keys. Everything below comes from the page's own code.

A few details are easy to miss:

• Keys work only when you are not typing. Shortcuts are ignored while a text box has focus or while you hold Ctrl, Cmd or Alt.
• Space presses whichever button has focus. If you just clicked Lap, pressing Space records another lap instead of stopping the clock. Click Stop for that press, or use Space only when no button has focus. L and R still work either way.
• R does not ask first. If you brush it during a long run, the time and the laps are gone. On a phone you will normally use the on-screen buttons, so keep your thumb away from Reset.
• The last stretch is not a lap until you press Lap. At the finish, press Lap, then Stop. If you only press Stop, the final lap is missing from the table.
• Hours work. Past 60 minutes the display switches from mm:ss to h:mm:ss. The newest lap sits at the top of the table.

Timelive says a running stopwatch stays correct in a background tab and picks up where it left off if you reload the page in the same browser. After a reload, Timelive catches up using the device's clock, so changing the system time while the page is closed can shift the result. Do not rely on any of this for a run you cannot repeat: browser storage can be cleared, and a private window may not keep it.

Lap time, split time and overall time#

Take three checkpoints in a run, and think of the stopwatch as running the whole time.

• The cumulative reading is the total time since Start at each checkpoint. Casio's watch manuals call this the split time. Timelive's table calls it Overall.
• The lap reading is the difference between one checkpoint and the one before. Casio defines it as the time for the current segment, and many Casio watches show both readings at once.

The words are not used the same way everywhere. A runner who says "my splits were 1:52, 1:49 and 1:51" often means the time for each segment. The negative split, a race run with the second half faster than the first, compares the times of two halves. So when you read a pacing article, check which kind of "split" it means before you compare numbers. On Timelive, use the Lap time column for segment times and Overall for running totals.

A worked example: four laps of a 400 m track#

A standard outdoor track is built so that one lap of lane 1 measures 400 meters (Miller Sports), so four laps is 1,600 meters. A mile is 1,609.344 meters, which makes 1,600 meters about 0.6% short of a mile (computed). The lap times below are invented for illustration. Each press of Lap stores the running total, and the page then works out the Lap time column by subtracting the previous total.

The total is 7:17.75, and the average lap is about 1:49.4. The gap between fastest and slowest is 8.10 seconds. Timelive subtracts the previous overall time for you.

The highlight starts once you have two laps, colors only the Lap time column and is re-judged each time you add a lap.

Timing a run, a swim, a talk or an experiment#

Running#

For a track, press Lap each time you cross the line. For a road run, press Lap at kilometer or mile markers. The Overall column then gives your elapsed time at each marker and the Lap time column the time for that stretch.

RUN247's guide defines a negative split as running the second half of a race faster than the first. To check your own pacing, press Lap at the halfway mark and again at the finish, then compare the two Lap time values. For a 45:00 10K, an even pace is 4:30 per kilometer (computed); a 23:00 first half and a 22:00 second half would add up to the same 45:00.

A few general habits that suit any timed run:

• Start the stopwatch before you start moving, and keep your eyes on the path. Press Lap at the marker and look at the screen afterward.
• Laps show pace, but they do not replace how you feel. This is not medical advice: if you have a health condition, ask a clinician before pushing hard.

Swimming#

A handheld timer on a pool deck works the same way. Masters Swimming Australia describes pressing LAP when the swimmer first touches the wall, which gives the lap time and the cumulative time, and pressing it again at the next touch for the next segment. For a 100 m swim in a 50 m pool, that is one press at the turn and one at the finish. When you time someone else, your reaction time is the one that counts.

Presentations and speeches#

Rehearse out loud with the stopwatch running. A University of Queensland guide points out that rehearsing in your head runs faster than speaking, so it gives a false length. Published speaking paces vary from about 100 to 160 words per minute (one speaking coach's page discusses them); at 130 words per minute, a 5-minute talk is about 650 words (computed). Press Lap at the end of each section to see where the talk ran long. If you instead want a warning when five minutes are up, switch to a countdown on the timer.

Cooking, chores and experiments#

Use a stopwatch when you do not know how long something takes: a kettle boiling, dough doubling, a commute door to door. Once you have a number, set a countdown next time; How to Use a Pomodoro Timer: 25/5, 52/17, 90-Minute Blocks and Timeboxing shows how to turn a measured time into a timebox.

For something that repeats, such as a pendulum swing, time 10 swings and divide by 10. If your start-to-stop error is typically 0.1 s, each swing's time carries only 0.01 s of it (computed).

How accurate is a stopwatch?#

Two things are being measured, and they are very different in precision.

The clock inside the page#

Timelive reads your device's high-resolution clock, and its page says the measurement is typically accurate to within a millisecond. Browsers deliberately round that clock to make some kinds of attack harder. A 2021 Chromium discussion of timer resolution proposed 100 microseconds on desktop pages that are not cross-origin isolated, and noted that Firefox and Safari already used 1 millisecond (a 2021 figure that may have changed). MDN's reference page, as mirrored by w3cub, lists 100 microseconds for non-isolated pages and 5 microseconds for isolated ones. Even at 1 millisecond, the clock is ten times finer than the 0.01 s on the display, which is shown as hundredths, cut off and not rounded.

Background tabs are a separate issue. Browsers throttle timers in tabs you cannot see; one explainer puts the usual limit at once per second, and Chrome has since added stricter cases. A stopwatch that counted its own ticks would drift, which is why a well-built one, including Timelive's, works out elapsed time by comparing clock readings. What you lose in a hidden tab is the animation, not the elapsed time.

Your reaction time#

The slow part is you. NIST's procedure for calibrating stopwatches names human reaction time, variation in operation and the watch's resolution as the main limits on the result, and requires the person calibrating to have a documented start-and-stop response time. A University of Surrey study modeled a person timing one anticipated event with a stopwatch and found a typical single reaction of about 0.11 s (standard deviation about 0.07 s) and, if the reaction is the same at start and stop, a start-to-stop uncertainty of about 0.10 s (one standard deviation). Other sources commonly quote visual reaction times of roughly 0.15 to 0.3 seconds, and the error shrinks when you can see the start coming. Sources differ: treat 0.1 s as a typical size for an anticipated event, not a limit, because an unprepared person can be slower.

The same absolute error has a very different effect depending on the duration. Using 0.1 s and 0.2 s as examples, the table is simple arithmetic:

Athletics shows why this matters. Athletic.net's guide says hand times are valid only to a tenth of a second and any hundredths are rounded up, so 10.83 seconds is recorded as 10.9. It also gives conversion factors for comparing hand and automatic times, adding 0.24 seconds for races under 300 m, and says they are for comparison only. Wikipedia's entry on fully automatic timing adds that sprint records and sprint qualifying times for the Olympic Games or World Championships must be timed by an automatic system, and a federation document reproducing World Athletics rules also lists fully automatic timing for record events. We found these only in secondary sources, so check the current World Athletics rules if the exact wording matters.

As a rule of thumb (our judgment, not a standard): trust differences of a second or more, treat differences under a quarter of a second as likely noise unless the same person pressed both buttons, and regard the hundredths digit as display detail. For checking your device's own time of day, see How Accurate Is Your Phone or Computer Clock? How to Check and Fix It. How Your Phone Knows the Time: Atomic Clocks, Leap Seconds and the Network Behind Them covers where reference time comes from.

Tips for getting consistent times#

1. Press at the same moment each time. Pick a cue, such as the first foot off the line or the first word spoken, and use it for every trial.
2. Use the same hands. The error is partly a consistent delay. If the same person starts and stops, much of it cancels.
3. Time longer events or repeats. The longer the event, or the more repeats you divide by, the smaller your error in percentage terms.
4. Decide in advance what a lap is and do not change it halfway.
5. Copy the result before you reset. Reset has no undo.

Frequently asked questions

Sources and further reading

1. Module No. 5512 — Casio watch manual (split and lap time definitions)
2. Calibration of Stopwatches and Timing Devices (SOP 24) — NIST
3. University of Surrey study of stopwatch reaction-time error (Open Research record) — University of Surrey Open Research
4. Hand Time Conversion Standards — Athletic.net
5. What is a Negative Split in running? — RUN247
6. Intent to Ship: Align performance API timer resolution to cross-origin isolated capability — Chromium blink-dev
7. How Long Is a Track? + Other Track Measurements — Miller Sports