World clock and time zones
The current time in thirty-one places at once — change the reference time to plan a call.
See what time it is somewhere else, and what hour here lands while the other side is awake. Daylight saving changes country by country and year by year; the browser already carries that data and keeps it current, so this page ships no table of its own — there is nothing here to go stale.
Reference point
What you enter is saved in this browser, so it is still here next time
Gaps are measured from this city
Redraws itself as each minute turns.
At that moment
Reading the clock…
| City | Local time | Date | From UTC | Gap |
|---|---|---|---|---|
| Seoul | — | — | — | — |
| Tokyo | — | — | — | — |
| Shanghai | — | — | — | — |
| Hong Kong | — | — | — | — |
| Singapore | — | — | — | — |
| Bangkok | — | — | — | — |
| Jakarta | — | — | — | — |
| Delhi | — | — | — | — |
| Dubai | — | — | — | — |
| Moscow | — | — | — | — |
| Istanbul | — | — | — | — |
| Berlin | — | — | — | — |
| Paris | — | — | — | — |
| Madrid | — | — | — | — |
| Rome | — | — | — | — |
| London | — | — | — | — |
| Cairo | — | — | — | — |
| Lagos | — | — | — | — |
| Johannesburg | — | — | — | — |
| São Paulo | — | — | — | — |
| New York | — | — | — | — |
| Toronto | — | — | — | — |
| Chicago | — | — | — | — |
| Denver | — | — | — | — |
| Los Angeles | — | — | — | — |
| Mexico City | — | — | — | — |
| Honolulu | — | — | — | — |
| Sydney | — | — | — | — |
| Perth | — | — | — | — |
| Auckland | — | — | — | — |
| UTC (Coordinated Universal Time) | — | — | — | — |
Daylight saving comes from the IANA time zone data inside your browser. This page ships no table of its own, so a rule change does not leave it stale.
Computed from the browser's time zone data
Each city's clock is read by giving Intl.DateTimeFormat an IANA name such as America/New_York and turning the parts it returns back into numbers. The offset is that wall clock read as UTC minus the actual instant, so Seoul is +540 minutes, or +9:00. New York comes out as −4:00 in summer and −5:00 in winter on its own — no rule is written down here; the browser's data is followed as is. The gap column subtracts the base city's offset, so from Seoul, London is +1 − 9 = −8 hours in summer and −9 in winter.
Meeting times are entered on the base city's clock
Choosing a date and time instead of "now" reads them on the base city's wall clock, turns them into one instant and recomputes all thirty-one places for it. Seoul 14:00 is London 06:00 in summer and 05:00 in winter, New York 01:00 or 00:00, Los Angeles 22:00 or 21:00 the previous day. Going from wall clock to instant needs the offset, and the offset needs the instant — a loop resolved by estimating once and correcting twice, which puts even the hour of a daylight-saving switch in its right place.
Rows are sorted by offset; only differing dates get a date
The thirty-one rows run from the smallest UTC offset to the largest — Honolulu at the top, Auckland at the bottom — so the table reads as a day flowing west to east. The base city's row is highlighted, and only rows whose date differs from the base city's carry "yesterday" or "tomorrow" and a month-day. Delhi at +5:30 is 3 h 30 min from Seoul, and since offsets are measured in minutes that comes out exactly. On first paint "now" is not yet known, so the rows show "—" until the page attaches and the values arrive.
What it does not do
Cities cannot be added or removed — the list is fixed at thirty-one, and anywhere else means picking a neighbour in the same zone. Seconds are not counted; it stops at minutes. Only one instant is shown at a time — it does not find "when both offices are open", so you read the table while moving the time. Historical daylight-saving rules are only as right as the browser's data.
Common questions
QIs daylight saving handled?
Yes. The IANA time zone data built into your browser is used as is. Set the reference time to summer and then winter and New York moves between −4 and −5 hours. Because no rule is written down here, a rule change does not leave this page wrong.
QWhy does Korea never shift?
Korea used daylight saving until the 1988 Seoul Olympics and then dropped it, so Korean Standard Time sits at UTC+9 all year. Only the other country moves, which makes the gap seem to change by an hour each spring and autumn.
QMy city is not listed.
Thirty-one commonly used places are listed; showing all four hundred zones makes finding one slower, not faster. Cities in the same zone share the same clock, so picking a nearby one is usually exact.
QWhat time is 2 pm in Korea in New York?
1 am in summer and midnight in winter. The US observes daylight saving from the second Sunday in March to the first Sunday in November, so the gap is 13 hours in between and 14 hours otherwise. Set Seoul as the base and enter 14:00 and the New York row shows it with a "previous day" mark.
QAre half-hour offsets handled?
Yes. Delhi is UTC+5:30, 3 h 30 min from Seoul, and the table measures offsets in minutes so that is what it shows. Nepal at +5:45 is not in the list, but the same data would count quarter-hour zones the same way.