Add Time Calculator

Add Time Calculator

Add up to 20 durations, mix time units, convert the total, and export the current calculation to a real Excel workbook.

5 entries 30 decimal hours h · min · sec result

Time entries

The example starts with one workweek totaling exactly 30 hours. In “h · min · sec” mode, enter values such as 5 h 30 min. Other units accept a nonnegative decimal number.

5 of 20 entries shown

Live result

Total duration

30 h 0 min 0 sec

Total seconds

108,000

Decimal hours

30

Included entries

5

Average duration

6 h 0 min 0 sec

Example workbook is ready to download.
Total duration is 30 hours.

Entry breakdown

Entry Entered value Input unit Seconds Share of total
Time 1 5 h 30 min h · min · sec 19,800 18.33%
Time 2 6 h 15 min h · min · sec 22,500 20.83%
Time 3 4 h 45 min h · min · sec 17,100 15.83%
Time 4 5 h 55 min h · min · sec 21,300 19.72%
Time 5 7 h 35 min h · min · sec 27,300 25.28%
Each row is converted to canonical seconds first. The share column is the row's seconds divided by total seconds, so the displayed percentages may differ from exactly 100% by a tiny rounding amount.

How to use the Add Time Calculator

What this calculator does

This calculator adds independent time intervals and expresses the same total in the unit you choose. It is useful for work logs, study blocks, project tasks, training sessions, travel segments, media runtimes, and similar duration totals. Every valid row is converted to seconds, summed, and then converted to the selected Result unit. The calculation is about elapsed duration, not a clock-of-day or calendar date, so it does not account for time zones, daylight-saving transitions, leap seconds, or a particular month's actual length.

For technical context, the NIST Guide to the SI lists the standard relationships for minutes, hours, and days: 1 minute equals 60 seconds, 1 hour equals 3,600 seconds, and 1 day equals 86,400 seconds. Those exact factors are used here. Longer calendar-like units are explicitly treated as fixed average durations so that the addition remains deterministic.

When to use it

  • Add a week of shift durations, billable time, or study sessions when each item was recorded separately.
  • Combine mixed units such as 90 minutes, 2.5 hours, and 0.25 day without converting them by hand.
  • Convert a total duration into seconds, hours, days, or another supported unit for reporting or spreadsheet work.
  • Audit how much each time entry contributes to the overall total using the Entry breakdown table.

How to calculate

  1. The calculator opens with a complete demonstration workweek: 5 h 30 min, 6 h 15 min, 4 h 45 min, 5 h 55 min, and 7 h 35 min. The first result is 30 hours, and a validated example XLSX workbook is available immediately.
  2. Replace any Time value with your duration. Leave its Unit at h · min · sec for entries such as “1 h 50 min” or “45 min 20 sec.” If you choose a scalar unit such as Hours or Minutes, enter one nonnegative decimal number such as “2.5” or “90”.
  3. Use Add another time to create more rows, up to 20 total. Remove rows you do not need. Blank rows are ignored, but a nonblank malformed row is rejected and excluded until corrected.
  4. Change Result unit at any time. This converts the already-computed total without altering the source entries. Read Total duration for the selected presentation, then use Total seconds, Decimal hours, Included entries, and Average duration for cross-checking.
  5. Select Download Excel to create a fresh workbook from the current validated controls. The workbook contains Summary, Inputs, and Breakdown sheets with typed numeric cells. Reset is intentionally different from startup: it clears the demonstration data, leaves two blank rows in the neutral h · min · sec mode, clears results, and disables export until at least one complete valid duration is entered again.

Input guide

Time 1, Time 2, and any added Time rows are duration inputs. In h · min · sec mode, they are required only if you want that row included and must contain one or more recognized components such as 3 h 37 min, 44 min, or 12.5 sec. Hours may exceed 24 because these are durations, not clock times. Minutes and seconds may also exceed 59; they are normalized through seconds. Negative values, scientific notation, unsupported text, duplicated unit tokens, and ambiguous comma-decimal forms are rejected rather than silently reinterpreted.

Unit 1, Unit 2, and each added Unit determine how the adjacent value is parsed. Scalar choices accept a U.S.-style decimal number with an optional correctly placed thousands separator. The exact short-unit factors are nanosecond = 10⁻⁹ second, microsecond = 10⁻⁶ second, millisecond = 10⁻³ second, minute = 60 seconds, hour = 3,600 seconds, day = 86,400 seconds, week = 7 days, and fortnight = 14 days. Months use 30.44 days and average years use 365.25 days, matching the stated average-duration assumptions. Decades, centuries, and millennia scale that average year; Leap years use exactly 366 days.

Result unit is a required display control. It does not change the underlying total; it only changes its representation. The h · min · sec result is normalized into whole hours and minutes plus seconds, while scalar units show a decimal value. A common mistake is to read an average month or year conversion as a calendar-date calculation. It is not: adding one “month” here means adding exactly 30.44 days, regardless of which month is on a real calendar.

Output guide

Total duration is the primary sum in the selected Result unit. Total seconds is the canonical aggregate used internally; it is especially useful for checking conversions. Decimal hours divides total seconds by 3,600. Included entries counts only nonblank, valid rows. Average duration divides total seconds by Included entries and formats that mean as h · min · sec. The header pills repeat the entry count, decimal-hour total, and current result format for fast scanning.

The Entry breakdown table has five columns: Entry identifies the row; Entered value preserves the user-facing input; Input unit names the parsing mode; Seconds shows that row after conversion to the canonical base; and Share of total shows the row's proportion of the positive total. A zero-duration row is valid and displays a 0% share when the overall total is positive. If the entire valid total is zero, shares display as 0% rather than implying a division by zero.

Worked example

The startup example adds 5 h 30 min + 6 h 15 min + 4 h 45 min + 5 h 55 min + 7 h 35 min. Adding the hour components gives 27 hours. Adding the minute components gives 180 minutes, and 180 minutes ÷ 60 = 3 hours. Therefore the exact total is 30 h 0 min 0 sec, which equals 108,000 seconds and 30 decimal hours. With five included entries, the average is exactly 6 h 0 min 0 sec. The first-open controls, result cards, breakdown, and XLSX checkpoints all use this same example.

Learn more

The Bureau International des Poids et Mesures explains the SI definition of the second, the base unit used for every conversion in this calculator. For additional writing and conversion conventions, see the NIST guidance on using SI units.

How the time addition model works

Time addition becomes reliable when every row is reduced to one common unit before summing. This calculator uses seconds as that common unit because the second is the SI base unit of time. A value in minutes is multiplied by 60; hours by 3,600; days by 86,400; and smaller decimal subdivisions are multiplied by their exact power-of-ten factor. Once the total exists in seconds, any supported output is one division away.

Compound h · min · sec inputs use the same principle. For example, 2 h 44 min becomes 2 × 3,600 + 44 × 60 = 9,840 seconds. There is no need to manually “carry” 60 minutes into an hour during data entry because conversion to seconds handles normalization automatically. When the total is displayed again as h · min · sec, whole hours are taken first, then whole minutes from the remainder, then seconds from the final remainder.

Average months and years need an assumption

Minutes, hours, and days have fixed relationships in this model. Calendar months do not: they contain 28, 29, 30, or 31 days, and calendar years can contain 365 or 366 days. To keep a duration converter deterministic, this calculator treats a Month as 30.44 days and an average Year as 365.25 days. These are convenient averaging conventions for duration arithmetic, not rules for adding calendar dates. If the real question is “what date is one month after January 31,” use a calendar-aware date tool instead of a fixed-duration converter.

Validation and precision

Malformed input is rejected instead of being cleaned into a different number. For scalar units, commas are allowed only as U.S.-style thousands separators, so “1,500” is valid but “1,5” is not interpreted as 1.5 or 15. Scientific notation is intentionally not accepted in the editable controls. The internal model keeps ordinary JavaScript numeric precision and checks every derived value for finiteness before rendering or exporting. Display values are rounded for readability, while the Excel workbook receives the canonical numeric values rather than rounded text copied from the page.