World Clock

Build your own board of city clocks drawn from 96 countries and 120 cities; every tile ticks once a second and the board is still there on your next visit.

What is the World Clock?

The World Clock answers one question, repeatedly: what time is it there right now. A card at the top gives your own 24-hour time, the full date and the time zone name your browser reports, and below it you assemble a grid of cities picked country first, then city. The 120 cities map onto 113 distinct zone identifiers, so some entries necessarily share a clock: Beijing and Shanghai both read from Asia/Shanghai, and Rio de Janeiro shares Sao Paulo's zone.

Key Features

• Country picker then city picker, covering 120 cities across 113 zones
• Cards refresh every second, showing 24-hour time with seconds
• Each card carries its own local date, so tomorrow is visible
• Saved cities persist in the browser, surviving reloads and later visits
• Filter box narrows a long board by typing part of a city name

Common Use Cases

• Checking whether it is a civil hour to call a supplier abroad
• Watching a relative's local time before setting up a weekend video call
• Tracking a market open or a match start in the city where it happens
• Keeping a standing board of the offices you deal with every week

How to Use the World Clock

1. Choose a country from the first dropdown; the city list unlocks beside it.
2. Pick a city and press Add to place its card on the board.
3. Repeat for every office, family member or market you follow.
4. Type into the filter box to narrow a long board down to one city.
5. Press the X on a card to remove it, which returns it to the picker.

Tips for Best Results

• Cities already on the board drop out of the picker, so a country can read as fully added.
• The filter matches city names only, so typing a country name returns nothing.
• Offsets print as decimal hours, so Kathmandu's 5:45 shows as UTC+5.8 rather than +5:45.
• Every reading derives from your device clock, so a machine set wrong makes the whole board wrong.

Why Use WiserWork's World Clock?

Time zones are not a tidy grid: India runs a single offset half an hour off the hour, Nepal a further quarter hour beyond that, and China keeps one clock across a span that would geographically hold five. Reading a real city's current time removes all that arithmetic, including the daylight saving shifts that a fixed offset held in your head quietly gets wrong twice a year. Because the board is saved in your browser, the cities you actually care about are waiting the next time you open the page.

Who Uses the World Clock?

People with family or colleagues abroad, traders and sports fans watching an event start in another country, and anyone who has ever woken a friend at 4 am with a well-meant call. Support and operations teams keep a board of the regions they cover so a handover never has to be worked out from an offset table.

Frequently Asked Questions

Which cities can I add?

120 cities under 96 countries and territories, from Kabul and Algiers through to Harare. Larger countries carry several entries: the United States offers New York, Los Angeles, Chicago, Denver, Anchorage and Honolulu, and Australia offers Sydney, Melbourne, Perth, Brisbane and Adelaide.

Does it update live?

Yes. The whole board, including your local card, is redrawn once a second, so the seconds tick rather than showing a snapshot frozen at the moment the page loaded.

Does it handle daylight saving?

Yes, automatically. Each city is stored as an IANA zone identifier and rendered through the browser's own time zone data, so London moves an hour in spring and Sydney moves the other way in October without you touching anything.

Are my cities remembered?

Yes. The board is written to your browser's local storage under a single key, so it reappears on your next visit. It stays on that device in that browser, and clearing site data removes it.

Why is the offset shown as a decimal?

Offsets are calculated in hours and printed to one decimal place. India's five and a half hours shows as UTC+5.5, and Nepal's five and three quarter hours rounds to UTC+5.8, which is a display convention rather than the real offset.

Can I switch to a 12-hour clock?

No. Every reading, your local card included, is 24-hour with seconds. There is no am and pm toggle.

Why do two of my cities show identical times?

Because they share a zone. Beijing and Shanghai both use Asia/Shanghai, Frankfurt reads from Europe/Berlin, Barcelona from Europe/Madrid, and Mumbai, New Delhi and Bengaluru all use Asia/Kolkata. The identifier is printed on each card so you can see which zone is in play.

Why does a card show a different date from mine?

Because the calendar date genuinely differs across the date line. Each card prints its own weekday and date next to the time, which is the quickest way to notice that your Friday evening is already Saturday in Auckland.

My city is not listed. What now?

Add the nearest city that shares the same offset and daylight saving rules, then check the zone identifier printed on the card to confirm it matches. The list is fixed in the page and cannot be extended from the interface.

Where does the time itself come from?

Your own device clock, converted into each zone. Nothing is fetched from a time server, so if your computer's clock has drifted, every card on the board drifts with it.

Add the handful of cities you genuinely deal with, and the question of what time it is there stops being a calculation you redo every week. The board is waiting on your next visit.