Time/Numbers

Duration Calculator

Sum or subtract several durations — handy for tallying worked hours, video length, or total task time.

An empty field counts as 0. The ± button toggles adding/subtracting the row.


                    

Manually adding up several durations written as hours:minutes:seconds is awkward — 45 minutes + 40 minutes isn't simply "85 minutes" in normal notation. This tool adds and subtracts multiple durations at once, correctly carrying minutes into hours.

How to use it

Common uses

Things to keep in mind

If the sum of subtractions exceeds the sum of additions, the result is shown with a minus sign — handy for seeing a shortfall of hours against a target at a glance.

Unlike the date-difference calculator, this tool works with plain durations (hours, minutes, seconds), not specific calendar dates.

Article about this tool: Duration calculator: how to correctly add up hours, minutes, and seconds

Frequently asked questions

How do I add one duration and subtract another in a single calculation?

Each row has its own ± toggle — flip it so that row is subtracted from the total instead of added. Empty fields count as 0.

Does the calculator account for months of different lengths?

No, there are no "months" or "years" fields here — only days, hours, minutes, and seconds in a fixed ratio (1 day = 24 hours). For calculations involving calendar months, use "Date Difference" instead.

What do the "decimal" total values mean?

The same total expressed as a single number with a fractional part — for example, 90 minutes is shown both as "1h 30m" and as "1.5" decimal hours, which is handy for timesheets.

Why can the sum show more than 24 hours?

That's normal and expected — unlike a wall-clock time of day, a sum of durations isn't bounded by a single day. For example, a weekly timesheet can easily total "42h 15m".

What happens if the result is negative?

If the sum of subtractions exceeds the sum of additions, the result is shown with a minus sign — useful, for instance, to see a shortfall of hours against a target.

Articles: Time/Numbers

Unix time: why computers count time from 1970

Why January 1, 1970 became the reference point for time in most computer systems.

Cron expressions: how to decode a task schedule

How to decode an expression like */15 * * * * and know exactly when the job will run.

Number systems: why binary, octal, and hexadecimal exist

Why the color #FF5733 in CSS is written in hexadecimal digits instead of decimal.

Bitwise operations: how AND, OR, and XOR work at the bit level

How bitwise AND differs from logical AND, and why you'd operate on individual bits of a number at all.

Date difference: why counting days is trickier than it looks

Why naively subtracting dates can give the wrong result because of leap years.

Age calculation: why it's not just subtracting years

Why simply subtracting birth years can give an age one year higher than the real one.

Time zones: why UTC isn't the same thing as GMT

Why UTC never changes twice a year, while London time (GMT/BST) does.

ISO 8601 duration: how to write a duration in a standard format

Why PT1H30M means "1 hour 30 minutes," not "1 minute 30 hours."

Week number: why different countries count weeks differently

Why January 1 sometimes falls into week 52 or 53 of the previous year under the ISO 8601 standard.

Roman numerals: how a system with no zero and no place value works

Why IV means 4, not 6, and how the subtraction rule works in Roman numerals.

IEEE 754: why 0.1 + 0.2 doesn't equal 0.3 in code

Why almost every programming language prints 0.1 + 0.2 as 0.30000000000000004.

Number to words: why turn digits into text

Why bank documents write an amount both in digits and in words at the same time.