Stopwatch Timer
Press Start to begin tracking elapsed time with precision.
How the Elapsed Time Calculator Works
Track any duration with stopwatch precision.
Press Start
Click the Start button to begin the timer. The display immediately begins counting up in hours, minutes, seconds, and milliseconds.
Record Laps
While running, press Lap to capture a split time. Each lap records the individual lap duration and cumulative total for comparison.
Stop Timer
Click Stop to freeze the timer. The elapsed time stays visible, and you can resume by pressing Start again or reset to zero.
Read Results
The summary shows total hours, minutes, seconds, and decimal hours. Lap table records persist until you reset the timer.
What Is an Elapsed Time Calculator?
Understanding elapsed time measurement and how it helps.
Precision time tracking
An Elapsed Time Calculator is a digital stopwatch that measures the duration from when you press Start to when you press Stop. It counts every second, providing a live readout you can use to track work sessions, workouts, cooking times, or any activity.
Unlike a wall clock, which shows the current time of day, an elapsed timer measures relative duration — how long something has been happening.
High-resolution timing
This calculator uses the browser's performance.now() API, which provides sub-millisecond accuracy. Because it calculates elapsed time from timestamps rather than counting intervals, it remains accurate even if the browser tab is inactive or the computer goes to sleep.
Lap splits for detailed analysis
The lap feature lets you break a session into segments. Each lap records the time of that individual segment and the cumulative total. This is invaluable for runners timing splits, engineers benchmarking processes, or anyone comparing the duration of sequential tasks. Count whole calendar days instead with the days between dates calculator.
When to Use an Elapsed Time Calculator
Scenarios where a precision timer makes a difference.
Running & Fitness
Track lap splits during interval training. Record each set duration for weightlifting or time entire marathon training runs with mile-by-mile breakdowns.
Development & Debugging
Time build processes, API response durations, or deployment pipelines. Compare before vs. after optimization by recording elapsed times for each run.
Client Billing
Track billable hours by starting the timer at the beginning of a call or task. Stop when done and log the decimal hours directly to your invoice.
Lab & Experiments
Time chemical reactions, incubation periods, or experiment phases. Use laps to mark phase transitions and measure each stage's duration.
Presentations & Speeches
Rehearse presentations and track total speaking time. Use laps to mark slides or sections, ensuring each segment fits within your allotted time.
Cooking & Baking
Time proofing dough, marinating, or multi-step recipes. Use laps to switch between stages without losing track of total elapsed cooking time.
Step-by-Step Walkthrough
How a raw stopwatch reading becomes a number you can put in a timesheet — and why the conversion order matters.
A lab technician times a calibration run. The stopwatch stops at 2 hours, 47 minutes and 33 seconds.
Flatten the reading into seconds
(2 × 3600) + (47 × 60) + 33 = 7200 + 2820 + 33 = 10,053 secondsThree mixed units become one. Every other conversion is easier from a single base quantity, and this step removes the possibility of a carrying error later.
Running total10,053 seconds
Convert to total minutes
10,053 ÷ 60 = 167.55 minutesUseful whenever a system wants whole minutes. Note that the .55 here is a fraction of a minute — 33 seconds — not 55 seconds.
Running total167.55 minutes
Convert to decimal hours
10,053 ÷ 3600 = 2.7925 → 2.79 hoursThe billing and payroll format. Dividing seconds by 3600 in one step avoids compounding the rounding that a seconds→minutes→hours chain would introduce.
Running total2.79 decimal hours
Check the seconds do not disappear
0.79 × 60 = 47.4 minutes ✓ (47m 33s)Converting back should reproduce the original reading. Here 0.79 hours recovers 47 minutes and change, confirming nothing was lost in the rounding.
Running totalRound-trip confirmed
Round for the destination
Billing (2 dp): 2.79 hours Quarter-hour: 2.75 hours Whole minutes: 168 minutesDifferent systems want different precision. Round once, from the exact figure, rather than rounding a value that has already been rounded.
Running total2.79 / 2.75 / 168
A stopwatch reading of 2:47:33 is 10,053 seconds, 167.55 minutes or 2.79 decimal hours. Convert from seconds each time rather than chaining conversions.
Common Mistakes and Pro Tips
Mistakes that quietly corrupt your numbers
Reading 2:47:33 as 2.47 hours because the digits look like a decimal.
Convert properly: 47 minutes and 33 seconds is 0.79 of an hour, giving 2.79.
Why it matters: The colon-separated reading and a decimal number share a shape but not a meaning. The error understates by 0.32 hours here, and it is hardest to catch precisely when the minute value is large.
Converting seconds → minutes → hours, rounding at each step.
Divide the total seconds by 3600 in a single operation.
Why it matters: Each rounding introduces error, and chaining them compounds it. On long durations the two routes can differ by a full minute, which is enough to break reconciliation against a second source.
Leaving the timer running through a break and reporting the whole reading as work.
Stop the timer at the interruption, or subtract the break from the elapsed total afterwards.
Why it matters: A stopwatch measures wall-clock elapsed time and has no idea whether anyone was present. Unattended running is the most common way a stopwatch reading ends up describing something other than the activity it was meant to time.
Relying on the timer to keep counting after closing the tab or locking the phone.
Note the start clock time as a backup, or use start/end times instead for long runs.
Why it matters: Browser timers can be throttled or suspended in background tabs and on sleeping devices. For anything running over hours, a stopwatch is the wrong instrument — two clock readings are far more robust.
Pro tips
Record the start clock time too
Note the actual time of day when you press start. If the timer is disturbed you can still recover the duration, and you gain a record of when the activity happened, not just how long it took.
Stop for genuine interruptions
A stopwatch cannot tell the difference between working and being away. Stopping deliberately is what makes the reading mean the activity rather than the wall clock.
Do not background long runs
Browser timers are throttled in inactive tabs and suspended on sleeping devices. For durations over an hour, prefer start and end clock times over a running stopwatch.
Match precision to purpose
Seconds matter for experiments and athletic splits. For billing, seconds are noise — round to two decimal places or to your billing interval and keep the raw reading separately.
Verify with a round trip
Multiply the decimal fraction back by 60 and check it reproduces your minutes. It takes seconds and catches every misplaced conversion.
Copy before you navigate
A stopped reading exists only in the page. Move it into your notes, log or invoice before doing anything else with the tab.
Elapsed Time Conversion Reference
Common stopwatch readings in every format, so a raw reading can go straight into whatever system needs it.
| Reading | Total seconds | Total minutes | Decimal hours |
|---|---|---|---|
| 0:00:30 | 30 | 0.50 | 0.008 |
| 0:05:00 | 300 | 5.00 | 0.083 |
| 0:15:00 | 900 | 15.00 | 0.250 |
| 0:25:00 | 1,500 | 25.00 | 0.417 |
| 0:45:00 | 2,700 | 45.00 | 0.750 |
| 1:00:00 | 3,600 | 60.00 | 1.000 |
| 1:30:00 | 5,400 | 90.00 | 1.500 |
| 2:15:45 | 8,145 | 135.75 | 2.263 |
| 2:47:33 | 10,053 | 167.55 | 2.793 |
| 4:00:00 | 14,400 | 240.00 | 4.000 |
| 7:30:00 | 27,000 | 450.00 | 7.500 |
No rows match that filter.
Decimal hours are shown to three places to make the seconds visible; round to two for billing. To measure a span from two clock readings instead of a running timer, use the time difference calculator.
How Elapsed Time Measurement Actually Works
What a browser stopwatch can and cannot promise.
Why browser timers drift in background tabs
Browsers deliberately throttle timers in tabs that are not visible, and mobile operating systems suspend them entirely when a device sleeps. This is a battery-life feature, not a bug.
A well-built stopwatch compensates by recording a timestamp at start and computing elapsed time as the difference against the current clock, rather than counting ticks. That approach survives throttling, because the arithmetic does not depend on the display having updated.
Even so, for durations measured in hours, two clock readings remain more reliable than any running timer — there is simply less that can interfere with them.
Elapsed time versus active time
A stopwatch measures the wall clock, which is a different quantity from time spent working. The gap between them is filled by interruptions, breaks and anything else that happened while the timer ran.
Neither figure is more correct — they answer different questions. Elapsed time is right for "how long did this take end to end", which is what a client or a process owner usually wants to know. Active time is right for "how much effort did this consume".
Decide which one you are measuring before you start, because they cannot be separated afterwards from a single reading.
Precision, accuracy and what to report
A display showing hundredths of a second implies precision that the measurement rarely has. Human reaction time on pressing start and stop is typically 150–250 milliseconds at each end.
That places a practical floor of roughly a quarter-second on any manually triggered reading, however many digits are shown.
Report at a precision the method can support. For anything human-triggered, whole seconds is honest; sub-second figures suggest an instrument that was not actually used.
Converting without losing the seconds
The rule is to convert from a single base unit rather than in a chain. From total seconds:
- Minutes:
seconds ÷ 60 - Decimal hours:
seconds ÷ 3600 - HH:MM:SS: integer-divide by 3600, then by 60, taking remainders
Each derives independently from the exact value, so no rounding is inherited. Chaining conversions — seconds to minutes to hours, rounding at each hop — is where readings quietly lose a minute.
Frequently Asked Questions
Common questions about the Elapsed Time Calculator.
How accurate is this elapsed time calculator?
The timer uses your browser's high-resolution performance API (performance.now()), which provides sub-millisecond accuracy. Display updates occur every 10 milliseconds for a smooth visual experience.
Can I record lap times?
Yes. While the timer is running, click the "Lap" button to record a split time. Each lap shows the individual lap duration and the cumulative elapsed time. You can record unlimited laps.
Does the timer keep running if I switch tabs?
Yes. The timer uses timestamp-based calculation, not interval counting. Even if you switch browser tabs, the elapsed time will be accurate when you return because it calculates from the start time.
Can I use this for billing clients?
Absolutely. Start the timer when you begin work, use laps to mark task transitions, and stop when finished. The total elapsed time in decimal hours is perfect for time-based billing.
What's the maximum duration this timer can track?
There is no practical limit. The timer can track durations of days, weeks, or longer without losing accuracy. The display format expands automatically to show hours beyond 99.
Is my timer data saved?
The timer runs entirely in your browser. Data is not saved between page reloads or sent to any server. If you need to preserve your times, note them down or take a screenshot before leaving the page.
Does the timer keep running if I switch tabs?
Elapsed time is computed from timestamps rather than counted ticks, so the total stays correct even when the display is throttled. That said, for runs lasting hours a pair of clock readings is more robust than any browser stopwatch.
Why is 2:47:33 equal to 2.79 hours and not 2.47?
Because the minutes and seconds have to be converted into a fraction of an hour: 47 minutes and 33 seconds is 0.79 of an hour. The colon-separated reading looks like a decimal but does not behave like one.
Should I convert seconds to minutes first, then to hours?
No. Divide the total seconds by 3600 in a single step. Chaining conversions and rounding at each stage compounds the error, and on long durations the two routes can differ by a full minute.
How precise is a browser stopwatch?
The underlying clock is precise, but human reaction time when pressing start and stop adds roughly 150 to 250 milliseconds at each end. Whole seconds is an honest reporting precision for anything triggered by hand.
Can I pause the timer for a break?
Stop the timer when you step away and note the reading, or subtract the break from the elapsed total afterwards. A running stopwatch measures wall-clock time and cannot tell whether anyone was present.