Count working days between two dates
This business days calculator compares two calendar dates and returns two different counts: elapsed calendar days and the number of Monday–Friday dates in the interval. It is useful for checking a study schedule, planning a weekday activity window or understanding how a date span changes when weekends are excluded.
The tool uses date-only inputs. It does not read a time of day, infer an organization’s opening hours or choose a country-specific holiday calendar. Its working-day definition is always Monday through Friday. A weekday that is a public holiday or a closure day remains counted unless you account for it separately.
Choose the start and end dates and the results update immediately. If the dates are entered in reverse order, the calculation uses the earlier-to-later interval and notes that ordering. Results stay nonnegative; this page is not a signed date subtraction or a deadline-addition tool.
Understand the endpoint conventions
Elapsed calendar days are the difference between the dates. The earlier date is not counted as an entire elapsed day merely because it is selected. Selecting the same date twice therefore gives zero elapsed days. This is an interval length, not an inclusive list of calendar dates.
The weekday result uses an inclusive convention: both selected dates count when they fall on Monday through Friday. Selecting the same weekday twice therefore gives one weekday, even though the elapsed interval is zero. Selecting the same weekend date twice gives zero weekdays.
These conventions answer different questions and are stated beside the calculator. Do not assume that the two results use the same denominator or that weekdays can never exceed elapsed days in very short intervals. If a process excludes its starting date, adjust the selected range to match that process before using the weekday result.
The calendar and weekday formulas
After strict validation, each input is represented as a UTC calendar-day number. Elapsed days equal the absolute difference between those day numbers. The inclusive interval contains the elapsed-day count plus one calendar date. This avoids measuring local-clock hours as if they were always complete calendar days.
For the weekday total, each complete week contributes five weekdays. The calculation adds those complete weeks, then checks the remaining dates individually. It needs only a short remainder check rather than walking through every date in a long range. Saturdays and Sundays contribute nothing to the weekday count.
Date-only arithmetic also avoids a device-timezone trap. Parsing a date at UTC midnight and then reading its weekday in local time can move it to the previous local date for a visitor west of UTC. This implementation keeps the date and weekday interpretation in UTC throughout, including intervals across daylight-saving changes.
Worked examples checked with the date library
The examples below use the same validated date-interval function as the tool. The first row matches its default inputs. Each weekday total includes both endpoints if eligible, while the elapsed count is the difference between the calendar dates.
| First date | Second date | Elapsed calendar days | Weekdays, inclusive |
|---|---|---|---|
| 2026-07-01 | 2026-07-21 | 20 | 15 |
| 2026-10-30 | 2026-11-03 | 4 | 3 |
| 2026-11-02 | 2026-11-02 | 0 | 1 |
| 2026-11-01 | 2026-11-01 | 0 | 0 |
| 2025-03-07 | 2025-03-10 | 3 | 2 |
In the short cross-month example, the eligible weekdays are the Friday and the following Monday and Tuesday. The weekend between them contributes to elapsed calendar time but not to the weekday count. Reversing the two inputs preserves those totals because the tool normalizes the direction.
The final example was also checked with US and overseas device time zones. It produces the same date counts across the daylight-saving interval. Your location does not change which calendar dates are included in this date-only model.
Holidays, regional weekends and organization rules
The calculator does not remove holidays automatically. If your selected range includes a relevant closure on a Monday through Friday, adjust the weekday total once for that date. Do not subtract a holiday that is already excluded as a Saturday or Sunday, and do not subtract the same closure twice when multiple calendars name it.
A different workweek needs a different model. This interface does not let you select alternative weekend days, rotating shifts or part-day schedules. The title “business days” should therefore be read with its explicit Monday–Friday definition rather than as a guarantee about a particular employer or institution.
There is also no built-in interpretation of phrases such as “three to five business days.” Such a phrase needs a starting-date convention, an applicable calendar and possibly a time-of-day rule before it identifies an endpoint. This page counts a range you select; it does not infer those missing assumptions.
Input checks and useful follow-up tools
Enter complete dates using the date controls. Invalid calendar dates, a missing endpoint and years outside the supported range are rejected rather than silently rolled into a different month. When an input is cleared, the old result disappears so it cannot be mistaken for a calculation using the new range.
For time values expressed as Unix seconds or milliseconds, use the Unix timestamp converter; timestamps and date-only intervals are different inputs. For an upcoming exam event, use the exam countdown. The semester planner helps organize course planning, and the study timer handles timed work sessions. None of those tools supplies a holiday calendar to this one.