Spin the globe, pick any city, and see every timezone at once. Plan meetings, schedule calls, never mis-read a time again.
Yes. It uses the IANA timezone database, which encodes DST transitions for every region. Times near a switch boundary are computed correctly, including fractional offsets like India (+5:30) and Nepal (+5:45).
Many regions, including Japan, China, India, Iceland, and most of Africa, do not observe DST. Others, like Arizona in the US, opt out. The converter respects each region's rules automatically.
Yes. Every city you add is saved automatically in your browser via local storage and will reappear the next time you open the tool. No account needed.
Open the Meeting Planner tab. The 24-hour UTC overlay highlights working hours (9 to 18 local) in every city. Cells outlined in green are the overlap. Use the day slider to shift the timeline forward or backward.
The IANA database goes back decades, so historical conversions are reliable for most modern dates. Very old dates (pre-1970) may be approximate as standard time was inconsistently observed.
If zones followed the sun strictly, each would be a clean 15-degree slice. In reality China spans five geometric zones but uses one clock, Spain runs on Central European time despite sitting on the Greenwich meridian, and India and Iran offset by half hours (+5:30, +3:30) while Nepal uses +5:45. This is why reliable conversion uses named zones from the IANA database (Europe/Athens, America/New_York) rather than raw offsets: the name carries the political rules, including when they change.
The US and Europe shift on different weeks: the US springs forward in mid-March, Europe in late March, and the autumn changes diverge too. For roughly three weeks a year the usual New York to Athens gap of 7 hours becomes 6, and standing meetings silently move. The only safe habit is to schedule in one anchor zone and let everyone else convert, never to memorise an offset.
Advertisement