Working days in a year

Add an optional list of holiday dates to remove weekday holidays from the result without subtracting the same date twice or counting a holiday that already falls on a weekend. The calculation uses fixed Gregorian calendar rules and deterministic arithmetic, so the same input always produces the same result in every time zone.

Choose the year with an explicit date

Enter a date in the exact YYYY-MM-DD ISO format. The complete date is required even though the calculation uses its year, because an explicit date keeps API requests unambiguous and avoids assumptions about the current year, account locale, or server clock. For example, 2024-07-25 selects the whole 2024 calendar year, from January 1 through December 31; it does not start counting on July 25. The result reports the submitted date, selected year, number of calendar days, weekend days, weekday holidays, and final workday count. Years from 0001 through 9999 follow the proleptic Gregorian calendar, including the familiar leap-year rule: a year divisible by four is a leap year unless it is divisible by one hundred, except that years divisible by four hundred remain leap years. Invalid calendar dates such as 2025-02-29 are rejected instead of being silently normalized. This makes the calculator suitable for reproducible schedules, audits, tests, and stored business rules where an implicit current date would make an old request change meaning later.

Exclude weekends and optional holidays correctly

Every Saturday and Sunday in the selected year is excluded first. You may then provide holiday dates as an array of ISO strings. A holiday reduces the workday total only when it belongs to the selected year and falls from Monday through Friday. A Saturday or Sunday holiday is already excluded as a weekend, so it does not reduce the total again. Repeated holiday dates are deduplicated for the same reason. Valid holidays from another year are accepted but ignored, which makes it safe to send a shared multi-year holiday list without filtering it before each request. The tool does not invent public holidays, substitute observance dates, or infer a country from your location. Those rules differ among jurisdictions, employers, collective agreements, and years. Supply the exact closure dates that apply to your organization. If a holiday observed on Monday replaces one that occurred on Sunday, include the observed Monday date. This explicit approach makes the count transparent: weekend days and effective weekday holidays are reported separately, so you can explain precisely how the final number was obtained.

Use a deterministic count in planning and automation

The calculation performs pure integer calendar arithmetic. It does not call a network service, read the current clock, use the JavaScript Date object, apply daylight-saving transitions, or inspect the machine's locale. In practical terms, UTC is the stable interpretation: an input such as 2026-01-01 remains that calendar date regardless of whether a request runs in Tokyo, London, or California. This is valuable when a workday total feeds annual capacity plans, staffing models, utilization targets, service-level forecasts, or payroll estimates. Store the input date and holiday list alongside the returned breakdown, and you have an auditable snapshot that can be recomputed later. Remember that the result is a count of potential Monday-to-Friday working dates, not the hours worked by a particular employee. It does not account for vacation, part-time schedules, shutdowns omitted from the holiday list, regional weekends other than Saturday and Sunday, or half-day closures. Run it in the browser for an interactive check, or call the API for $0.002 when the same rule belongs in a repeatable workflow.