When
Live: the table follows the clock.
The first row. Every other zone is compared with it.
Search by city, region or UTC offset.
How this one works
Choose Now to see the current time everywhere, or Date & time to convert a meeting, a deadline or a timestamp from a log. The reference zone is the first row: it is where a time you type is read, and every other row says how far ahead or behind it is. Set as reference on a row makes that zone the reference without changing the moment shown.
Offsets come from your browser's copy of the IANA time zone database, looked up for the exact date shown rather than today, so a meeting in late March converts with the offsets in force on that date, and the zone's name changes with it (Eastern Standard Time to Eastern Daylight Time). A sun or moon shows whether it is day or night there, and a row that lands on another calendar day 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.
How do I find a meeting time that works everywhere?
Choose Date & time, pick a time in the reference zone and watch the sun and moon icons: a time that is daytime in every row suits everyone. Change the time and every row follows.
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 time, the reference 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.