DayKitHow it works
Choose the beginning and end of your date range, then decide whether each endpoint counts. Mark every weekday that is normally non-working for you. Add custom excluded dates in YYYY-MM-DD format, separated by commas or new lines. Public holidays are not added automatically. Each included calendar date is classified once: a non-working weekday first, then a custom exclusion, otherwise a working day. An excluded date on a non-working weekday is not deducted twice.
Formula
Working days = included calendar dates − skipped non-working weekdays − custom exclusions on working weekdays. An identical start and end counts only when both endpoint switches are enabled.
Example
October 21 to November 4, 2026 includes 15 calendar dates when both endpoints are included. With Saturday and Sunday marked non-working, the result is 11 working days and four skipped weekend days. Excluding October 26 reduces the count to ten. The month view explains each classification; use CSV for the full trace of a long range. Dates are civil calendar dates, so daylight-saving changes do not add or remove a day.
Assumptions and limitations
Dates are calendar dates, not timestamps. Custom dates on non-working weekdays are skipped only once.
Frequently asked questions
Are public holidays included automatically?
No. Add the dates you want to exclude. Custom weekends and exclusions are your own planning rules, not an official holiday calendar.
Are my settings uploaded?
No. Calendar rules and weekly shifts remain in this browser. Clear this site’s data to remove them. CSV exports are created on your device.
Does this apply payroll or legal deadline rules?
No. The tools calculate according to your explicit inputs. They do not infer jurisdiction, overtime, public holidays or contract-specific counting rules.