World Clock
This world clock shows the current local time and date for a curated list of cities, updating live every second. Check New York, London, Tokyo, Dubai, Phoenix, Honolulu, and other major locations from the same current instant. Each card includes the offset that applies at that moment, including half-hour offsets and seasonal changes supplied by the browser's time-zone data. Pick one city for the featured clock or scan the list to compare working hours, dates, and day boundaries. The clock uses named IANA zones rather than adding a permanent offset, so places with daylight saving time can change between standard and summer time. It also shows when a city has moved into the previous or next calendar date.
Quick answer
Each clock shows the current local time for that city, updating every second.
Cities around the world
What this tells you
- •Each clock shows the current local time for that city, updating every second.
- •Daylight saving time is handled automatically, so summer and winter offsets are correct.
- •The UTC offset next to each city shows how far ahead or behind Coordinated Universal Time it is.
- •Phoenix and Honolulu use zones without seasonal clock changes, while several other listed cities change offsets according to local rules.
- •Time and date are calculated from one shared instant, so a city may already be on the next date or still on the previous date.
- •Offsets can include minutes, as in Mumbai at UTC+5:30, rather than always being a whole number of hours.
- •The displayed rule depends on the browser's IANA time-zone database and the accuracy of the device clock.
How to Use
- 1Open the tool to see live clocks for major cities.
- 2Pick a city from the list to feature it as the large clock.
- 3Read the local time and date for each city.
- 4Check the UTC offset that applies at the displayed instant instead of assuming the standard winter offset.
- 5Compare the date as well as the hour when arranging an event across the International Date Line or near midnight.
- 6For a future meeting affected by a clock change, use a date-aware time-zone converter and confirm the result close to the event.
How It Works
Formula
local time = current UTC instant + the city's UTC offsetEvery clock begins with the same current epoch timestamp. The browser formats that instant in the city's named IANA time zone, producing its local hour and calendar date. The offset is recovered by comparing those local date-and-time parts with the original UTC instant, then rounded to minutes and formatted as UTC plus or minus hours and minutes. This method handles date rollover and non-whole-hour offsets. It also applies the historical or current daylight saving rule stored by the browser for that zone and instant. A named zone is important because UTC-5 alone cannot tell whether New York should be UTC-5 in winter or UTC-4 in summer.
Calculation note: values are processed in the order shown above, using the current input units.
Worked Examples
What time is it in Arizona when it is noon UTC?
Arizona sits at UTC-7 all year because it does not observe daylight saving, so noon UTC is 5:00 AM in Phoenix.
What time is it in Tokyo when it is noon UTC?
Tokyo is at UTC+9, so it is 9 hours ahead. Noon UTC is 9:00 PM the same day in Tokyo.
Mumbai at noon UTC
Mumbai uses UTC+5:30, so adding five hours and thirty minutes to noon gives 5:30 PM on the same date. This shows why offsets are not always whole hours.
Tokyo crosses into the next date
Tokyo is UTC+9. Adding nine hours to 11:00 PM reaches 8:00 AM on the following calendar date, so both the time and date must be checked.
New York during northern summer
The America/New_York zone observes daylight saving on this date. Its applicable offset is UTC-4, making noon UTC equal to 8:00 AM rather than the 7:00 AM produced by the standard UTC-5 offset.
UTC Offsets for Common Cities
Standard UTC offset for each city. Daylight saving shifts some by one hour in summer.
| City | Time Zone | Standard UTC Offset |
|---|---|---|
| Los Angeles | Pacific | UTC-8 |
| Phoenix (Arizona) | Mountain (no DST) | UTC-7 |
| Chicago | Central | UTC-6 |
| New York | Eastern | UTC-5 |
| Honolulu (Hawaii) | Hawaii (no DST) | UTC-10 |
| London | GMT | UTC+0 |
| Madrid (Spain) | Central European | UTC+1 |
| Dubai | Gulf | UTC+4 |
| Mumbai (India) | India | UTC+5:30 |
| Singapore | Singapore | UTC+8 |
| Tokyo | Japan | UTC+9 |
| Sydney | Eastern Australia | UTC+10 |
Offsets shown are standard time. During daylight saving, zones that observe it move one hour later, so New York becomes UTC-4 and London becomes UTC+1.
Offsets, named zones, and date changes
A UTC offset describes the difference at one instant. A named time zone contains a set of regional rules. New York can use UTC-5 during standard time and UTC-4 during daylight time, while Phoenix remains UTC-7. The city name and date are therefore needed when seasonal rules matter. A permanent offset alone cannot represent those changes.
Daylight saving transitions do not occur everywhere or on one global schedule. Northern and southern locations can change in different months, and many locations do not change at all. Governments can also revise rules. The browser applies the time-zone database installed with the operating system or browser, which is why current software matters.
The same instant can carry different dates around the world. Adding an eastern offset near midnight UTC can move into tomorrow, while subtracting a western offset can move into yesterday. The International Date Line makes this especially visible, but ordinary comparisons between Asia, Europe, and the Americas can also cross a date boundary.
A live clock answers what time it is now. It is not the best tool for guaranteeing a future meeting time because time-zone rules may change and a daylight transition can make a local hour repeat or not occur. For travel, legal deadlines, broadcasts, or operational schedules, save the named zone and full date, then confirm against an authoritative source.
Common mistakes
- Assuming Arizona changes with the rest of Mountain Time. Most of Arizona does not observe daylight saving, so its clock stays at UTC-7 all year.
- Forgetting daylight saving when comparing cities. The gap between two cities can change by an hour when one switches and the other does not.
- Reading the date wrong across the date line. When it is late evening in New York, it may already be the next day in Tokyo and Singapore.
- Treating a current offset as permanent. A city that shows UTC-4 today may show UTC-5 in another season.
- Assuming every seasonal shift is exactly one hour. Rules are jurisdiction-specific and historical changes can differ from common modern patterns.
- Using a city label without checking its actual zone. Regions within one country can follow different rules, and the curated clock represents the listed city only.
- Relying on an incorrect device clock. Every city starts from the same device-supplied instant, so a device error shifts all displays.
Embed this calculator on your site
Drop this single line where you want the calculator to appear. It is responsive, mobile-friendly, resizes automatically, and is free to use with attribution.
<script src="https://calctide.com/embed.js" data-tool="world-clock" async></script>Preview the embed at /embed/world-clock/.