Are these calendar days or working days?
Choose inclusive or exclusive endpoints, then exclude weekends and only the holidays supplied before calculating a target date.
Dates & time
Calculate calendar days, work shifts, age and date-aware city zones. Check DST changes, fixed UTC offsets, leap days and time units with stated conventions.
From question to result
Calculate first, understand the formula and example, then compare your options. Each link answers a different question.
Choose inclusive or exclusive endpoints, then exclude weekends and only the holidays supplied before calculating a target date.
Use a stated anniversary convention for February 29 and distinguish completed years from the number of calendar days remaining.
A weekday and an ISO week-year describe different calendar properties; dates near New Year can belong to a different week-year.
Separate elapsed duration from paid hours, explicitly allow overnight shifts, then total multiple shifts before applying a wage.
Choose an IANA time zone for date-specific daylight-saving rules or a fixed UTC offset. Distinguish ambiguous or missing local times, Unix seconds versus milliseconds, and an absolute countdown deadline.
Calculator set
Open a calculator for an immediate estimate, then use its method notes, examples, limits, and sources to understand the result.
Understand, then calculate
A calendar date and an instant are different concepts. Counting calendar days should not divide browser-local elapsed milliseconds blindly by 24 hours, because a daylight-saving transition can create a 23- or 25-hour local day. Date-only tools construct labels at UTC midnight to retain whole-day arithmetic. The time-zone converter separately offers constant UTC offsets or dated city conversion with IANA rules, rejecting missing spring times and explicitly resolving repeated autumn times. A Unix timestamp instead identifies elapsed time from an epoch; seconds and milliseconds differ by a factor of one thousand.
Boundary conventions must be chosen before interpreting a count. Excluding the end date gives zero days for equal endpoints; including it counts one calendar date. Work-day calculations remove weekends and only the holidays actually supplied. An ISO week-year can differ from the calendar year near New Year, and a February 29 birthday requires a stated non-leap-year anniversary rule. A shift crossing midnight needs an explicit overnight interpretation; it should not silently become a negative paid duration. These conventions make examples reproducible without claiming legal or payroll rules.
Identify the decision first, then open the calculator that answers it.
Understand the recurring inputs and results instead of reading only the final number.
Choose with context
Use these distinctions to move through the Dates & time tools without comparing unrelated results.
Use calendar days or working days according to the question, explicitly choosing the endpoint convention.
Use duration for elapsed time, hours for one shift after breaks, and a time card for multiple shifts.
Use city zones with a source date for automatic DST, fixed offsets for a stated offset, or Unix timestamps for instants; check leap days and ISO week-years separately.
Check the stated input format, calculation convention and limits before using the result.
Common questions
These answers explain how to use the estimates and where their limits begin.
Use calendar days or working days according to the question, explicitly choosing the endpoint convention. Use duration for elapsed time, hours for one shift after breaks, and a time card for multiple shifts. Use city zones with a source date for automatic DST, fixed offsets for a stated offset, or Unix timestamps for instants; check leap days and ISO week-years separately.
Work days use only the holidays you enter. Date arithmetic uses UTC calendar labels. City time-zone mode uses dated IANA rules and explicit overlap choices, while fixed mode preserves a constant offset. Clock-only hours and time cards do not infer a dated city zone.