Days Between Dates Calculator — Calculate Days, Months, Years

Hotel-night counts are exclusive of the check-out day: a Mon→Wed booking (check-in Mon, check-out Wed) is 2 nights (Mon night + Tue night, leaving Wed morning). Contract durations and many legal periods are inclusive of both endpoints — a Mon→Wed contract is 3 days by inclusive-counting convention common in legal contracts (both endpoints counted). Vacation policies vary: some workplaces count both endpoints (5 working days for a Mon→Fri vacation), others count only working days (excluding weekends within the range), others exclude the return day. The toggle in this tool defaults to exclusive (matching hotel-night convention) and adds 1 if you switch to inclusive. Common gotchas: rental contracts often mix conventions (rent days = inclusive, security-deposit return = exclusive); insurance policies count from effective date inclusive to expiry date exclusive; mortgages accrue interest differently across jurisdictions.

Daylight-saving transitions can add or subtract a day at the boundary if you compute durations in local time. EU spring-forward (last Sunday of March, +1 hour) makes clocks jump from 01:00 to 03:00 in CET, so a "1-day duration" computed as local-time difference can come out to 23 hours instead of 24; autumn fall-back gives 25 hours. UK DST follows the same EU pattern; US DST runs on different Sundays (second Sunday of March, first Sunday of November). Southern-hemisphere dates run reverse (Australian DST starts October, ends April). Parsing both dates as UTC midnight (00:00:00Z) sidesteps all of this — the difference in milliseconds is exactly `days × 86,400,000` regardless of which calendar dates fall in DST. The trade-off: if you actually care about wall-clock time across DST (counting how many actual business hours), you have to add the boundary correction back manually.

30.4375 days = 365.25/12, which is the Julian-year average month length. The Gregorian-exact value is 365.2425/12 = 30.436875 days/month — a difference of 0.000625 days (~54 seconds) per month, accumulating ~0.5 hour per year. For ballpark date thinking ("about 6 months from now") the difference is invisible. For multi-year mortgage amortisation, actuarial work, or academic research, you should use Gregorian-exact 365.2425 with explicit leap-year handling, or a calendar-aware library (Temporal API, date-fns, Luxon, day.js as the modern successor to deprecated Moment.js). The tool's "approximate months" output suits project-scope estimation and human-conversation context; for legal/financial precision spanning multiple years, use the dedicated age calculator which does year-and-month math explicitly with calendar-aware clamping.

ISO 8601:2019 (the YYYY-MM-DD format) meets two critical properties simultaneously: it's locale-unambiguous (the US 02/03 = February 3, the EU 02/03 = March 2 — never the same conversation in ISO), and it's lex-sortable as a plain string (so "2024-12-31" < "2025-01-01" gives the correct chronological order without parsing). RFC 3339 (Klyne & Newman 2002) is the IETF profile of ISO 8601 used throughout the web stack: HTTP Date headers, JSON Schema date format, OpenAPI specifications, JWT iat/exp claims, structured log timestamps, RSS/Atom feed dates, ISO database TIMESTAMP columns, JavaScript's Date.prototype.toISOString(). When you write any date to a file, log, or API payload, use ISO 8601. Localised display formats (12/31/2024, 31.12.2024, 31 dic 2024) belong only in user-facing UI rendered just before display.

The Unix epoch 1970-01-01T00:00:00Z (midnight UTC, January 1, 1970) is the reference time origin for the POSIX time_t standard (IEEE Std 1003.1, current revision 1003.1-2024), which Linux, macOS, BSD, and most Unix-like systems use as their internal clock representation. JavaScript inherited the convention from Java in 1995 and codified it in ECMA-262 §21.4: a Date object's internal value is the number of milliseconds since the epoch, stored as an IEEE-754 double-precision float. The double-precision range gives ±100,000,000 days ≈ ±273,790 years from the epoch, with millisecond precision (±0.5–1 ms). The epoch was chosen partly arbitrarily (the original Unix system clock at Bell Labs was 1971; the round-down to 1970-01-01 was ergonomic) and has stuck because the alternative — re-anchoring to a different epoch — would break decades of stored timestamps in databases, log files, and protocols.