How this calculation works
Wall-clock mode compares the entered date/time labels without assigning a location. Offset mode subtracts each endpoint’s declared UTC offset before taking the elapsed difference. A separate calendar decomposition counts complete years and months by clamping the original start day to the last valid day of the target month, then counts the remaining days, hours, minutes and seconds. Calendar components and fixed-hour totals are deliberately distinguished.
Elapsed seconds = (end local clock − end offset) − (start local clock − start offset)A worked example
31 January 2026 at 12:00 to 1 March 2026 at 13:30 is 29 days and 1.5 hours, or 2,511,000 seconds. Under the stated month-end rule, its calendar form is one month, one day, one hour and thirty minutes. A 24-hour day is not one calendar month.
Good to know
No geographic time-zone database or automatic daylight-saving inference. Enter the appropriate offsets at both endpoints if you know them. Calendar decomposition uses the written wall clocks, while offset totals measure elapsed time. Years 1–9999, whole-second resolution, no leap-second model.
Reference: US Naval Observatory: time systems and calendars (opens in a new tab) ↗
Calendar components and elapsed hours answer different questions
A calendar month has no fixed number of hours. This tool therefore reports calendar years and months separately from total seconds and fixed twenty-four-hour days. The original start day is clamped to the target month’s final valid day when a whole-month anchor is formed, avoiding an unexplained overflow from February into March.
For 31 January to 1 March in the example year, that rule finds a February month-end anchor and then counts the remaining day and clock time. The date difference calculator instead reports a pure day interval and explicitly labeled average-month comparisons. Neither convention should be mistaken for the other.
Offset mode uses the offsets you enter at each endpoint
An offset in minutes east of UTC is subtracted from the local clock label to obtain the corresponding UTC instant. If the endpoint offsets differ, elapsed hours can differ from the wall-clock difference. Entering start 01:30 at +60 minutes and end 03:30 at +120 minutes describes one elapsed hour, despite a two-hour difference in written clocks.
The page does not infer a city’s daylight-saving rules. It also does not represent leap seconds, which are a separate timekeeping issue. The day of the week calculator operates on plain dates without any clock conversion. Choose the interpretation before using a duration for payroll, travel or scheduling; a precise output does not resolve an unspecified time zone.
A few questions, answered
Does the tool know my city’s daylight-saving changes?
No. Offset mode uses the two offsets entered explicitly.
Does one month mean thirty days?
No. Calendar components use a stated month-end anchor rule.
Are negative durations accepted?
No. End must not precede start under the chosen elapsed-time assumptions.