World Clock: Current Time Around the World
Live local time in Paris, London, New York, Tokyo and your own cities, with UTC offset, time difference, sunrise and sunset, and the next clock change.
Related tools
All Dates & time tools →Before you call a colleague in Singapore or family in Montreal, the question is simple: is it day or night there, and what time is it exactly? This page answers it for all your cities at once. The top card follows your own time zone, as your browser reports it; below it, fourteen cities appear by default, and you can keep up to thirty, in whatever order suits you. Each card ticks over every second and gives the date of that city's next clock change, which matters because New York and London don't switch on the same Sunday. To line up a specific time on a chosen date, the time zone converter is the better fit.
How to use it
- Look at the “Your local time” card at the top: it shows the time zone your browser reports, with the country and the IANA zone name.
- Type a city in “Add a city” (“Londres” finds London too); each suggestion shows its country and UTC offset. Move through them with ↑ ↓ and press Enter, or click the one you want.
- Reorder your cards with the ↑ and ↓ buttons (Move up, Move down) and drop the ones you no longer need with × (Remove).
- Pick a “Time format”: Auto follows the page language, 12h shows AM and PM, 24h counts up to 23:59.
- Read each card: local time and date, UTC offset, the gap “from your time”, the Day or Night badge, sunrise and sunset, and the next clock change on the last line.
- To return to the fourteen starting cities, click “Restore the default list”.
How the clock works out each card
The time on screen comes from your device clock, read again at every full second. For each city, your browser applies the rules of the IANA time zone database to that instant through the Intl API: that gives the local time, the date and the offset, shown as UTC+5:45 for Kathmandu, whose offset isn't a whole number of hours. The gap “from your time” is the difference between that offset and your own zone's at the same instant, and an abbreviation such as EDT is added only when your browser knows a readable one in the page language.
Sunrise and sunset use NOAA's solar formulas (declination, equation of time, atmospheric refraction included) for the coordinates of the city on the card, with the offset in force at noon that day. The Day or Night badge compares the current instant with those actual times rather than a fixed 6 a.m. to 8 p.m. window, so it stays on Day when the sun sets after midnight. The calculation runs again only when the local date changes.
The next clock change is looked up in the same database: the offset is compared week by week over a 400-day horizon, then the week in which it changes is halved repeatedly until the exact minute is found. The card gives the date, the time clocks showed just before the jump and its size, such as −1 h; a zone with nothing scheduled says so in words. Your own time zone is read again whenever you come back to the tab.
When a world clock earns its place
- A team spread across New York, London and Singapore: the time and the Day or Night badge on each card show at a glance who a call would reach in the middle of the night.
- Calling family on the other side of the world: the full date, weekday included, and the “+1 day” badge remind you that Sydney or Tokyo may already be into tomorrow.
- Planning a trip: the sunrise and sunset times of your destination help you shape the first day, for instance in Reykjavík in June.
- Recurring meetings with Europe: in March and around the end of October, the clock-change lines on the New York and London cards show the days when the usual gap stops holding.
- Working with India or Nepal: half-hour and quarter-hour offsets appear as they are, with the exact gap from your time.
- Customer support across continents: keep your cities in the order of your queues; the list stays in your browser from one visit to the next.
The clock on specific dates
Values calculated by the tool's own engine for fixed dates, as the cards show them if your browser is set to New York time and you open the page that day.
- The gap with London shifts twice a year: the London card reads “+5 h from your time” on January 15, 2026, but “+4 h” between March 8 and March 29, 2026, and again between October 25 and November 1, 2026, because the US moves its clocks forward three weeks before the UK and back one week after it.
- On September 14, 2026, the New York card says “Clocks go back on Nov 1 at 2:00 AM (−1 h)”, London “Clocks go back on Oct 25 at 2:00 AM (−1 h)”, Sydney “Clocks go forward on Oct 4 at 2:00 AM (+1 h)”, and Phoenix and Tokyo “No clock change scheduled”.
- On June 21, 2026, New York shows “Sunrise 5:25 AM” and “Sunset 8:31 PM” (7:17 AM and 4:32 PM on December 21); the same day, Reykjavík shows “Sunrise 2:55 AM” and “Sunset 12:03 AM (next day)”.
- On Saturday, September 19, 2026, at 10:00 PM in New York, the Sydney card reads 12:00 PM, “Sunday, September 20” and “+1 day”. The gap also changes with the seasons: +16 h on January 15, 2026, +14 h on July 15, 2026, since the two cities observe daylight saving time at opposite times of year.
What the world clock can't guarantee
- The time comes from your device clock: if it's wrong, every card is wrong by the same amount. The tool doesn't sync with any time server.
- Time zone rules are those of the IANA database built into your browser. A country that changes its daylight saving rules at short notice may not be in it yet, especially in an older browser.
- Sunrise and sunset are approximate to within a few minutes and calculated for the reference city's coordinates, not your position; cities outside the built-in list show none.
- In a background tab or on a sleeping device the display can freeze; it picks up the real time as soon as the page is visible again. The tool doesn't keep your screen on.
- Thirty cities at most besides your local card, and the search leaves out smaller towns: pick a city in the same time zone instead.
Privacy
Processed in your browserEverything is calculated in your browser: times, offsets, sun times and clock changes need no network request. Your city list and time format stay in this browser's local storage (the allin_tools key) and are sent nowhere. As on every page of the site, an audience measurement goes to OneKitly with the page address, language, device type and a random session ID that is deleted when the tab closes; the tool adds a single “tool used” event the first time you add or remove a city, with no city name and no time.
Frequently asked questions
Why does the gap with London drop from 5 to 4 hours on some days?
Because the US and the UK don't change their clocks on the same Sunday. In spring, New York moves forward three weeks before London; in autumn, London falls back a week before New York. During those periods, about four weeks a year, the London card shows +4 h instead of +5 h. The clock reads both zones' real offsets every second, so the gap updates on its own at the exact moment of the change.
How does the clock know my time zone?
It reads the time zone your browser reports, which usually follows your system settings, without asking for your location. That zone is read again whenever you come back to the tab: if your laptop switched time zones after a flight, the local card follows without a reload. If the browser reports none, the card says “Time zone not detected” and the gaps “from your time” disappear.
Why does my local card say Los Angeles when I'm in Seattle?
Your browser only reports a time zone, America/Los_Angeles, which covers the whole US West Coast. The local card shows that zone's reference city from the built-in list: the time is the same everywhere in the zone, but the sunrise and sunset are those of Los Angeles, not of where you are. If your zone has no reference city, the card carries the zone's name and shows no sun times.
Are my cities kept when I close the page?
Yes, in this browser: the list, its order and the time format are saved in local storage under the allin_tools key. Nothing is tied to an account or synced, so on another device or browser you'll see the fourteen default cities. In a private window the list goes when the window closes; if storage is blocked, the cards follow your changes only while the page stays open.
Why do some cities show no sunrise or sunset?
Sun times need coordinates, and only the 90 or so cities of the built-in list have them. Other cities the search finds, such as Boston, Seattle or Houston, bring only their time zone: their card shows the time, date, offset and next clock change, without sunrise, sunset or the Day or Night badge. Smaller places such as Boise aren't in the search at all; add Denver, which keeps the same time.
Is the time on the cards accurate to the second?
It's as accurate as your device's clock, which supplies it: the tool doesn't query any time server. Most computers and phones set their clocks automatically; if yours is off, every card is off by the same amount. In a background tab the browser may slow down updates, but when you come back the display picks up the real time again, with no delay carried over.
What does “No clock change scheduled” mean?
It means your browser's time zone database has no offset change for that zone in the next 400 days. That's the case for Tokyo, Phoenix and Honolulu, which keep the same time all year. If a country adopts or drops daylight saving time, the card only reflects it once your browser has been updated with the new rules.