Time Zone Converter

How to use

1. Set a date and time, and the place it belongs to.
2. Add the places you need to see it in — your own zone is included automatically.
3. Read the same moment on each clock, with the day noted when it differs.
4. Watch for the warning on the two hours a year that are not ordinary.

Features

• Any IANA zone, with daylight saving applied as it was on that date.
• The hour skipped when clocks go forward, and the hour repeated when they go back, both named.
• Half-hour and quarter-hour zones handled — India, Nepal, Chatham.
• The offset and the short name each place used at that moment.
• Runs entirely in your browser.

Frequently asked questions

Why is 9am in New York not always the same UTC time?

Because the offset changes twice a year. In July, 9am in New York is 13:00 UTC; in January it is 14:00. A wall-clock time is not a fixed point until you know the date, which is why this tool asks for one and why converting with a fixed offset is wrong for half the year.

What does "this time never happened" mean?

When clocks go forward, an hour is skipped. In New York on 8 March 2026 the clock jumps from 01:59 to 03:00, so 02:30 does not exist that day. Most converters answer anyway and give you a time that never occurred. This one says so, and shows the nearest real instant.

And when a time happens twice?

When clocks go back, an hour repeats. 01:30 on 1 November 2026 happens twice in New York, an hour apart, and nothing in the wall-clock time says which you meant. The first occurrence is shown, and the ambiguity is flagged — worth knowing before scheduling anything in that hour.

Why use city names rather than offsets like GMT+7?

Because an offset is not a place. GMT+7 tells you nothing about whether it will still be GMT+7 next month, whereas Asia/Ho_Chi_Minh carries its whole history of changes. Storing offsets instead of zone names is the usual reason a calendar entry drifts by an hour.

Related tools