Understanding the result
The main result is the local time in the destination zone, with its date and weekday. Beneath it you can see the UTC offset and abbreviation of each zone at that moment and how far apart they are on that date.
A note appears when the converted date differs from the entered date, or when the time you entered was skipped or repeated by a clock change.
What is a time zone converter?
A time zone converter answers "when it is 3 pm here, what time is it there?". It is used to schedule meetings and calls across regions, follow live events and plan travel.
Zones are chosen by IANA identifiers such as Europe/Dublin or America/New_York. These identify a region and its whole history of clock rules, not just a single offset.
How it works
The entered date and time are first placed on the timeline using the source zone's rules on that date, giving an exact moment. That moment is then displayed as a local date and time in the destination zone using its rules on the same date.
Offsets come from your browser's copy of the IANA time zone database, so daylight saving changes, half-hour offsets (India +05:30), 45-minute offsets (Nepal +05:45) and historical changes are handled from data rather than assumed.
When clocks jump forward, some local times never occur. When they go back, some occur twice. The tool reads a skipped time using the offset before the change and picks the first occurrence of a repeated time, and says so.
Examples
London to Tokyo
20:00 in London on 15 January 2026 is 05:00 the next day in Tokyo (a 9-hour difference in winter). In July, when London is on summer time, the gap shrinks to 8 hours.
Sydney to Los Angeles
09:00 on 15 January 2026 in Sydney is 14:00 on 14 January in Los Angeles: the date is a day earlier there.
Dublin and New York in March
They are usually 5 hours apart. In mid-March, after the United States has changed its clocks but Europe has not, 12:00 in Dublin on 15 March 2026 is 08:00 in New York: 4 hours.
A time that does not exist
Clocks in New York jump from 02:00 to 03:00 on 8 March 2026. 02:30 that day never happens; the tool reads it as 07:30 UTC, which is 03:30 on the local clock, and explains this.
Things to keep in mind
- Time zone rules are set by governments and change occasionally, sometimes with little notice. Your browser's data may lag behind a very recent change.
- Daylight saving starts and ends on different dates in different countries, so the difference between two places is not constant through the year.
- Abbreviations such as IST or CST are ambiguous (IST can mean India, Ireland or Israel). The UTC offset is always shown alongside for that reason.
- For meetings, share the date, time and the zone (for example "15:00 Europe/London") rather than only an offset.