What "Time Between Dates" Actually Means
Subtracting one date from another sounds trivial — and at the level of milliseconds, it is. The modern Gregorian calendar maps every wall-clock instant onto a number on a real timeline, and any two such instants have a perfectly well-defined duration in seconds. The complications start the moment you try to express that duration in human-friendly units. A "month" is not a fixed number of days; it can be 28, 29, 30, or 31. A "year" is 365 or 366. "Three months from January 31" could land on April 30 or May 1 depending on the convention you pick, and both are defensible. This is why every legal contract that uses date math also defines exactly how it counts months, and why every spreadsheet has at least three different DATEDIF behaviours.
The calendar most of the world uses today is the Gregorian calendar, introduced by Pope Gregory XIII in 1582 to correct a 10-day drift that had accumulated under the Julian calendar since the Council of Nicaea in 325 AD. The Gregorian rule for leap years — "every four years, except century years not divisible by 400" — keeps the calendar aligned with the tropical year to within one day every 3,236 years. The international standard ISO 8601specifies how dates and durations should be written and computed for unambiguous machine exchange, using the format YYYY-MM-DD and the proleptic Gregorian calendar (extended back indefinitely so that historical dates can be expressed consistently).
The Calculation Method
This calculator uses two distinct strategies and reports both. The exact total in days, hours, minutes, and seconds is computed from the timestamp difference. The human-friendly "Y years, M months, D days" breakdown is computed by calendar walk-forward from the start date.
Total days = (end_timestamp − start_timestamp) ÷ 86,400,000 ms
Y/M/D breakdown: increment year, then month, then day, borrowing from the previous month when day overflows
Business days = sum of weekdays in the inclusive range
Both methods agree on total span; they only differ in how the span is presented. Legal documents and lease agreements typically use the calendar walk-forward method, which is why "a 3-month lease starting January 31" ends on April 30, not on day 90.
How to Use It Step-by-Step
- Pick a start date. The default is today; click the field to choose any other date.
- Pick an end date. The default is one year from today.
- If the end date is earlier than the start date, the calculator silently swaps them so the result is always a positive duration.
- Read the "Y, M, D" breakdown for human contexts (age, contract terms, anniversaries).
- Read the total-days, total-weeks, or total-hours figures for project planning, billing, or countdowns.
- The business-days count excludes Saturdays and Sundays only — not public holidays, which vary by country.
Worked Examples
Example 1 — A 12-month lease
Start 2025-03-15, end 2026-03-15. Y/M/D breakdown: 1 year, 0 months, 0 days. Total days: 365 (2026 is not a leap year). Business days (Mon–Fri): 261. Weekends: 104. This is the canonical "one year" lease in calendar terms.
Example 2 — Born 1992-08-15, today 2026-04-28
Y/M/D breakdown: 33 years, 8 months, 13 days. Total days: 12,309. Approximate weeks: 1,758. The Y/M/D figure is what you would put on a birthday card; the total-days figure is what an actuary or insurance underwriter would feed into a mortality table.
Example 3 — Project ending across a leap year
Start 2024-01-01, end 2024-12-31. Total days: 365 (2024 is a leap year, so February has 29 days; the inclusive endpoint count is still 365 because the calculation rounds down the inclusive last second of December 31). Business days: 262. The February 29 is counted exactly once like any other date.
Gregorian, Julian, and ISO 8601
The Julian calendar, introduced by Julius Caesar in 45 BC, declared every fourth year a leap year without exception. That rule overshoots the tropical year by about 11 minutes per year, which adds up to a full day every 128 years. By 1582, when Pope Gregory XIII commissioned the reform, the Julian calendar had drifted 10 days out of alignment with the spring equinox. The Gregorian reform skipped 10 days (October 4, 1582 was followed by October 15) and modified the leap-year rule: a year is a leap year if divisible by 4, unless it is divisible by 100 but not by 400. Catholic countries adopted immediately; Protestant Britain held out until 1752 (skipping 11 days then), and Orthodox Russia until 1918 (skipping 13). For dates before each country's adoption, software typically uses the "proleptic Gregorian" rule specified in ISO 8601.
ISO 8601 (most recent edition: ISO 8601-1:2019 / 2:2019) is the international reference for date and time representation. It mandates the year-month-day order with hyphens (YYYY-MM-DD), uses 24-hour times with optional fractional seconds, defines durations in the PnYnMnDTnHnMnS format (e.g. P1Y3M5D for "1 year, 3 months, 5 days"), and is the basis for RFC 3339, the date format used in JSON APIs and almost every modern web standard.
Business Days, Holidays, and Time Zones
The business-day count here excludes Saturdays and Sundays only. Public holidays are not subtracted, because holiday calendars are jurisdiction-specific: 11 US federal holidays, 8 UK bank holidays, 16+ South Korean public holidays, and so on, with frequent year-to-year shifts (Easter moves; New Year's Day on a Sunday gets observed on Monday in some countries and not others). For an exact working-day count in your jurisdiction, subtract your region's holiday count from the calculator's business-day figure. Time zones add another layer: a date that begins April 28 in Seoul (UTC+9) is still April 27 in New York (UTC−4). This calculator treats each chosen date as a calendar date in your local time, which is the convention almost every contract and legal document uses unless it explicitly says otherwise. Daylight saving transitions are handled correctly because the underlying timestamp math is in milliseconds since the Unix epoch.
Common Misconceptions
- "A month is 30 days." Sometimes. Months can be 28, 29, 30, or 31 days. Treating "month" as exactly 30 days is fine for rough estimates and wrong for legal documents.
- "A year is 365 days." 365 in common years, 366 in leap years. The Gregorian rule: divisible by 4, except century years unless also divisible by 400. So 2000 was a leap year; 1900 was not; 2100 will not be.
- "Business days excludes holidays." Not in this calculator. Public holidays vary by country and would require a jurisdiction-specific holiday calendar to subtract correctly.
- "ISO 8601 dates are mm/dd/yyyy." No — that is the US locale format. ISO 8601 mandates yyyy-mm-dd specifically because it sorts lexicographically.
- "Subtracting timestamps gives the right answer for 'months between'." Only as an estimate. Calendar walk-forward is the right method when months and years matter, because timestamp subtraction implicitly assumes a fixed month length.
Frequently Asked Questions
How does it calculate months when they have different lengths?
It uses calendar walk-forward: roll the year forward, then the month, then borrow the previous month's day count if the day overflows. This is the same method used by legal contracts and most spreadsheet DATEDIF implementations.
Does it account for leap years?
Yes. Total days are computed from the real timestamp difference, so February 29 is counted exactly once when it falls inside the range. The Gregorian leap-year rule (divisible by 4, except century years unless divisible by 400) is fully respected.
Are public holidays excluded from the business-day count?
No. The business-day count only excludes Saturdays and Sundays. Holidays vary by country and region, so they are not subtracted automatically. For an exact local working-day count, subtract your region's holiday count from the business-day total.
What if my start date is later than my end date?
The calculator silently swaps them so the result is always a positive duration, and shows a small note that the swap occurred. The numerical answer is identical either way; only the sign convention changes.
Does it handle dates before 1900?
Yes, using the proleptic Gregorian calendar specified in ISO 8601. Note that the actual historical calendar in your country before its Gregorian adoption (e.g. 1752 in Britain, 1918 in Russia) was Julian, so historical dates may differ from contemporary documents by 10–13 days.
Is my data stored?
No. Every calculation runs entirely in your browser. The dates you choose are never uploaded, logged, or retained.
References
- International Organization for Standardization. ISO 8601-1:2019 Date and time — Representations for information interchange — Part 1: Basic rules.
- U.S. Naval Observatory, Astronomical Applications Department. Calendar Conversion and the Gregorian Reform.
- Klepper R. The Gregorian Reform of the Calendar. Vatican Observatory Publications, 1983.
- Internet Engineering Task Force. RFC 3339 — Date and Time on the Internet: Timestamps, July 2002.
- Reingold EM, Dershowitz N. Calendrical Calculations, 4th edition. Cambridge University Press, 2018.