Days between two dates

Classic checks include 2024-01-01 to 2024-01-11 yielding ten days, 2024-02-28 to 2024-03-01 yielding two days in a leap year, and identical endpoints yielding zero.

What a whole-day span means and what the response contains

Counting whole calendar days between two dates answers a different question from business-day counts, age in years and months, or timezone-aware timestamp subtraction: it measures pure civil distance on the Gregorian calendar, midnight to midnight, without skipping weekends, holidays, or daylight-saving transitions. If you need business days, subtract-days navigation, epoch conversion, or multi-format parsing, use those dedicated tools; this page answers only the whole-day Gregorian distance between two validated ISO dates. You supply a start date and an end date as strict YYYY-MM-DD strings; order does not have to be chronological because the absolute days field is always non-negative while signed_days preserves direction when the end is earlier than the start. The calculator validates that both days are real calendar days — February 29 only in leap years, thirty days in April, never day thirty-two — then returns the normalized start and end strings, days as the absolute whole-day distance, signed_days as serial end minus serial start, the component fields start_year, start_month, start_day, end_year, end_month, and end_day for easy piping into other tools, and a short formula reminder. Rejected cases include a missing start or end field, wrong shapes such as 2024/01/01, impossible months, days that do not exist such as 2023-02-29, and years outside one through 9999.

How start and end are read and how the count stays reproducible

Each string must match four digits, a hyphen, two digits, another hyphen, and two digits; leading or trailing spaces are trimmed, but partial dates, ordinal day-of-year alone, month names, and embedded times are not expanded here. After parsing, each year must fall between 1 and 9999, each month between 1 and 12, and each day between 1 and the true length of that month in that year, with leap years following the Gregorian rule of divisible by four except century years not divisible by four hundred. The preferred first field is start, but aliases from, date1, a, and begin are accepted so spreadsheets, query strings, and typed forms can reuse the same contract without renaming columns. The preferred second field is end, with aliases to, date2, b, and finish for the same reason. Internally the engine converts each civil triple to a proleptic Gregorian serial day count using the well-known days_from_civil mapping, subtracts serial start from serial end to obtain signed_days, then takes the absolute value for days — pure integer arithmetic that is bitwise stable across runtimes. Identical dates yield zero; reversing the pair flips only the sign of signed_days and leaves days unchanged. Pair the free browser run on this page with the priced API when you need the identical day span inside an automated pipeline.

Where day-span arithmetic fits in planning, billing, and software

On this page the work runs entirely in your browser; through the API each successful lookup costs $0.002, failed validation is not charged, and nothing is stored after the response returns. That split — free interactive exploration and a priced, identical API — matches the rest of the KIT tier-A catalog and lets you move from a one-off check to a pipeline without changing the mathematical result.