What this world clock does
This tool answers the question that comes up whenever people, meetings, or flights span more than one country: what time is it there right now? Your own local time appears automatically as the first card, and every city you add shows its current time next to it, ticking live and already corrected for that region's daylight saving rules.
It is built for the moments where guessing an offset by hand goes wrong — a colleague in a city that just changed its clocks, a family member on the other side of the date line, or five time zones you need to compare at a glance before booking a call.
How to use it
Four quick steps — most people only ever touch the add-a-city field.
- Your local time appears automatically.The first card reads straight from your device's clock and time zone — nothing to configure.
- Add a city.Choose one from the dropdown and press Add. Its card joins the grid and starts ticking immediately.
- Watch the times update live.Every card updates once a second, already adjusted for that city's current daylight saving status.
- Remove, switch format, or copy.Remove any city with its ×, toggle 12-hour or 24-hour display, or copy the whole list to paste into a message.
How time zones are calculated
Every place on Earth keeps time as an offset from UTC (Coordinated Universal Time) — for example, New York is normally five hours behind UTC, written UTC−5. The clock takes your device's exact moment in time, then applies each city's current offset from the IANA Time Zone Database, the reference dataset built into every modern browser and operating system, to work out that city's local time.
12:00 (UTC−5)London →
17:00 (UTC+0)Dubai →
21:00 (UTC+4)Tokyo →
02:00 next day (UTC+9)Sydney →
03:00 next day (UTC+10, standard time)
Why the offset for a city can change during the year
Many countries observe daylight saving time, shifting their clocks forward by an hour for part of the year and back again later. New York, for instance, moves from UTC−5 to UTC−4 in spring. Because the shift happens on different dates in the Northern and Southern hemispheres — and some places, like Dubai and Tokyo, do not observe it at all — a city's offset from UTC is not fixed all year. The clock above reads the live offset for each city automatically, so it is always current, whether or not that region is currently observing daylight saving.
Half-hour and quarter-hour zones
Not every zone sits on a whole hour. India (UTC+5:30) and Nepal (UTC+5:45) are two well-known examples of countries that chose an offset in half-hour or quarter-hour steps rather than a full hour from UTC.
Quick examples
What each city's clock reads when it is 12:00 noon UTC, using each city's standard (non-daylight-saving) offset.
| City | Standard UTC offset | Time at 12:00 UTC |
|---|---|---|
| New York | UTC−5 | 07:00 |
| London | UTC+0 | 12:00 |
| Paris | UTC+1 | 13:00 |
| Dubai | UTC+4 | 16:00 |
| Mumbai | UTC+5:30 | 17:30 |
| Singapore | UTC+8 | 20:00 |
| Tokyo | UTC+9 | 21:00 |
| Sydney | UTC+10 | 22:00 |
Need to schedule a call across several of these zones rather than just read them? The meeting planner lines up working hours across every city you pick, and the UTC converter converts a single time to and from UTC.
Who uses it, and for what
- Remote teams & distributed companies checking who is online, or awake, before sending a message or booking a call.
- Travelers tracking the time back home while abroad, or checking a connecting flight's local arrival time.
- Traders & analysts watching market opening hours in New York, London, and Tokyo at once.
- Families & friends abroad working out a decent hour to call someone on another continent.
- Gamers & event organizers converting a launch time or match start into every player's local time.
If you only need to convert one specific time rather than watch several cities live, the GMT converter or UTC converter is the faster tool for that single lookup.
Frequently asked questions
What is a world clock and how does it work?
A world clock shows the current time in several cities at the same moment. This tool reads the exact time from your device and, for each city you add, applies that city's UTC offset from the IANA time zone database to display its local time — all updating live, once a second.
Does this world clock account for daylight saving time?
Yes. Each city's offset is calculated through your browser's built-in time zone data, which follows the IANA Time Zone Database and already knows every region's daylight saving rules and change dates, so no manual adjustment is needed.
How accurate is the time shown?
It is only as accurate as your device's system clock, which is typically synced to internet time servers automatically. The tool itself performs no rounding beyond whole seconds.
Can I add more than one city from the same country?
Yes. There is no restriction on region or country — add New York and Los Angeles together, for example, to compare two U.S. time zones side by side.
Why do some cities differ by 30 or 45 minutes instead of a whole hour?
Not every time zone sits on a whole-hour boundary. India (UTC+5:30) and Nepal (UTC+5:45) are common examples of countries that chose a half-hour or quarter-hour offset from UTC rather than a full hour.
Is my data stored or shared anywhere?
No. The clock runs entirely in your browser using your device's own clock and time zone data. Nothing is sent to a server or stored once you leave the page.
Accuracy & sources
Each city's time is produced by taking your device's exact current moment and applying that city's live UTC offset, as supplied by your browser's built-in time zone engine — no server round-trip and no manual offset table to go stale. Every worked example and offset shown on this page has been independently verified by hand.
Time zone and daylight saving data follow the IANA Time Zone Database, the reference dataset that browsers and operating systems use to track every region's current offset and change dates. Written and reviewed by Fletcher Langley, and re-checked whenever the tool changes — last reviewed August 2026.
