The Time Difference Calculator compares a date-specific local time in one named IANA timezone with the matching time in another. It preserves one instant, applies seasonal UTC offsets, shows both offsets, reports the signed minute difference, and flags a date rollover. Use it for meetings, launches, travel, support coverage, and distributed work.
Read the output as two local representations of one instant. The source date and time belong to the Reference location; comparison time, target date, abbreviation, and offset represent that instant elsewhere. The signed minute difference explains clock movement; rollover explains date movement. Verify schedules against the controlling policy. reviewedAt records this content update and fixture testing, not official human review.
How this is calculated
The date and HH:mm value are interpreted in the Reference location. The engine resolves that wall-clock value with IANA rules, formats the same instant in the comparison zone, and calculates offsetMinutes as target offset minus source offset. Negative means the comparison clock is earlier; positive means later. A spring-forward gap must be rejected, while a repeated fall-back label needs offset confirmation.
Assumptions and limits
The date is required because offsets change by season.
The selector is a finite list of named zones, not an arbitrary city search.
This is planning information, not a legal, employment, transport, venue, or contractual determination; share date, time, zone, and offset.
Duration is separate: browser-local arithmetic has no IANA selector and distinguishes components from total seconds.
BusinessDaysBetween includes eligible weekdays at both endpoints and its UI is unsigned for reversed ranges; deadline advancement excludes the start, skips weekends only, and has no regional holiday selector.
The in-progress age policy clamps Feb 29 birthdays to Feb 28 in non-leap years and normalizes components; this is not legal-age advice.
Worked examples
India morning becomes New York evening on the prior date
Inputs: 2026-01-15 09:00; Asia/Kolkata to America/New_York
Result: Wed, Jan 14 · 22:30 EST; -630 minutes
The target is 10 hours 30 minutes earlier and lands on January 14, so the rollover matters.
Summer daylight saving changes the offset
Inputs: 2026-07-15 09:00; America/New_York to Europe/London
Result: Wed, Jul 15 · 14:00 GMT+1; +300 minutes
July rules make London five hours later; a winter shortcut would be wrong.
Late Pacific time becomes Tokyo's next date
Inputs: 2026-01-15 23:30; America/Los_Angeles to Asia/Tokyo
Result: Fri, Jan 16 · 16:30 GMT+9; +1020 minutes
The 17-hour gap crosses midnight, so the target date must travel with the time.
Boundary cases
A spring-forward gap contains no such local label; reject it instead of silently moving the instant.
A repeated fall-back hour has two possible instants; confirm the intended UTC offset before publishing it.
A large offset difference can cross midnight; include target date and rollover, not only the clock time.
Invalid dates, malformed times, or unsupported zones produce no conversion; correct inputs instead of treating blank as zero.
Timezone conversion does not remove weekends, holidays, or company closures; no workday tool is universally holiday-adjusted.
Common mistakes
Using a memorized city difference without checking event date and DST status.
Sharing a clock time without its converted date, named zone, or UTC offset.
Treating a repeated fall-back label as one instant without confirming the offset.
Using browser-local duration as IANA conversion, or this page for workdays, holiday deadlines, legal age, or contractual cutoffs.