Count date labels with a visible boundary rule

Measure the gap and choose endpoint inclusion

Enter two valid Gregorian dates in YYYY-MM-DD form. The calculator preserves direction, shows the base boundary difference, and applies explicit start/end inclusion without pretending that every calendar day contains exactly 24 elapsed hours.

Loading the days-between-dates calculator…

Enable JavaScript to enter two dates and select endpoint inclusion. The counting rules, DST distinction, examples, and scope remain readable below.

“Between” is incomplete without a boundary convention

Exclusive and inclusive counts answer different range questions

RuleAugust 4 to August 5Interpretation
Exclude both1 date boundaryThe start of August 5 is one calendar step after the start of August 4.
Include start2 represented datesAugust 4 and the boundary leading to August 5 are counted under the range convention.
Include end2 represented datesThe terminal date belongs to the requested range.
Include both2 represented datesThere are only two unique labeled dates; an identical endpoint is never double-counted.

Requirements often use “inclusive” casually. A hotel night count, medication schedule, filing window, project span, and array slice may each assign endpoints differently. Choose the convention from the real domain, then record it with the result.

Civil dates are not fixed-duration timestamps

A date boundary remains one even across DST

These inputs contain a year, month, and day but no clock time or named time zone. The calculator therefore uses proleptic Gregorian date arithmetic. It does not create local midnight timestamps and divide milliseconds by 86,400,000, a technique that can yield surprising fractions or off-by-one results around daylight-saving changes.

From Saturday to Sunday is one date boundary whether the local clocks later skip an hour, repeat an hour, or never observe daylight saving. If the actual question asks how many seconds passed between two instants, the inputs must include times, zones, and an offset-history rule. That is outside this page's date-only contract.

Leap days are real dates. A range that crosses February 29 includes the extra date boundary automatically. The tool validates the Gregorian year rule: years divisible by four are generally leap years, century years are not unless divisible by 400.

Date distance
Count of civil date boundaries.
Elapsed duration
Seconds or hours between instants.
Leap day
A valid February 29 in a Gregorian leap year.
Direction
Which entered endpoint occurs first.

Apply exclusions in the right layer

Weekends, holidays, and age use different contracts

All calendar days

This page counts every date. Whole weeks and remainder days are a presentation of that count, not an ISO week-number calculation.

Working dates

The Business Days Calculator applies a weekend pattern and explicit holiday list rather than silently assuming a locale.

Move an endpoint

The Date Calculator adds or subtracts years, months, weeks, and days with a stated month-end clamp.

Range-count answers

Days between dates FAQ

How many days are between the same date?

The exclusive boundary difference is zero. If both endpoint inclusion options are selected, that single calendar date counts as one represented day rather than two duplicate endpoints.

What is the difference between exclusive and inclusive counting?

Exclusive counting measures date boundaries without counting an endpoint as a represented day. Including the start, the end, or both changes which labeled calendar dates belong to the requested range.

Does a daylight-saving change create a fraction of a day?

No. This calculator counts Gregorian date boundaries, not elapsed 24-hour blocks. Consecutive local dates remain one date apart even if a zoned timestamp interval spans 23 or 25 hours.

Are weekends and holidays removed?

No. Every Gregorian date is counted under the chosen endpoint rule. Use the business days calculator when weekends or user-supplied holidays must be excluded.

Which date format does the calculator accept?

Enter both civil dates as YYYY-MM-DD. The interface validates real Gregorian dates, including leap-year rules, rather than accepting an impossible date such as 2025-02-29.