World Clock

More Time & Clocks Tools

Pomodoro Timer

Stay focused with timed work sessions and breaks — the classic Pomodoro Technique, running entirely in your browser.

Time Zone Converter

Convert a specific date and time between any two time zones, with full daylight saving awareness — perfect for scheduling cross-border calls.

OS

Online Stopwatch

A precise stopwatch with lap timing — start, stop, record split times and reset, all running in your browser.

CT

Countdown Timer

Count down the days, hours, minutes and seconds to any future date or event — a live countdown running in your browser.

How to Use World Clock

View a grid of live-updating clocks showing the current time in cities across the globe. Each card shows the local time (HH:MM:SS), day of the week, full date, and time zone. Add or remove cities to build your own dashboard.

About World Clock

A world clock is the simplest possible answer to 'what time is it in...' — instead of converting one specific future datetime (which the Time Zone Converter does best), a world clock shows you the live, right-now time in multiple cities simultaneously, so you can glance at a single screen and see that it is 09:00 in New York, 14:00 in London, 22:00 in Tokyo, and 23:00 in Sydney, all at the same moment. This is useful for distributed teams, international clients, or simply being aware of what part of the working day your contacts in another region are currently in before you write that email or schedule that meeting. The World Clock on this page shows six cities by default — New York, London, Tokyo, Sydney, Dubai and Los Angeles — chosen to give a spread across major global time zones and business centres. Each city card updates every second using JavaScript's setInterval, which means the seconds ticker moves visibly, and the display is accurate to within roughly one tick of your browser's internal clock. The time shown for each city uses the IANA time zone identifier (e.g., 'America/New_York', 'Europe/London', 'Asia/Tokyo') and your browser's Intl.DateTimeFormat engine to display the local time correctly, including whether that city is currently on standard time or daylight saving time on today's date. The city list is a starting point, not a fixed permanent set — the add/remove controls let you customise the grid to show exactly the cities relevant to you and hide the ones you do not need, building a personal dashboard of time zones you work with regularly rather than a generic global overview. And like every tool in this category, it runs entirely in your browser: the clocks tick using your local device clock with time zone math applied, not by querying an external time server, so there is no data transmitted and no dependency on an internet connection once the page has loaded. A practical note: the accuracy of the displayed times depends on how accurately your device's system clock is set. Most modern devices synchronise their clock automatically with internet time servers, so this is usually accurate to within a second or two. The per-second display resolution is for the visual ticking and the immediacy of seeing a 'live' clock — not a claim of sub-second precision.

Details & Tips

How the World Clock works: • Each city card displays: city name and country, current local time (HH:MM:SS, 24-hour format), day of the week, full date (e.g., 'Wednesday, 15 July 2026'), and the IANA time zone identifier. • Times are calculated using Intl.DateTimeFormat with the city's IANA time zone, which automatically applies the correct UTC offset and daylight saving rules for today's date. • The display updates every second using setInterval, so the seconds ticker is visibly live. Default cities (6): • New York — America/New_York (UTC−5 / UTC−4 DST) • London — Europe/London (UTC+0 / UTC+1 DST) • Tokyo — Asia/Tokyo (UTC+9, no DST) • Sydney — Australia/Sydney (UTC+10 / UTC+11 DST) • Dubai — Asia/Dubai (UTC+4, no DST) • Los Angeles — America/Los_Angeles (UTC−8 / UTC−7 DST) Additional cities available (pre-configured, toggle on/off): • Chicago, Denver, Toronto, Mexico City, Sao Paulo, Buenos Aires, Paris, Berlin, Moscow, Istanbul, Mumbai, Shanghai, Singapore, Seoul, Auckland Edge cases handled: • Double-click or rapid add/remove: the toggling is idempotent — adding a city already in the grid does nothing; removing the last city shows a 'no cities selected' placeholder. • Browser tab in background: setInterval may be throttled but catches up when you return — the display will jump forward rather than freezing, showing the correct current time. • DST transitions: on a day when clocks spring forward or fall back (e.g., a 2 AM→3 AM leap in spring), the display shows the local time as it currently is, reflecting that the offset has changed. It does not show both before-and-after times simultaneously. • The grid is fully responsive — on narrow screens the cards stack in a single column; on wide screens they arrange in 2–4 columns.

Frequently Asked Questions

How often does the World Clock update?

Every second — the seconds display ticks visibly using a JavaScript setInterval loop. Each tick recalculates the local time for every visible city using your browser's Intl.DateTimeFormat API and the city's IANA time zone.

Does the World Clock show daylight saving time correctly?

Yes. Each city's time is displayed using its full IANA time zone (e.g., America/New_York rather than just UTC−5), so the browser automatically applies the correct offset for today's date, including whether DST is currently in effect.

Can I add cities that are not in the default list?

The current version includes 21 pre-configured cities covering major global time zones. You can toggle any of these on or off using the checkboxes to build your own dashboard — cities not in the pre-configured list cannot be added as free-text input in this version.

What happens if my device clock is wrong?

The World Clock uses your device's system clock as its reference, applying time zone offsets to it. If your system clock is wrong, all displayed city times will be wrong by the same offset. Most modern devices sync their clock automatically, so this is rarely an issue.

Why does Tokyo show the same offset all year but London changes?

Japan does not observe daylight saving time — Asia/Tokyo is UTC+9 all year. The UK observes British Summer Time (UTC+1) from late March to late October and Greenwich Mean Time (UTC+0) the rest of the year. The World Clock applies the correct rule for each zone automatically.

Does the clock work offline?

Yes, once the page has loaded. The clocks tick using JavaScript running entirely in your browser with no server round-trip or external time server query — no internet connection is needed for the display to keep updating.

Why does the clock show 24-hour time not 12-hour AM/PM?

The World Clock uses 24-hour format (14:00 rather than 2:00 PM) to eliminate ambiguity between time zones — a 24-hour display makes it immediately clear whether a time is morning or afternoon without needing to mentally assign AM/PM to a city you may not be familiar with.

Can I see the date as well as the time?

Yes. Each city card shows the full date (day of the week, day, month and year) below the time — this is especially useful for cities across the International Date Line, where the date may differ from yours.

Is any data sent to a server while the clocks are running?

No. The World Clock runs entirely in your browser using JavaScript and the Intl API — nothing about which cities you are viewing or what times are displayed is transmitted, logged, or stored.

What is the difference between the World Clock and the Time Zone Converter?

The World Clock shows the live current time right now in multiple cities, updated each second. The Time Zone Converter takes a specific date and time you choose and tells you what the clock reads in another zone at that exact moment — it is for planning a specific future or past moment, not for seeing what time it is right now.

How does the clock handle cities in half-hour time zones like India?

Cities with fractional UTC offsets (e.g., India at UTC+5:30, Nepal at UTC+5:45) display their local time correctly — the Intl.DateTimeFormat API handles fractional offsets the same way it handles whole-hour offsets.