Days Between Dates

The calculator counts the whole days from the earlier date to the later one, on the real calendar. Order does not matter — it sorts the two dates and returns a positive number. Because it walks the actual calendar rather than multiplying averages, February 29 and the difference between a 30-day and a 31-day month are handled without you doing anything. January 1 to January 31 is 30 days, not 31 — the count measures the gap between the two dates, and that distinction turns out to matter more than it looks.

There are two legitimate ways to count a span and they always differ by one. Exclusive counting measures the gap: January 1 to January 31 is 30. Inclusive counting counts both endpoints as days: the same span is 31 days "inclusive". This calculator is exclusive. The distinction is not academic. A hotel booked from the 1st to the 8th is seven nights but touches eight calendar days — which is why a rate quoted per night and a trip described in days never quite agree. Rental agreements, per-diem allowances and daily-penalty clauses often say "both days inclusive" precisely because the drafter knew about this ambiguity. The rule is simple: if what you are counting is nights, gaps or intervals, use the number as given. If you are counting days on which something happens — days of coverage, days of a rental, days a fee accrues — add one.

The same span reads three ways here. Total days is exact and is what deadlines and countdowns need. Weeks suit anything planned in seven-day blocks. The calendar difference in years, months and days is the human version, the way you would describe an age or how long ago something happened. The three do not convert into one another cleanly, because a month is not a fixed length. "One month" runs from 28 to 31 days, and a month completes when you reach the same day number in the next month, not after any particular count of days. A concrete case: 90 days is not three months. Add 90 days to January 1 and you land on April 1 in a common year but on March 31 in a leap year, because February gained a day. A Net 90 invoice dated the same day in two different years genuinely falls due on two different dates.

A year is a leap year when it is divisible by 4, except that years divisible by 100 are not, unless they are also divisible by 400. So 2024 was a leap year, 1900 was not, 2000 was, and 2100 will not be. The exception exists because a year is not exactly 365.25 days long; dropping three leap days every four centuries brings the average calendar year to 365.2425 days, which tracks the seasons closely enough to last millennia. Any span that crosses a February 29 is one day longer than the same span a year earlier or later. Over a single year the effect is invisible; over a decade of accrued daily interest or a long project schedule it is not.

This calculator works in pure calendar dates, with no time of day and no time zone — which is the right model for contracts, birthdays and deadlines, and the wrong one for anything measured to the hour. The moment a time zone enters, "what day is it" stops having one answer. For several hours of every day, Los Angeles and Tokyo are on different calendar dates, so two colleagues counting days to the same launch get numbers one apart and both are right. A deadline written as "by midnight on the 15th" is genuinely ambiguous across a distributed team until someone names the zone. If hours matter, count from timestamps that carry a UTC offset rather than from bare dates. If only days matter, the plain calendar count here is the cleaner tool — it cannot drift.