YourWorldTime

Time zone converter

Pick two zones and a date, and this converts between them exactly — including on the two days a year when daylight saving makes a local time either impossible or ambiguous.

Convert a time

Converted time

Next change

Offsets and dates are computed at build time from the IANA database. Live times render in your browser.

FromUTCNext change
New YorkUTC-42026-11-01 Clocks go back 60 minutes
Los AngelesUTC-72026-11-01 Clocks go back 60 minutes
LondonUTC+12026-10-25 Clocks go back 60 minutes
BerlinUTC+22026-10-25 Clocks go back 60 minutes
KolkataUTC+5:30Does not observe daylight saving time
TokyoUTC+9Does not observe daylight saving time
SingaporeUTC+8Does not observe daylight saving time
SydneyUTC+102026-10-04 Clocks go forward 60 minutes

What makes time zone conversion go wrong

Almost every scheduling mistake comes from one of four places, and all four are handled here rather than rounded away.

The offset is not a constant. "New York is five hours behind London" is true for about ten months of the year. For roughly three weeks each spring and one each autumn it is four hours, because the two regions change their clocks on different dates. A converter that stores a fixed offset per city is wrong on those days, and those are exactly the days people book the meeting they later regret.

Not every offset is a whole number of hours. India is 5 hours 30 minutes ahead of UTC. Nepal is 5 hours 45 minutes ahead. The Chatham Islands are 12 hours 45 minutes ahead, and Lord Howe Island shifts by only 30 minutes when its daylight saving starts. Roughly a fifth of the world lives on a non-whole-hour offset.

Some local times do not exist. When clocks spring forward, an hour is deleted. In New York on the changeover date, 01:59:59 is followed immediately by 03:00:00 — so 02:30 never happens. Ask most tools to convert 02:30 and they will answer confidently anyway. This one tells you what it did.

Some local times happen twice. When clocks fall back, an hour repeats. 01:30 occurs once on daylight time and again an hour later on standard time. This converter takes the first occurrence and says so, and shows you the second.

Common questions

Does this converter handle daylight saving time?
Yes, and it handles the two awkward days as well. Offsets come from the IANA time zone database through the browser, so a conversion on a change-over date uses the offset that actually applied at that moment, not the one that applies today. If you enter a local time that never happened, or one that happened twice, the converter says so instead of silently picking one.
Why does the time difference between two cities change during the year?
Because the two places rarely change their clocks on the same date, and some never change them at all. New York is 5 hours behind London for most of the year but 4 hours behind for two weeks in March, because the United States moves its clocks two to three weeks before Europe does. Always convert against a specific date rather than a remembered offset.
Which time zones can I convert between?
Every zone in the IANA database — over 400 of them, including the half-hour and 45-minute offsets that trip up most converters. India at UTC+05:30, Nepal at UTC+05:45 and the Chatham Islands at UTC+12:45 are all handled exactly, not rounded to the nearest hour.
Do I need JavaScript?
For the live converter, yes. Everything else on this site — offsets, daylight saving transition dates, hour-by-hour reference tables and every explanation — is part of the prerendered page and works with JavaScript disabled.
Is anything I type here sent anywhere?
No. Every calculation happens in your browser. There is no backend, no analytics, no cookies and no third-party script. The zones you pick appear in the URL so you can share or bookmark a conversion, and that is the only place they go.