Time zone converter
Compare a time across cities and find the overlap in everyone’s working day.
| Zone | Time | Date | Abbrev | Offset |
|---|---|---|---|---|
| UTC UTC | 18:00 | Tue, Jul 28 | UTC | UTC+00:00 |
| New York America | 14:00 | Tue, Jul 28 | EDT | UTC−04:00 |
| London Europe | 19:00 | Tue, Jul 28 | GMT+1 | UTC+01:00 |
| Tokyo Asia | 03:00 | Wed, Jul 29 | GMT+9 | UTC+09:00 |
Working-hours overlap
Shaded blocks are 09:00–18:00 local. Look for a column shaded everywhere.
Add zones
How it works
Time zones are political, not astronomical. Offsets change with daylight saving, governments revise them, and some are not whole hours — India is UTC+05:30, Nepal UTC+05:45, and the Chatham Islands UTC+12:45.
Why this uses zone names, not offsets
“UTC−5” is not the same as “New York”. New York is UTC−5 in winter and UTC−4 in summer, and the switch dates differ from Europe's by several weeks — so for two weeks each spring and autumn, the London-to-New-York gap is four hours rather than five. Using IANA zone identifiers means the browser's own time-zone database resolves all of that correctly for any date you pick.
Scheduling across zones
The overlap grid shows where everyone's working day intersects. When no column is shaded everywhere, someone is taking an early or late call — better to know that while scheduling than to discover it in the invite. For recurring meetings, remember that the overlap shifts when one region's clocks change and the other's do not.
UTC never changes
Coordinated Universal Time has no daylight saving, which is why logs, APIs and aviation use it. If you are storing a timestamp, store UTC and convert on display.