UTC is a reference, not another city
Coordinated Universal Time, written UTC, lets people describe the same instant without relying on a local clock. A UTC offset tells you the difference between a local reading and that reference at a particular date. UTC−07:00 means seven hours behind UTC; UTC+09:00 means nine hours ahead. The sign is easy to reverse mentally, so write both the date and the zone when sending an invitation.
An offset alone is not a long-term time-zone rule. Los Angeles may have a different offset in winter than in summer. A recurring meeting that is always at 9:00 a.m. in Los Angeles should normally be associated with that named zone in a calendar, rather than with a permanently fixed subtraction from UTC. That lets the calendar apply the rules for each occurrence.
Why we use IANA zone names
The clocks above use America/New_York, America/Los_Angeles, Europe/London, Asia/Tokyo, and Australia/Sydney. These are identifiers from the IANA time-zone system. The browser’s date formatter uses its available zone data to turn one device timestamp into the five local readings. No city-by-city time server is contacted by this world-clock tool.
The IANA Time Zone Database is updated as governments change civil-time rules. An older browser or operating system can therefore contain older information. Updating your device software matters particularly when a country announces a recent change. The city name identifies a set of rules; it does not mean the site has detected where you live.
Daylight saving can change meeting overlaps
Different regions change clocks on different dates, and some do not change at all. In the weeks between two regions’ transitions, their usual time difference may temporarily change. A meeting you remember as “eight hours apart” can be wrong on a specific date. The live display answers what time it is now; it is not a future-date meeting converter.
For a future appointment, use a calendar that supports named time zones and enter the actual date. Ask invitees to confirm the local time shown by their calendar. Avoid abbreviations such as CST on their own, because abbreviations can refer to more than one region. A city plus a named zone and a full date is clearer, especially when arranging travel or a call across the International Date Line.
A worked meeting-overlap example
The table below is a fixed example for September 24, 2026, not a live availability display. It compares a one-hour meeting from 16:00 to 17:00 UTC. The example uses the zones listed above. Actual working hours vary by person; a time that fits a conventional workday is not evidence that somebody is available.
One meeting, five local dates and times| City | Local interval | Planning consideration |
|---|
| Los Angeles | Sep 24, 09:00–10:00 | Morning |
|---|
| New York | Sep 24, 12:00–13:00 | Could overlap lunch |
|---|
| London | Sep 24, 17:00–18:00 | End of day |
|---|
| Tokyo | Sep 25, 01:00–02:00 | Overnight; seek another arrangement |
|---|
| Sydney | Sep 25, 02:00–03:00 | Overnight; seek another arrangement |
|---|
This example shows why one “perfect” global meeting slot may not exist. A practical alternative is two shorter regional meetings, an asynchronous update, or rotating inconvenient hours fairly. Before moving the meeting earlier, calculate the effect on the westernmost participant as well as the easternmost one. A small adjustment for one person can cross midnight for another.
Keep the date attached to the time
The same instant can fall on Thursday in one city and Friday in another. The compact live city rows above show the time of day, so do not infer the local calendar date from those digits alone. Check the complete date in your invitation. “Tomorrow at nine” depends on where the reader is and when they read the message; “September 25 at 09:00 in Asia/Tokyo” gives them an explicit reference.
When travelling, check the zone assigned to your device after arrival. The large local clock follows your browser’s device settings, while the five named-city rows continue to use their explicit zones. A manually configured device zone can make the large reading look unexpected without changing the named-city conversions. Incorrect device time affects all the readings because they share the same underlying timestamp.
A reliable handoff to your calendar
- Choose the organizer’s named zone and the actual event date.
- Check each participant’s local date, start time, and end time.
- Send a calendar invitation with the zone included, rather than only a screenshot of the current clocks.
- Recheck recurring meetings around clock-change dates and when participants travel.
- Set a reminder on a device you expect to have available.
The homepage alarm is a browser reminder using your device’s local time. It does not import this table or create an international calendar invitation. After comparing cities, convert the intended event to your own local date and time before setting that alarm. Keep a backup reminder for important appointments because a browser cannot wake a sleeping device.
Reading and privacy limits
The world-clock display uses JavaScript and updates approximately once per second. A busy or backgrounded browser may update less frequently. It is suitable for everyday comparisons, not for checking the millisecond accuracy of a network time service. If a reading seems wrong, first check the device clock and zone, then update the browser and compare the named city with the event organizer.
The five zone conversions happen locally. Optional site analytics, when enabled through your privacy choices, are a separate service described in the Privacy Policy. Changing the weather city on the homepage does not change the five cities on this page. See the browser date-formatting reference for the API used to display these readings.
By Ed Vaquerano · Updated September 24, 2026 · Editorial policy