Find out exactly how much time sits between two dates, expressed both ways: as a calendar difference in years, months and days, and as straight totals in days, weeks and hours. Both matter — a contract that runs for three months is not the same as one that runs for 90 days, and which one you need depends on what you are counting. There is a business-day count too, skipping weekends, for deadlines and delivery estimates. Leap years and month lengths are handled properly, and every calculation runs in UTC so a clock change between the two dates cannot quietly shift the answer by a day. It all happens in your browser, so nothing is uploaded.
| Range | Calendar | Total days | Business days |
|---|---|---|---|
| 2026-01-01 → 2026-03-01 | 2 months | 59 | 42 |
| 2024-01-01 → 2024-03-01 (leap) | 2 months | 60 | 43 |
| 2026-01-05 → 2026-01-12 | 1 week | 7 | 5 |
| 2026-01-31 → 2026-03-01 | 1 month, 1 day | 29 | 21 |
Because they answer different questions. From 1 January to 1 March is 2 months, but it is 59 days in a common year and 60 in a leap year. Contracts and notice periods are usually counted in months; deadlines and interest are usually counted in days. Showing only one would be misleading for the other use.
The totals count the span between the two dates, so the end date is not included by default. Use the toggle to count it as well — that is the convention when you are counting days of attendance, hotel nights billed by day, or an inclusive date range on a form.
By walking the range and counting every day that is not a Saturday or Sunday, including the start date and excluding the end. Public holidays are not deducted, because they differ by country and often by region — subtract the ones that apply to you.
Yes. February's length is taken from the actual calendar rather than assumed, so a range spanning 29 February counts the extra day and a month-length borrow uses 29 rather than 28.
No. Every calculation is local date arithmetic. The dates you enter are not sent to a server, logged, or stored.
The difference is computed two ways because people ask two different questions. The calendar breakdown counts whole years, then whole months, then leftover days: the start date is stepped forward by the whole years and months, clamping the day to the target month's length, and the remaining days are counted from there — the clamping is what makes 31 January to 1 March come out as one month and one day rather than underflowing. The totals are computed independently from the elapsed milliseconds, so they are exact regardless of month lengths. Business days are counted by walking the range and skipping Saturdays and Sundays, including the start date and excluding the end, which is the convention payroll and project tools use; public holidays are not deducted because they vary by country. All arithmetic runs in UTC, so a daylight-saving change between the two dates cannot shift a result by a day — the most common source of off-by-one errors in date tools.