Count business days between dates
Sums weekdays between two inclusive dates, then subtracts a custom holiday list. Output breaks down the total, weekends, and excluded holidays.
How the count works
We iterate every day between start and end (inclusive). Each Sat/Sun goes to weekends; each ISO match in your holiday list goes to holidays; everything else is a workday.
- 01
Pick start + end
Inclusive — both endpoints count. End must be on or after start.
Parsing accepts ISO 8601, RFC 3339, RFC 2822, and Unix epoch seconds/milliseconds. The Date constructor handles the rest with browser-engine consistency.
inputISO 8601RFC 3339epochlivestart · timestampend · ISO2026-01-01 2026-01-31
loaded · ISO 8601zone · ready - 02
Paste holidays
One ISO date per line — copy-paste from your HR site or a public holiday source.
All math runs in UTC internally to avoid DST landmines; presentation converts back to the user’s zone via
Intl.DateTimeFormat.holidaysUTC mathIntlDST-safelivelist · optionsyyyy-mm-dd · live2026-01-01 2026-12-25
options applied · UTCDST-safe - 03
Iterate days
Sat/Sun = weekend; matched ISO = holiday; rest = workday.
Output respects the chosen timezone offset (
Zvs+05:30) and pads digits per ISO conventions so sorts stay chronological.countoffsetzone-awaresortablepaddedloop · computedday · readydow: 0/6 = w/e
computed · instantsortable - 04
Read the breakdown
Business days are the headline; totals, weekends, holidays sit underneath.
Copy writes via the Async Clipboard API; nothing pings a time server — the browser’s clock is the only oracle.
outclipboardno oracledeterministicclient-side✓ · copiedready · done✓ Copied
shipped · ready to shipsuccess
Time math without DST landmines
Always store UTC
Convert to local for display only. UTC storage avoids DST jumps and timezone drift in databases.
Watch leap seconds
POSIX time doesn’t count leap seconds; some systems do. Don’t use timestamps for sub-second precision across boundaries.
Prefer Temporal eventually
The Date API has many quirks. Temporal is shipping in modern engines and handles zones correctly.
Cron is timezone-tricky
Cron expressions run in the daemon’s local zone unless told otherwise. Pin a TZ explicitly for predictable runs.
ISO 8601 sorts naturally
YYYY-MM-DDTHH:mm:ss sorts correctly as a string. Don’t use US-style MM/DD/YYYY for anything machine-readable.
Beware Y2K38
Signed 32-bit Unix timestamps overflow in 2038. Use 64-bit storage end-to-end for long-lived systems.
When to count business days
Contracts, SLAs, payroll, leave.
Contract delivery
"5 business days" SLAs land on real dates with holidays excluded. Math runs in UTC under the hood to dodge DST jumps — local time is only for display. That means scheduling logic and date diffs survive March / November fall-back without the classic off-by-one-hour bug.
DST-safePayroll
Working-day counts feed accrual calculations. Browser clock is the only source — no external time server, no privacy leak, no rate limit. Pair with NTP-synced server time for high-accuracy use cases, but for human-scale work the browser clock is plenty.
UTC-correctLeave planning
How many working days does a 2-week holiday eat? ISO 8601 output sorts naturally as strings, perfect for filenames (report-2026-01-15.pdf) and log lines that need chronological ordering without parsing. Drop into S3 keys for free time-bucketing.
ISO-sortableCourt deadlines
Legal filings often measure in business days. Pairs cleanly with cron, scheduled tasks, and timestamped log analysis. The tool's output drops directly into APScheduler, Linux cron, or GitHub Actions schedule expressions without re-formatting.
spec-gradeProject sizing
Estimates over a span need workday counts, not raw days. Output respects the chosen timezone offset (Z vs +05:30) so REST APIs and database TIMESTAMP WITH TIME ZONE columns round-trip cleanly. No ambiguity between "noon UTC" and "noon local".
zone-awareInternational ops
Different countries have different holiday calendars — paste yours. Confirms the difference between epoch seconds (10 digits) and milliseconds (13 digits) before you commit code that mis-multiplies by 1000 — a classic bug in cross-language time handling.
i18nFrequently asked questions
Something missing?
Tell us what you need. We ship the top requests every two weeks.