Date Difference Calculator

A date difference calculator measures the gap between two calendar dates and expresses it as days, weeks, approximate months, approximate years, and smaller units such as hours or minutes. Typical checks include project duration, leave ranges, invoice periods, anniversaries, retention windows, and simple historical intervals. The result should be understood as a date interval, not automatically as an inclusive count: January 1 to January 3 is a two-day difference unless your business rule says to count both endpoints. Months and years are often approximate because calendar months do not have equal length. For workdays, holidays, time zones, or legal deadlines, use the relevant rule set instead of relying only on the plain difference.

The exact day difference is computed as Math.floor((end.getTime() - start.getTime()) / 86_400_000), where 86,400,000 is the number of milliseconds in a non-DST 24-hour day. This gives an exclusive interval - January 1 to January 3 is 2 days, not 3 - because the subtraction measures the span between two instants rather than counting calendar squares. For inclusive counting (count both endpoints), add 1 to the result; many legal, leave, and billing rules require this and the off-by-one is the single most common cause of disagreements between HR and finance reports. Weeks are simply days / 7; the page also displays hours = days * 24, minutes = days * 1440, and seconds = days * 86,400 as derived totals. Month and year differences are deliberately labeled "approximate" because calendar months and years vary in length. The simple approach is days / 30.436875 (average Gregorian month) and days / 365.2425 (average Gregorian year over a 400-year cycle), which is fine for status reports and dashboards but wrong for contracts. For a calendar-accurate "X full months between", the algorithm subtracts year x 12 + month components and then decrements by 1 if the end day-of-month is earlier than the start day-of-month - this is how most date libraries (date-fns differenceInMonths, dayjs $.diff('month'), Temporal Duration.from) compute it. Year math has the same quirk: 2024-02-29 to 2025-02-28 is sometimes counted as 1 year (clamping to month-end) and sometimes as 0 years 11 months 30 days, depending on the convention. Leap years follow the Gregorian rule (divisible by 4, except centuries not divisible by 400, so 1900 = common, 2000 = leap, 2024 = leap). A span that includes February 29 picks up an extra day automatically because the day count is anchored on milliseconds since epoch, not on calendar fields. Timezone handling is critical when the two endpoints are at sub-day resolution: subtracting two Date values constructed from local-time strings can be off by the local UTC offset, and a span that crosses a DST transition can be 23 or 25 hours rather than the nominal 24. The Y2038 problem (Unix time_t signed 32-bit overflow on 2038-01-19T03:14:07Z) does not affect this page because JavaScript Date uses a 64-bit float capable of representing dates up to roughly 100 million days either side of the epoch, but downstream systems written in 32-bit C still need attention.

• Exact days = Math.floor((end - start) / 86_400_000); 86.4M ms per non-DST day.
• Result is exclusive by default: Jan 1 to Jan 3 = 2 days; add 1 for inclusive counting (both endpoints).
• Approximate month uses average 30.436875 days; year uses 365.2425 days over the 400-year Gregorian cycle.
• Calendar-accurate month diff: (y2-y1)*12 + (m2-m1) then -1 if end day < start day - matches date-fns differenceInMonths.
• Leap years: divisible by 4, except centuries must be divisible by 400 (1900 no, 2000 yes, 2024 yes).
• DST transitions create 23h and 25h calendar days; a 24h subtraction may not equal one calendar day.
• JavaScript Date is a 64-bit float, immune to Unix Y2038 (32-bit time_t overflow at 2038-01-19 03:14:07 UTC).