Days Between Dates Calculator

Counting days between two dates seems like it should be simple — but February, leap years, and whether you count the start date, end date, or both introduce enough complexity that most people's mental arithmetic leads to off-by-one errors. Whether you're calculating a contract deadline, determining how many days until a vacation, figuring out a billing period, or tracking how long ago something happened, the right calculation matters.

Calculating Duration in Days for Common Scenarios

Pregnancy due date counting: gestational age is calculated from the first day of the last menstrual period (LMP). A full-term pregnancy is 280 days (40 weeks) from the LMP. The due date is exactly 280 days after the first day of the LMP. Counting from a known LMP to today gives gestational age in days; dividing by 7 gives gestational weeks.

Age in days is a surprisingly meaningful number for some applications. Neonatal medicine tracks infant age in days for the first 28 days. A baby born July 14 at gestational age 37 weeks + 2 days — what is the baby's corrected gestational age on September 1? Days between July 14 and September 1: July has 31 days, so remaining July days = 17, August = 31, September 1 = 1 day = 49 days. Gestational age at birth: 37 weeks + 2 days = 261 days. Corrected gestational age September 1: 261 + 49 = 310 days = 44 weeks + 2 days.

Business days between dates require accounting for weekends and holidays. A "5-business-day" shipping estimate from a Monday: days counted are Monday, Tuesday, Wednesday, Thursday, Friday = 5 business days, arriving by end of Friday. An order placed Thursday with a 5-business-day estimate: Thursday, Friday, Monday, Tuesday, Wednesday = delivery by end of Wednesday (skipping the intervening weekend). This calculation requires knowing the specific days of the week, not just the calendar day numbers.

The Basic Date Difference Calculation

The number of days between two dates equals the difference in their "day numbers" — where each date is expressed as a count of days from some reference point. The Julian Day Number is one such system, dating to 4713 BCE in astronomical calculations. More practically, most software counts days from a reference epoch (January 1, 1970 for Unix timestamps; January 1, 1900 for Excel).

The manual calculation approach: convert both dates to a serial day number, then subtract. For dates within the same calendar year, the simpler approach works: use a running day-of-year number (January 1 = day 1, February 1 = day 32, etc.) and subtract. March 15 = day 74; July 4 = day 185. Days between March 15 and July 4 = 185 - 74 = 111 days. But this only works within a single calendar year, and you must remember to add 1 for leap years when crossing February.

For multi-year date differences, the calculation becomes: (end year - start year) × 365, plus the day-of-year difference, plus the number of leap years between the two dates. A leap year occurs in years divisible by 4, except centuries not divisible by 400 (so 1900 was not a leap year, but 2000 was). Getting the leap year count right is where manual calculation gets error-prone.

Related Calculators

• Date Difference Calculator
• Business Days Calculator
• Days Until Calculator

Inclusive vs. Exclusive Counting

Whether you count the start date, end date, both, or neither creates a persistent source of confusion. If you rent a hotel room checking in on March 10 and checking out on March 15, how many nights did you stay? 5 nights (10, 11, 12, 13, 14 — the end date isn't a night you stayed). The same date difference of 5 days, but different interpretation based on context.

Legal and contractual date counting follows specific conventions. In most legal contexts, a period "from" a date begins the day after that date. A 30-day notice period "from March 1" typically begins March 2 and expires March 31. But "within 30 days of signing" often means by day 30, counting the signing date as day 1, making the deadline day 30 (not day 31). These distinctions are not academic — missing a legal deadline by one day because of counting method confusion can have serious consequences.

A billing period from January 1 through January 31 is 31 days (inclusive of both endpoints). A subscription billed "monthly from January 1" typically means the next billing date is February 1 — 31 days later — not 30 days later, even though 31 - 1 = 30 by simple subtraction. Days in the period = end day number minus start day number plus 1 when both endpoints are included.

Date Arithmetic Across Month Boundaries

Month boundaries create irregular day counts that trip up people counting manually. Adding 30 days to January 15: January has 31 days, so 30 - (31-15) = 30 - 16 = 14 days into February = February 14. Adding 30 days to January 31: 30 - 0 remaining January days = 30 days into February. But February has only 28 days (or 29 in a leap year). Day 30 of February = March 1 (or March 2 in a leap year).

This ambiguity is why "one month later" is not the same as "30 days later." One month after January 31 is typically February 28 (or 29) — the last day of February. One month after March 31 is April 30. One month after August 31 is September 30. The "same day next month" convention collapses to the last day of the shorter month when the starting date exceeds the destination month's length.

"30 days from today" is unambiguous (add exactly 30 days). "One month from today" is ambiguous without a convention for month-end handling. Contracts and legal documents that specify "one month" rather than a specific number of days create interpretation disputes in edge cases. The cleaner specification is always a specific number of days when precision matters.

Leap Year Considerations

Leap years add one extra day (February 29) to years divisible by 4, except century years not divisible by 400. This affects date difference calculations for any period spanning a February 29 in a leap year. The dates where leap years matter most: any period starting before March 1 in a leap year and ending after February 28 is one day longer than the same calendar span in a non-leap year.

February 28, 2024 to March 1, 2024 = 2 days (because 2024 was a leap year, so February 29 exists). The same February 28 to March 1 in 2025 = 1 day. Anyone calculating "days from February 28 to March 1" manually without checking whether the year is a leap year will get the wrong answer half the time.

For long-period calculations, the number of leap years in the range matters. Years 2000-2024 include 7 leap years (2000, 2004, 2008, 2012, 2016, 2020, 2024). The total days in this 25-year span = 25 × 365 + 7 = 9,132 days. Forgetting to add the leap days produces a 7-day error on a 25-year calculation.

Tools and Practical Tips

Online date calculators and programming languages handle all these complications automatically. Python's datetime module, JavaScript's Date object, and Excel's DATEDIF function all correctly account for leap years, month lengths, and day-of-week patterns. Use them rather than manual arithmetic for anything requiring precision.

For recurring checks like "how many business days until the contract deadline?", building a simple calendar view with weekdays marked makes the counting visual and error-resistant. Count only the colored (business day) cells between your start and end dates, and you can't get the day-of-week component wrong.

The most important habit for date arithmetic is specifying your counting convention explicitly. "Days remaining" might mean up to and including the deadline (inclusive counting) or strictly before the deadline (exclusive counting). "By December 31" and "before December 31" are different deadlines. Document your convention when it matters, and verify that the other party uses the same convention when any ambiguity could cause problems.