Date & Time Difference Calculator

Time between {{ startSummaryShort }} and {{ endSummaryShort }}

Total days: {{ summaryTotals.days.toLocaleString() }} Total hours: {{ summaryTotals.hours.toLocaleString() }} Working days ({{ workingWeekSummaryLabel }}): {{ workingDaysDisplay }} Business overlap: {{ businessOverlapDisplay }} {{ timezoneAdjustmentLabel }} {{ offsetShiftLabel }}

Start date & time:

Use YYYY-MM-DD plus optional HH:MM; blank time uses 00:00 and Now fills the current local minute.

End date & time:

Use YYYY-MM-DD plus optional HH:MM; blank time uses 00:00 and Now fills the current local minute.

Endpoint actions:

Swap keeps each timestamp with its timezone mode and fixed offset.

Start and end timestamps

Keeps each timestamp paired with its timezone interpretation.

Start timezone:

Choose Local, UTC, or Custom UTC offset; {{ startTimezoneLabel }}.

End timezone:

Choose Local, UTC, or Custom UTC offset; {{ endTimezoneLabel }}.

Working week:

Choose Mon-Fri, Mon-Sat, Sun-Thu, all days, or Custom for the workday count.

Custom weekdays:

Select one or more weekdays; current calendar is {{ workingWeekLabel }}.

Count end date:

Toggle only changes working-day totals; elapsed duration and business overlap stay timeline-based.

Capacity hours/day:

Enter 1-24 hours, e.g. 7.5 or 8; business-window overlap is calculated separately.

Business window:

Use 24-hour HH:MM times; the end must be later than the start.

Holiday exclusions:

Enter YYYY-MM-DD dates separated by spaces, commas, semicolons, or new lines.

Parsed holidays: {{ parsedHolidayCount }} · Ignored: {{ ignoredHolidayCount }}

Checkpoint plan:

Choose quarters, thirds, or handoff reviews for exported checkpoints.

Decimal places: {{ decimalPlaces }} dp

Drag from 0 to 9 decimal places; current output uses {{ decimalPlaces }} dp.

The end input occurs before the start input. Calculations use the absolute difference, but use Swap to align the chronology if needed.

Wall-clock span is {{ wallClockHoursDisplay }}, while elapsed span is {{ formatNumber(totalHoursDecimal, 2) }} h. {{ timezoneAdjustmentLabel }} because the endpoints do not share the same timezone interpretation.

Metric	Value	Copy
{{ row.label }}	{{ row.value }}

Checkpoint	Timestamp	Offset	Business hours	Complete	Copy
{{ milestone.label }}	{{ milestone.timestamp }}	{{ milestone.offset }}	{{ milestone.businessHours }}	{{ milestone.completion }}

Enter distinct start and end moments to generate a milestone schedule.

Embed:

Customize

Include current inputs

Size

Advanced

Width

Height

Aspect ratio

Max height

Collapsible embed

Allow fullscreen

Referrer policy

Sandbox tokens

A date range can be simple on paper and still be easy to misread. Two timestamps may describe the same local clock time in different places, cross a daylight-saving change, include a weekend, or cover only part of a working day. The answer people need is often not just "how many days" but which kind of time is being counted.

Elapsed time measures the distance between two instants on one timeline. Civil time is the date and clock reading people type, write in tickets, or see on a meeting invite. Schedule time filters that span through a work calendar, holidays, and a daily business window. Keeping those ideas separate prevents common mistakes such as treating a five-calendar-day range as forty usable work hours, or assuming that matching clock readings mean no time passed.

Common date and time difference questions and the measurement that answers each one
Question	Measure to trust	Common mistake
How much real time passed?	Elapsed duration from interpreted instants	Ignoring the timezone or UTC offset attached to one endpoint
How far apart do the typed clock readings look?	Wall-clock span	Using it as elapsed time when offsets differ
How many dates count for planning?	Working-day count	Forgetting region-specific weekends or manual holidays
How much of the span lands inside office hours?	Business-window overlap	Multiplying full working days when the interval starts or ends mid-day

Timeline comparing elapsed time, wall-clock time, workday count, and business-window overlap.

Time zones matter because a local clock reading is not an instant by itself. A timestamp with UTC+08:00, UTC, or another numeric offset can be placed on a shared timeline. A bare local time depends on the device's timezone rules, including daylight-saving transitions where one clock hour may be skipped or repeated.

Work schedules add another layer. A date may be part of the elapsed span but excluded from capacity because it is a weekend, a regional off day, or a manually listed holiday. The safest reading is to treat elapsed duration, wall-clock span, workday count, and business-window overlap as related answers rather than interchangeable ones.

How to Use This Tool:

Start with the two timestamps, then adjust timezone and schedule settings only when the defaults do not match the source of the dates.

Enter Start date & time and End date & time. A blank time is treated as 00:00, and each Now button fills the current local minute.
Use Start timezone and End timezone to interpret each timestamp as device local time, UTC, or a custom UTC offset. Choose a custom offset when a log, receipt, ticket, or message already includes one.
Use Swap if the endpoints were entered backward and you want the chronology to read from earliest to latest. The elapsed totals are based on the absolute span either way.
Open Advanced when work schedules matter. Select the working week, custom weekdays if needed, and whether the ending calendar date should count in the working-day total.
Set Capacity hours/day for a rough work-capacity estimate, then set the Business window for actual overlap inside each counted working date. The business-window end time must be later than the start time.
Add Holiday exclusions as YYYY-MM-DD dates separated by spaces, commas, semicolons, or line breaks. Check the parsed and ignored counts before relying on a holiday-adjusted result.
Choose a Checkpoint plan and Decimal places if you need milestone rows, chart precision, CSV, DOCX, or JSON output for review.

If an error appears, correct the date fields or fix the business-window order before using the summary, tables, charts, or exports.

Interpreting Results:

The summary gives a readable duration and a short planning note. Use it for orientation, then verify the detailed fields when the result will affect a deadline, service window, handoff, payroll estimate, or staffing plan.

Delta Ledger is the audit table. It shows chronology, interpreted endpoints, readable duration, ISO 8601 duration text, decimal unit totals, workday counts, holiday parsing, business-window overlap, midpoint, and the planning recommendation.
Wall-clock span compares the typed civil date-times before timezone conversion. A difference between this span and elapsed hours points to different offsets, timezone modes, or a daylight-saving change.
Working days counts calendar dates allowed by the selected working week, the end-date option, and the holiday list. It does not change the actual elapsed hours.
Business-window overlap measures the portion of the interval that falls inside the daily business window on counted working days. It is stricter than multiplying working days by capacity hours.
Checkpoint Ladder places start, end, and selected percentage milestones on the elapsed timeline, with business hours accumulated at each point.

The charts answer different review questions. Schedule Mix shows how counted days split across working days, weekends, excluded weekdays, and holidays. Unit Scale Bars compares the same duration in years, months, weeks, days, hours, minutes, and seconds. Progress Curve compares elapsed hours with business hours across the checkpoint plan.

Treat warnings as interpretation checks, not cosmetic messages. An end-before-start warning means the totals use the absolute span while the typed order is reversed. A zone or DST warning means the clock-reading difference is not the same as the elapsed timeline difference.

Technical Details:

An elapsed duration calculation works only after each civil date-time has been converted into an instant. UTC and fixed-offset inputs can be mapped directly. Device-local inputs rely on the browser environment's local timezone rules for that date, including daylight-saving changes when they apply.

Calendar wording and fixed-unit arithmetic answer different technical questions. A breakdown such as one month and two days walks through the calendar from the earlier instant to the later one, so month length and leap years affect the wording. Decimal totals divide elapsed milliseconds by fixed unit sizes, which is better for comparisons and capacity math.

Formula Core

The base duration is the absolute difference between the interpreted endpoint instants.

D_{ms} = | t_{end} - t_{start} |

Total hours = \frac{D_{ms}}{3600000}

Wall-clock comparison removes timezone interpretation from the question. It compares the typed year, month, day, hour, and minute as civil values. Subtracting wall-clock span from elapsed span exposes offset differences, including daylight-saving effects when local time is involved.

Date and time difference mechanisms and interpretation limits
Mechanism	What changes it	What does not change it
Elapsed milliseconds	Endpoint dates, times, timezone modes, and fixed offsets	Working-week selection, holidays, capacity hours, and checkpoint plan
Calendar breakdown	Month length, leap years, and the exact endpoint instants	Decimal precision setting
Working-day count	Working-week rule, holiday exclusions, and end-date inclusion	Daily business-window start and end times
Capacity hours from working days	Working-day count and capacity hours/day	Actual start and end times inside each day
Business-window overlap	Actual interval endpoints, working calendar, holidays, and the daily window	Capacity hours/day estimate

Business-window overlap is an interval-intersection calculation. For each counted working date, the daily window is placed on the same timeline as the overall interval. Only the overlapping part contributes business hours.

Business overlap = \sum max(0, min(interval end, window end) - max(interval start, window start))

Numeric UTC offsets are useful for recorded timestamps because they identify the relationship between a local clock reading and UTC for that instant. They are not the same as named time zones with historical and future rule changes. When a timestamp comes from a location rather than a fixed offset, the location's timezone rule for that date is part of the interpretation.

Accuracy and Privacy Notes:

The calculation is deterministic for the values entered, but policy choices still matter. A support team, contractor, school, or regional office may define working days and holidays differently from the defaults.

Device-local mode follows the browser environment's local timezone rules. Use UTC or a custom offset when the source timestamp already states an offset.
Custom offset mode uses a fixed numeric UTC offset. It does not infer historical or future rules for named locations.
Holiday exclusions are manual. Invalid, duplicate, or differently formatted tokens are ignored and shown in the parsed status.
As with standard browser date arithmetic, leap seconds are not modeled as separate seconds.
The calculation runs in the browser from the entered values. There is no public data lookup or account-based schedule source.

Worked Examples:

Same-zone project window

Start with 2026-05-18 09:00 and end with 2026-05-22 17:00 in device local time. With Monday-Friday selected, Count end date on, and a 09:00 to 17:00 business window, the elapsed span is 4 days and 8 hours while the business-window overlap is 40 hours. The nights are part of elapsed time, but they are not part of the working window.

Matching clock readings with different offsets

A start of 2026-03-01 09:00 at UTC+08:00 and an end of 2026-03-01 09:00 at UTC+00:00 have a wall-clock span of 0 hours. They are still 8 elapsed hours apart because the offset places the first timestamp earlier on the UTC timeline.

Holiday exclusion changing capacity

For 2026-12-21 09:00 through 2026-12-28 17:00, adding 2026-12-25 to Holiday exclusions removes that date from the working-day count when Monday-Friday is selected. If a token such as 12/25/2026 is entered instead, the ignored count rises and the holiday-adjusted result should be corrected before it is shared.

FAQ:

Why can elapsed hours and wall-clock span disagree?

Elapsed hours compare interpreted instants on one timeline. Wall-clock span compares the typed civil date-times. Different UTC offsets, local timezone rules, or daylight-saving changes can make those answers diverge.

Should I use capacity hours or business-window overlap?

Use capacity hours when each counted workday represents a fixed planning allowance. Use business-window overlap when the actual start and end times decide how much of the interval was inside working hours.

What happens if the end is before the start?

The result uses the absolute difference and shows a warning. Use Swap when you want tables and exports to read in chronological order.

Why did a holiday not affect the working-day total?

A holiday affects the count only if it is a valid YYYY-MM-DD date, falls inside the counted date range, and would otherwise be a working day under the selected calendar.

Why do date-only entries start at midnight?

When the time field is blank, the calculator treats that endpoint as 00:00. Enter a time when a deadline, shift, ticket, or handoff depends on the hour and minute.

Glossary:

Instant: A specific moment on the timeline after a civil date-time is interpreted with a timezone or UTC offset.
Civil time: The human-readable calendar date and clock time, such as 2026-05-18 09:00.
UTC offset: The numeric difference between local time and Coordinated Universal Time, such as UTC+08:00.
Wall-clock span: The difference between typed clock readings before timezone interpretation changes the instants.
Working day: A calendar date included by the selected working-week rule and not removed by a holiday exclusion.
Business-window overlap: The part of the elapsed interval that falls inside the configured daily work window on counted working days.

References:

RFC 3339: Date and Time on the Internet: Timestamps, RFC Editor, July 2002.
Theory and pragmatics of the tz code and data, Internet Assigned Numbers Authority.
Date - JavaScript, MDN Web Docs.