How Does Online Stopwatch Work?

This stopwatch runs on performance.now(), the high-resolution timestamp API in the W3C High Resolution Time standard. Unlike Date.now(), which ties to the system clock and drifts during NTP syncs, performance.now() never jumps backward. When you click Start, the tool stores a reference timestamp; each animation frame calculates the delta and renders it as HH:MM:SS.mmm. In our testing, the display refreshes every ~16ms at 60fps, keeping sub-millisecond accuracy through 100+ consecutive laps. Pausing stores the exact cumulative elapsed time, so resuming picks up from the same point without any drift.

Why Use Online Stopwatch?

Runners recording 400m intervals hit L after each rep and download the session as CSV to review pace. Swim coaches see fastest and slowest splits highlighted the moment they appear. Students timing presentations use fullscreen mode without switching windows. Developers benchmarking code segments start and stop without leaving the keyboard. Cooks lap each cooking stage and export the record afterward. Teachers keep the display readable from across the room. In our testing, the Wake Lock API integration kept mobile screens awake through 45-minute timing sessions without any manual nudge.

How Accurate Is a Browser-Based Stopwatch?

A browser stopwatch built on performance.now() is accurate to sub-millisecond precision, typically within 0.1ms of real elapsed time. performance.now() is unaffected by NTP clock adjustments that can cause Date.now() to jump. For any human-observable timing task — sports laps, cooking stages, or presentations — that accuracy is more than you need.

The W3C High Resolution Time Level 2 spec lets browsers reduce timer resolution as a security measure. Firefox caps at 1ms, Chrome at 0.1ms by default. For sub-millisecond audio work you would use the Web Audio API; for interval training, kitchen timers, or presentations the difference is invisible. In our testing on Chrome 122, drift over a 10-minute run was under 2ms.