Time Tool

Plan dates and schedules with elapsed-time differences, selected working days and hours, optional rounding, date and time arithmetic, duration breakdowns, and time-zone comparisons. Explore detailed results and visual breakdowns, then export summaries in several formats.

Calendar dates use your device's local time zone; daylight-saving changes are handled by the browser.

Uses international IANA time zones and the browser's daylight-saving rules. Ambiguous or non-existent times during clock changes are rejected.

Elapsed time
—
Time breakdown
Detailed results

Table of Contents

  1. How Time Tool Works?
  2. Practical Use Cases
  3. Accuracy and Limitations
  4. Frequently Asked Questions (FAQs)
  5. Cite This tool

Highlights

  • Compare actual elapsed time or hours within selected workdays.
  • Add or subtract days, hours, minutes and seconds.
  • View detailed totals and a colourful interactive time breakdown.
  • Compare supported global time zones with daylight-saving awareness.
  • Export results as CSV, JSON, text or SVG charts.

How Time Tool Works?

The tool has four calculation modes: elapsed or working-time difference, date arithmetic, duration totals, and time-zone comparison. Date inputs are interpreted in the browser’s local time zone for difference and date arithmetic. The time-zone mode instead uses the selected named regions.

Elapsed difference. The two date-times are represented as timestamps. The end timestamp must be at or after the start timestamp.

elapsed seconds=end timestamp−start timestamp1000

Working time. For each selected weekday, only the overlap of the chosen working-hour window with the overall start–end interval is counted. The overlaps are added together. Working hours must start before they finish, and at least one weekday must be selected.

working seconds=∑d∈selected daysmax(0,min(end,day close)−max(start,day open))

Optional rounding applies to the final difference, to the nearest 5, 15, 30 or 60 minutes; the unrounded setting retains the entered precision.

Date arithmetic. Whole-number days, hours, minutes and seconds are combined into a duration and added to or subtracted from the base timestamp.

S=86400d+3600h+60m+s

Duration mode uses the same total and reports its equivalent totals and a days–hours–minutes–seconds breakdown. Date arithmetic treats a day as 86,400 elapsed seconds rather than a calendar-day increment.

Time zones. The source wall-clock time is resolved to a unique UTC instant using the chosen IANA region; that instant is displayed in the destination region. Regional UTC offsets, their difference and the UTC timestamp are shown. A non-existent or repeated source local time during a daylight-saving change is rejected.


ModeKey inputsKey outputs
DifferenceStart, end, elapsed or working hours, weekdays, roundingElapsed or working duration and totals
Add / SubtractBase date, direction, days, hours, minutes, secondsResulting date-time
DurationDays, hours, minutes, seconds, selected primary totalTotals and component breakdown
Time zonesSource local date-time, source region, destination regionDestination time, UTC offsets and UTC instant

The visual bar shows the relative counts of the displayed duration components. Its segments do not represent proportional elapsed seconds.

Practical Use Cases

Office managers: Select Monday to Friday and a 09:00–17:00 window to estimate how much scheduled working time lies between two deadlines, with optional rounding.

Project coordinators: Enter a project start and end to see actual elapsed time, or add a fixed number of days and hours to establish a follow-up timestamp.

Freelancers: Add together a task’s days, hours, minutes and seconds to review its total duration and detailed breakdown.

Remote teams: Compare the same instant between Auckland, London or other supported regions while accounting for date-specific regional clock rules.

Event organisers: Subtract a preparation interval from an event start time to determine when setup should begin, then export the resulting details.

Accuracy and Limitations

Elapsed differences use browser timestamps with second-level input and display precision; optional rounding can change the reported difference. Working schedules support a maximum span of 100 years, a single same-day daily work window and selected weekdays, but do not exclude public holidays, breaks or exceptions. Date arithmetic uses fixed 24-hour days, so daylight-saving transitions can change the resulting wall-clock time. Duration inputs must be whole numbers from 0 to 100,000 per field. Time-zone results depend on the browser’s IANA time-zone data and only the listed regions are selectable; ambiguous and non-existent source times are rejected. The graphic compares displayed component counts, not actual duration shares.

Frequently Asked Questions

Elapsed time includes every moment between two dates. Working time counts only the portions that fall within selected weekdays and scheduled hours.

Yes. Moving clocks forward or backwards can make the actual elapsed hours differ from the apparent difference between local clock readings.

During an autumn clock change, the same local time can correspond to two different instants. A time-zone-aware schedule needs an offset or another way to distinguish them.

Not necessarily. A weekday schedule still includes public holidays unless those dates are excluded separately.

No. A fixed 24-hour interval may land at a different local clock time when a daylight-saving transition occurs.

Cite This tool