Days Between Dates Calculator
Count calendar days between two dates without using local-clock elapsed hours. Weekends and holidays still count; the end date is excluded unless the inclusive option is checked.
- Explicit formulas and worked examples
- Check your inputs, then calculate
- Data is calculated in this browser only
Check the stated input format, calculation convention and limits before using the result.
Check the example inputs, then calculate. Your values stay in this browser.
The end date must be on or after the start; equal dates give zero, or one when the end is included.
Understand the Days Between Dates Calculator
Choose the right record before calculating
Choose calendar dates and decide whether the task counts elapsed boundaries or includes endpoint labels. A start date equal to the end has zero elapsed days but can represent one included date. This date-only calculation does not measure elapsed hours in a city time zone.
Content and calculation reviewed:
Understand the calculation
How to use it and the math behind it
Four steps to check your inputs and results
- Count calendar days between two dates without using local-clock elapsed hours. Weekends and holidays still count; the end date is excluded unless the inclusive option is checked.
- Enter Start date, End date, Include the end date in the stated format. Baseline values are for reproduction.
- Check the output unit and convention: Read calendar days with its stated unit and convention. The default example and the independent worked scenario use different inputs, so compare the assumptions before comparing the numbers.
- Change one input and compare the result. The end date must be on or after the start; equal dates give zero, or one when the end is included. All calendar dates count, including weekends and holidays; local-clock hours and holiday rules are outside this difference. Calendar-date inputs and calculated calendar dates must stay within years 0001–9999.
Days Between Dates Calculator: calendar conventions
Calendar-day subtraction excludes the end date by default. From February 28 to March 1 in leap year 2024 there are two day transitions: February 29 and March 1. Including the end adds one, producing three counted calendar dates. This is date arithmetic at UTC midnight, not a measure of local elapsed hours across daylight-saving changes.
days = (UTC(end) − UTC(start)) / 86400000 + inclusiveEnd
The detailed guide adds variable definitions, a reproducible example, a practice question and model limitations.
Questions before you calculate
Why does inclusive counting add an endpoint?
It counts date labels rather than only boundaries between them.
What is the elapsed count for the same date?
Zero.
Does the tool account for leap days?
Yes, using calendar-date validity and the selected year.
Does it determine a legal deadline?
No. Supply the applicable endpoint and rollover convention.
Is this an elapsed-hour calculation?
No. It operates on date labels, not named-zone instants.
From question to result