Utilities · Time across zones

World Clock

What time is it for everyone else

Track any number of cities, see who is inside working hours, and read every offset straight from the browser’s own time-zone data.

Every IANA zoneDST awareWorking hoursLive
Zones
All IANA
DST
Automatic
Uploaded
0 B

World Clock

Runs in your browser · nothing uploaded
You: UTC
  • London

    12:06

    Thu 29 Oct · UTC

    same time working hours

  • Berlin

    13:06

    Thu 29 Oct · UTC+1

    1h ahead working hours

  • New York

    08:06

    Thu 29 Oct · UTC−4

    4h behind

  • Los Angeles

    05:06

    Thu 29 Oct · UTC−7

    7h behind night

  • Kolkata

    17:36

    Thu 29 Oct · UTC+5:30

    5h30m ahead

  • Tokyo

    21:06

    Thu 29 Oct · UTC+9

    9h ahead night

  • Sydney

    23:06

    Thu 29 Oct · UTC+11

    11h ahead night

7 cities · 2 currently in working hours · offsets read from this browser’s time-zone data

01 — How to use World Clock

1 Start from the default board Seven cities across the major regions are shown from the moment the page loads, with times updating every second.
2 Add the zones you care about Type a city or an IANA zone name — the field suggests from every zone your browser knows, which is typically well over four hundred.
3 Check who is available Working hours now filters the board to cities currently between 09:00 and 17:00 on a weekday. The Vs you column gives the difference from your own zone.
4 Remove what you do not need Click any row to take that city off the board. Reset restores the default set.

02 — Getting good results

Offsets are calculated, never stored Every offset on this page is worked out by asking the browser what the wall clock reads in that zone at this instant, and comparing it to UTC. That is the only approach that is right all year: a stored number like "UTC+1 for London" is wrong for roughly half of it, and hardcoded tables go stale whenever a country changes its rules — which several do every year.
The date column matters more than it looks When it is Monday evening in London it is already Tuesday morning in Sydney. Arranging a call by time alone is how meetings end up scheduled on the wrong day. The date shown is the date in that city, derived from that city's own calendar rather than from yours.
Southern-hemisphere daylight saving runs the other way Sydney is ten hours ahead of UTC during the northern summer and eleven during the northern winter, because its own summer falls in the opposite half of the year. The gap between London and Sydney therefore changes by two hours over the year, and there are short windows around the transitions where it is neither of the usual values.
Not every offset is a whole number of hours India is five and a half hours ahead of UTC, Nepal five and three-quarters, and parts of Australia use forty-five-minute offsets. Any tool that assumes whole hours gets those wrong. The offsets here come from the same database your operating system uses, so the unusual ones are simply correct.

03 — Questions

No. Time zone data ships inside your browser, so every calculation happens locally. Nothing about which cities you track leaves the tab, and none of it is stored between visits.

04 — More about World Clock

61 more tools
where this came from.

Same shell, same shortcuts, same promise: nothing leaves your browser.

Browse all 62