Time Elapsed: Find the Exact Days, Weeks, or Months Between Any Two Dates

Exclusive counting (the default in most contexts) measures the gap between two calendar points as if you are counting fence posts minus the first or last post. If a project starts on Monday January 1 and ends on Friday January 5, exclusive counting says the gap is 4 days - you moved across 4 intervals to reach the end point.

Inclusive counting treats both the start day and the end day as full working units. Using the same example, January 1 through January 5 counted inclusively equals 5 days, because all five days are days you are actually "in" the period. This matters enormously in legal contracts ("the license shall be valid for 30 days inclusive of the execution date"), hotel billing (check-in Monday, check-out Friday = 4 nights but 5 days inclusive), event planning, and statutory deadlines where the law specifies that the filing day itself counts.

The toggle on this calculator labeled Include End Date (+1 Day) switches between these two modes instantly. When in doubt, read your contract or statute carefully to identify which convention applies.

A leap year is a year that contains 366 days instead of the standard 365, with the extra day added as February 29. The Gregorian calendar rule is: a year is a leap year if it is divisible by 4, EXCEPT for century years (those divisible by 100), which must also be divisible by 400 to qualify. So the year 2000 was a leap year (divisible by 400), but 1900 was not (divisible by 100 but not 400). The next leap years are 2028, 2032, and 2036.

For date duration calculations, leap years matter in two specific ways. First, any period spanning February 29 will be one day longer than an identical period in a non-leap year. A date range of January 1, 2024 to March 1, 2024 is 60 days because 2024 is a leap year; the same range in 2023 is only 59 days. Second, when calculating years and months in components (e.g., "1 year, 2 months, 3 days"), the math must account for the varying lengths of February across years to avoid off-by-one errors.

This calculator uses JavaScript's native Date object, which is built on Unix time (milliseconds since January 1, 1970). All leap year corrections are handled automatically by the runtime without any special-case branching.

Many legal, financial, and operational time limits are expressed in business days rather than calendar days because weekends are generally non-working periods. For example, a US employment contract might specify that an employer has 3 business days to respond to a written request. If you send that request on a Thursday, 3 calendar days later is Sunday - but 3 business days later is the following Tuesday, because Saturday and Sunday are skipped. Getting this wrong can expose a company to legal liability.

Payroll cycles are perhaps the most common practical use case. A bi-weekly payroll that covers a two-week period contains exactly 10 business days, regardless of whether there are 14 or 15 calendar days in that span (due to month boundaries). HR departments track working days to calculate accurate accrual rates for paid time off.

Important note on public holidays: This calculator excludes Saturdays and Sundays but does NOT automatically remove public holidays such as Thanksgiving, Christmas, or regional bank holidays. Holiday schedules vary by country, state, employer, and even year (when a holiday falls on a weekend and is "observed" on a different day). For contracts where holidays matter, you should manually subtract the applicable holidays from the business-day total this tool provides.

The Gregorian calendar is the international civil calendar used by most of the world today. It was introduced by Pope Gregory XIII in October 1582 as a refinement of the older Julian calendar, which had slowly drifted out of sync with the solar year by about 10 minutes per year. The key fix was the updated leap year rule described above (the "divisible by 400" exception), which keeps the calendar aligned with Earth's orbit to within 26 seconds per year.

Different countries adopted the Gregorian calendar at different times - Britain and its colonies switched in 1752, Russia not until 1918, and Greece in 1923. This means that for historical date calculations before the 20th century, you need to verify which calendar system a source is using. A date recorded as "March 1, 1700" in a British document refers to a different absolute moment in time than the same date written in an Italian document from the same period.

For practical modern use - anything after 1923 - this ambiguity does not apply. All countries now use the Gregorian calendar, and any modern date calculator (including this one) operates correctly across those dates. For genealogical research or historical analysis involving dates before the 19th century, consult a specialist resource that handles the Julian-to-Gregorian conversion.

Mistake 1 - Mixing exclusive and inclusive counting. A 30-day notice period that starts today does not end on the same day next month if you miscount. Always confirm with your agreement or policy whether the first and last day are counted. Use the inclusive toggle on this calculator to model both scenarios and compare.

Mistake 2 - Forgetting month-end edge cases. Adding "one month" to January 31 is ambiguous because February 28 (or 29) is the logical end, but March 3 is exactly 31 days later. Contracts should specify "calendar month" vs. "30 days" to avoid disputes.

Mistake 3 - Assuming all weeks have the same number of business days. Weeks that span a public holiday have 4 working days. For payroll that deducts for unworked holidays, you need to count holidays explicitly.

Mistake 4 - Time zone confusion on deadlines. A midnight deadline in New York and a midnight deadline in Los Angeles are 3 hours apart. For electronic filings with the SEC, IRS, or courts, verify the time zone of the receiving system, not the sender's local clock.

Best practice: For any date calculation with financial, legal, or employment consequences, use a tool like this to get the raw number, then have a second person verify the boundary dates before committing to a deadline.