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.

Export to PDF Fullscreen

Embed:

Customize

Include current inputs

Size

Advanced

Width

Height

Aspect ratio

Max height

Collapsible embed

Allow fullscreen

Referrer policy

Sandbox tokens

A date-and-time difference can mean more than one thing. Sometimes you need the exact elapsed span between two instants. Sometimes you need to know how long the interval looks on the clock in local terms. In project work, staffing, and handoffs, you may also need to remove weekends, exclude listed holidays, or see how much of the span actually lands inside working hours.

This calculator compares two complete date-and-time entries and keeps those questions separate. It returns a calendar-style breakdown in years, months, days, hours, minutes, seconds, and milliseconds, plus decimal totals in common units, an ISO 8601 duration string, a wall-clock span, midpoint timing, and a chronology note when the entered end is earlier than the entered start.

The advanced settings let you decide how each endpoint should be read. You can treat the start and end as device-local time, UTC, or a fixed UTC offset. You can choose a working-week pattern, define custom weekdays, include or exclude the ending calendar day from workday counts, set a daily business window, add holiday dates, switch between quarter, third, or handoff checkpoints, and change the displayed decimal precision for the unit totals.

The result area then turns the same interval into several practical outputs. Delta Ledger is the main table, Checkpoint Ladder lays out milestone timestamps and business-hour progress, Schedule Mix shows how the counted dates split across working and non-working categories, Unit Scale Bars compares the same elapsed span across units, Progress Curve plots elapsed hours against business hours, and JSON packages the inputs and results for export.

All calculations, tables, charts, and exports stay in the browser. That makes the tool convenient for private scheduling work, but it also means the result follows the browser's date-and-time model rather than a specialist calendaring system.

Technical Details

Each endpoint is built from a date, a time, and a time-zone interpretation. In Local mode, the browser reads the value using the device's local zone rules for that date. In UTC mode, the value is anchored to UTC. In Custom UTC offset mode, the form applies a fixed offset from UTC-12:00 to UTC+14:00 in 15-minute steps. That fixed-offset path is useful when a record already says something like UTC+05:30 or UTC+09:45 and you do not want daylight-saving rules changing the meaning later.

The elapsed interval is measured on the timeline between the two interpreted instants. The wall-clock span is measured separately from the entered calendar fields without converting them into different zones first. When those two numbers differ, the gap appears as Zone/DST adjustment vs wall clock. That is the tool's clearest warning that the same pair of local-looking timestamps do not point to the same amount of elapsed time.

The calendar breakdown is built from largest units to smallest units. The tool steps from the earlier instant to the later one by counting whole years first, then whole months, then days, hours, minutes, seconds, and milliseconds. That is a standard way to express human-readable duration, but it also means month boundaries follow real calendar lengths. A result that looks surprising at first is often a consequence of February being shorter than January, not a broken calculation.

\begin{array}{lcl} elapsed & = & | t_{end} - t_{start} | \\ wallClock & = & | civil ({end}_{input}) - civil ({start}_{input}) | \\ zoneAdjustment & = & elapsed - wallClock \\ businessOverlap & = & sum of only the interval segments that fall inside each counted day's business window \end{array}

How the main result families are calculated
Result family	What drives it	How to read it
`Duration (calendar breakdown)`	Whole years, then whole months, then smaller units between the earlier and later instant	Best when you need a human-readable answer such as "2 months, 5 days, 4 hours."
`Total years` through `Total seconds`	The same elapsed span divided into decimal unit totals, shown with the selected precision	Best for sheets, calculations, and export where one unit needs to stay consistent.
`Wall-clock span`	The difference between the entered calendar fields before time-zone conversion	Best for checking how the interval looks to someone reading the local date and time strings.
`Zone/DST adjustment vs wall clock` and `Offset shift across interval`	The gap between elapsed time and wall-clock time, plus the difference between the applied start and end offsets	Use these fields to catch mixed-zone inputs and daylight-saving effects.
`Working days` and non-working splits	The selected weekday calendar, holiday list, and end-date inclusion rule	These are date counts, not hour counts. They answer schedule questions.
`Business-window overlap` and `Business-day equivalents`	Only the portions of counted working days that fall inside the daily business window	These are the fields to trust when you need staffed time rather than simple elapsed time.
`Capacity hours from working days`	`Working days x Capacity hours/day`	This is a planning estimate. It is separate from the measured business-window overlap.

Working-day counting and business-window overlap follow different rules on purpose. Working-day counts look only at calendar dates. Business overlap looks at the actual time segments inside each counted day. That is why a two-day interval can show two working days but less than two full business days if the interval starts late, ends early, or loses time to weekends, holidays, or time-zone interpretation.

The midpoint and all checkpoint timestamps are generated from the earliest instant to the latest instant. If you enter the end before the start, the tool warns about the chronology but still uses the absolute difference for totals and charts. The midpoint and checkpoint timestamps are then shown using the zone interpretation of the earlier endpoint, which keeps the ladder internally consistent.

The browser also sets the practical limits. The tool handles civil dates, clock times, offsets, and daylight-saving-aware local timestamps, but it does not expose named time zones beyond the device's own local zone, and it is not intended for leap-second-sensitive timing or legal-calendar edge cases that require a jurisdiction-specific rule set.

Everyday Use & Decision Guide

Start with the question, not the fields. If the job is simply to measure the real elapsed span between two known instants, enter the two datetimes and read the duration totals first. If the job is to understand how a handoff feels on the clock in two places, compare Wall-clock span with Total hours and look for a nonzero zone adjustment. If the job is staffing or scheduling, move next to working-day settings, holiday exclusions, and the business window.

The safest time-zone choice depends on the source data. Use Local when both values were captured in the same local environment and you want the browser's current local rule set for those dates. Use UTC when the source already stores timestamps in UTC. Use Custom UTC offset when the original record came with a numeric offset and you need to preserve that exact offset instead of relying on a location-specific rule.

Read Duration (calendar breakdown) when another person needs a plain-language answer. Read decimal totals when another system needs one unit only.
If Wall-clock span and Total hours disagree, treat that as useful information, not noise. The tool is showing that local clock wording and elapsed time are telling different stories.
Use the working-week preset that matches the real calendar first. Monday to Friday, Monday to Saturday, Sunday to Thursday, all days, and custom weekdays produce different schedule counts even when the elapsed span stays the same.
Add holiday dates only in YYYY-MM-DD form. Accepted dates are counted; invalid or repeated tokens are ignored and reported separately.
Use Capacity hours/day for planning estimates and Business window for actual overlap. They answer different questions and should not be treated as interchangeable.
Change Checkpoint plan only when the review cadence changes. It does not change the duration itself; it changes where the ladder and progress markers sit.
When the result needs to leave the page, choose the output that matches the destination: CSV or DOCX for tables, chart downloads for visual summaries, and JSON when another system needs structured data.

Which tab or field to use for common datetime questions
If you need to know...	Read this first	Why
The real elapsed time between two instants	`Total hours`, `Total days`, or `ISO 8601`	These stay tied to the actual timeline difference.
How far apart the entered local date-and-time strings look	`Wall-clock span`	It ignores zone conversion and shows the civil-clock gap.
How many work dates a plan crosses	`Working days`, `Weekend/off days`, and holiday counts	Those outputs follow the selected calendar rules instead of raw elapsed time.
How much of the interval is actually staffed	`Business-window overlap` and `Business-day equivalents`	These are the time-based staffing outputs.
Where internal reviews should sit	`Checkpoint Ladder` and `Progress Curve`	They show milestone timestamps plus elapsed and business-hour progress.

A quick confidence check is to compare three lines together: the chronology note, the elapsed total you care about, and the schedule metric you care about. When those three agree with the real situation, the rest of the page usually becomes straightforward.

Step-by-Step Guide

Enter the start date and time, then the end date and time. If you want the current moment, use the Now button on the relevant side.
Pick the time-zone interpretation for each endpoint. Stay with Local for same-environment entries, switch to UTC for normalized timestamps, or use Custom UTC offset when the source includes a numeric offset.
If the entered end is really the earlier moment, either leave it as entered and read the chronology warning, or use Swap start & end to align the order before you export.
Open Advanced and set the working week, custom weekdays if needed, the end-date inclusion rule, capacity hours per day, the daily business window, and any holiday dates that should be excluded from working-day counts.
Choose the checkpoint plan that matches your review pattern. Quarters is the simplest default, Thirds is useful for shorter plans, and Handoff reviews adds 10%, 25%, 50%, 75%, and 90% markers.
Read the summary box and Delta Ledger first. Confirm the duration, wall-clock span, zone adjustment, working-day totals, and business-window overlap before trusting the charts.
Use Checkpoint Ladder, Schedule Mix, Unit Scale Bars, and Progress Curve only after the main table looks right. Then export as CSV, DOCX, chart image, chart CSV, or JSON as needed.

Interpreting Results

The most important distinction is between elapsed time and calendar or staffing interpretation. Total hours answers how much time truly passed between the two interpreted instants. Working days answers how many counted dates fall inside the chosen calendar. Business-window overlap answers how much of the interval sits inside the staffed part of those counted dates. A single interval can produce very different values in those three outputs without any contradiction.

Wall-clock span is the line that catches many quiet mistakes. If two timestamps look eight hours apart on their local clocks but only three hours apart on the timeline, the tool shows both numbers and reports the zone or daylight-saving impact. That helps you see the difference between "how the timestamps were written down" and "how much time actually passed."

The planning fields add a second kind of interpretation. Midpoint is the half-way instant across the full elapsed span. The checkpoint ladder uses the selected plan to place review moments across the same interval. Planning recommendation is a heuristic summary based on zone adjustment, holiday exclusions, working-day share, and business-hour share. It is useful as a prompt, not as a policy engine.

How to interpret the main datetime difference outputs
Field	What it tells you	Common mistake to avoid
`Duration (calendar breakdown)`	A human-readable decomposition of the elapsed span into mixed calendar units	Do not assume the month count can be converted to days with one fixed multiplier.
`Total days`, `Total hours`, and related totals	The elapsed span expressed in one unit at a time	The decimal-place slider changes the display precision, not the underlying interval.
`Wall-clock span`	The difference between the entered civil date-and-time values before zone conversion	Do not read this as the real elapsed time when endpoints use different zone interpretations.
`Working days`	The number of counted calendar dates after weekday and holiday rules are applied	It does not measure hours and it can change when you toggle end-date inclusion.
`Business-window overlap`	The actual hours that fall inside the configured daily work window	Do not confuse it with `Capacity hours from working days`, which is an estimate.
`ISO 8601` and `JSON`	Compact export-friendly representations of the same interval	They do not add new interpretation rules; they package the current result.

When mixed-zone inputs are involved, trust the combination of chronology, elapsed totals, and zone adjustment over intuition. Local clock readings alone are often enough to misread a handoff, especially around daylight-saving changes or when each endpoint came from a different region.

Worked Examples

A same-zone project window that crosses a weekend

Enter a start of 2026-04-10 09:00 and an end of 2026-04-13 17:00 with both endpoints in the same local interpretation. The elapsed span is 3 days, 8 hours, or 80 total hours. With a Monday to Friday workweek and the end date included, the schedule count becomes 2 working days and 2 weekend/off days. With a business window of 09:00 to 17:00, the staffed overlap is 16 hours, because only Friday and Monday contribute working-window time.

Two timestamps that look eight hours apart but are only three hours apart

Enter 2026-04-10 09:00 as UTC-04:00 and 2026-04-10 17:00 as UTC+01:00. On the clock, the written times are eight hours apart, so Wall-clock span shows 8.00 h. On the timeline, those instants are 13:00 UTC and 16:00 UTC, so Total hours becomes 3.00 h. The zone-adjustment line shows the gap directly, which is exactly why mixed-zone comparisons should not be judged by the clock face alone.

Holiday and staffing rules changing a delivery window

Enter a start of 2026-12-23 09:00 and an end of 2026-12-28 17:00, keep a Monday to Friday calendar, and add 2026-12-25 as a holiday exclusion. The elapsed span is 5 days, 8 hours. The counted work dates become 3 working days, with 1 holiday and 2 weekend days. With a 09:00 to 17:00 business window, the staffed overlap is 24 hours. The midpoint lands during the weekend, which makes the checkpoint ladder especially useful for placing internal reviews earlier than the simple half-way mark.

FAQ:

Does the calculator ever return a negative duration?

No. If the entered end comes before the entered start, the page warns about the chronology and then uses the absolute difference for totals, tables, and charts.

Why can Wall-clock span and Total hours disagree?

They answer different questions. Wall-clock span compares the entered civil date and time values. Total hours compares the interpreted instants on the timeline after the chosen zone or offset rules are applied.

Can I compare different regions without picking a named time zone?

Yes, within limits. You can use UTC or fixed UTC offsets for both endpoints. The tool does not offer a separate named-zone picker for locations beyond the device's own local zone.

Why can the month and day breakdown look odd around short months?

Because the duration is expressed by counting larger calendar units before smaller ones. Real month lengths vary, so some spans that have the same total days can still produce different-looking month-and-day combinations.

What format do holiday exclusions need?

Use YYYY-MM-DD. You can separate dates with commas, spaces, or new lines. Invalid, duplicate, or malformed tokens are ignored and counted in the ignored total.

Can the business window run overnight?

No. The end of the business window must be later than the start on the same clock day. Overnight staffing windows need to be split outside this tool.

Are the calculations and exports local to the browser?

Yes. The page calculates results, builds charts, and generates CSV, DOCX, image, and JSON exports without a server-side processing step.

Does the result account for leap seconds?

No. The page follows ordinary browser date-and-time handling for civil scheduling work. It is not meant for leap-second-sensitive measurement.

Glossary:

Instant: A specific point on the timeline after the entered date, time, and zone interpretation have been combined.
Wall-clock span: The difference between the entered local-looking date and time values before time-zone conversion.
Fixed UTC offset: A numeric offset such as UTC+05:30 that stays fixed instead of following location-based daylight-saving rules.
Working day: A calendar date that matches the selected weekday pattern and is not excluded by the holiday list.
Business-window overlap: The portion of the elapsed interval that falls inside the configured daily work window on counted working days.
ISO 8601 duration: A standard text form for a duration, using tokens such as P, Y, D, T, H, M, and S.

References:

Working with Time and Timezones, W3C Group Draft Note, 26 July 2025.
RFC 9557: Date and Time on the Internet: Timestamps with Additional Information, IETF, May 2024.
ISO 8601: Date and time format, ISO.
FAQ: Time Duration Calculator, timeanddate.com.