Time Zone Converter
Runs in your browserPick a moment in one zone and read it in all the others at once — with the offset that actually applied on that date, not a fixed one.
Showing right now, live
How this one works
Pick a date and time and say which zone you typed it in; everything else is the same instant, written the way a clock in each place would show it. Leave the date empty and the table follows the current moment instead.
Offsets come from your browser's copy of the IANA time zone database, looked up for the exact date you chose rather than today — so a meeting in late March converts with the offsets that will actually be in force then, and the abbreviation changes with it (EST to EDT, GMT to BST). When a converted time lands on a different calendar day, the row says so, because that is the mistake that costs people a meeting.
Questions
- Why does the offset change depending on the date?
- Daylight saving. New York is UTC-05:00 in January and UTC-04:00 in July, and the switch dates differ by country. That is why a converter that hardcodes offsets gets the shoulder months wrong, and why this one always asks the browser for the offset at that exact instant.
- What if the time I pick does not exist, or happens twice?
- Both are flagged above the table. When clocks go forward an hour is skipped, so a reading inside it never happens and the conversion uses the moment it runs into. When clocks go back an hour repeats, and the earlier of the two is used.
- Can I share a comparison?
- Yes. The date, the base zone and the list of zones are all in the page address, so copying the URL from your browser sends someone the same table. Nothing is stored on a server — the link itself carries everything.