Time Zone Calculator
Convert a local date and time from one time zone to another, with date-aware daylight saving time handling and the UTC hour differential.
How It's Calculated
Formula
\text{UTC instant} = \text{local time} - \text{origin offset}(\text{zone}, t) \qquad \text{destination time} = \text{UTC instant} + \text{destination offset}(\text{zone}, t)This calculator converts a local date and time from one named time zone to another. Every UTC offset it uses is looked up live for the specific zone and the specific date being converted — never a fixed constant — so the conversion is fully date-aware: the same zone pair can have a different hour differential in January than in July if either zone observes daylight saving time. Time zones are entered as IANA identifiers (e.g. "America/New_York", not the ambiguous abbreviation "EST"), because an abbreviation like EST or IST can refer to several different zones around the world with different rules and offsets. Twice a year, daylight saving time transitions can make a local wall-clock time ambiguous (it occurs twice, during a "fall back") or nonexistent (it's skipped entirely, during a "spring forward"); this calculator handles both cases explicitly rather than silently producing a wrong result — see the FAQ below.
Worked Examples
UTC to Europe/London
- Local time: 2026-01-15, 12:00, origin zone UTC, destination zone Europe/London
- London observes GMT (UTC+0) in January, so the destination time is also 12:00
- UTC hour differential = 0
Europe/London to America/New_York, across DST
- Local time: 2026-01-15, 12:00, origin Europe/London, destination America/New_York
- In January both zones are on standard time; New York is 5 hours behind London
- Destination time = 07:00, UTC hour differential = -5
- Repeating the same conversion in July (both zones on daylight saving time) still gives a -5 hour differential, because UK and US clocks shift together
Frequently Asked Questions
What happens if I enter a local time that doesn't exist, like 2:30 AM during a 'spring forward'?
The calculation is rejected with a clear message explaining that the time doesn't exist in that zone due to a daylight-saving transition, rather than silently shifting it to some nearby valid time.
What happens if I enter a local time that occurs twice, like 1:30 AM during a 'fall back'?
This calculator deterministically uses the earlier of the two occurrences (the one before clocks are set back) and flags the result as ambiguous, rather than guessing.
Why does this calculator use names like 'America/New_York' instead of 'EST' or 'IST'?
Abbreviations like EST or IST are ambiguous — IST alone could mean Indian, Irish, or Israel Standard Time, and EST doesn't indicate whether daylight saving is in effect. IANA time zone identifiers name a specific region with a specific, unambiguous rule set for every date, which is what makes an accurate date-aware conversion possible.
Why can the UTC hour differential change between two dates for the same pair of zones?
If one zone observes daylight saving time and the other doesn't (or they switch on different dates), the gap between their offsets changes over the year. This calculator always looks up the real offset for the exact date entered, so the differential shown is correct for that specific date.