One moment in several cities
Choose a city, a date, and a time. That choice becomes one moment, and you can add up to eight other cities that show the same moment. A missing or repeated local time waits for you to choose. The city list is not saved.
Loading the current time in the source city.
Compare several cities
The reference date and time are resolved once. Every city shows that same moment.
Loading the current time in the source city.
One chosen time, read in each city
Pick the reference city, the date, and the time. Convert resolves that wall-clock time to one moment, and every added city shows that moment. The city board is the current time, not a time you type. The clock on this device is only this device.
Set the moment, then add cities
- Search for the reference city, country, or time zone name, such as America/New_York.
- Set the date and time. Those fields belong to the reference city. They open on the current moment in that city, and you can change them.
- Add the other cities. Each one shows the same moment. A city already in the list is not added again.
- If daylight saving makes the reference time missing or repeated, choose the occurrence before any city card uses that moment.
The offset belongs to the moment
A named zone is a region with rules, not a fixed number of hours from UTC. New York uses America/New_York, London uses Europe/London, and Seoul uses Asia/Seoul. The offset on that name can change when daylight saving starts or ends. Adding a fixed number of hours goes stale as soon as one side changes. This page keeps the city and its IANA name, resolves the clock time you chose to one instant, and formats that instant in each city.
A missing time and a repeated time
When a region moves clocks forward, a range of local times never occurs. A jump from 2:00 to 3:00 skips the times in between, so 2:30 cannot be used until you pick a time that exists. When clocks move back, a range of local times occurs twice, once before the change and once after, with different UTC offsets. The page lists both and waits. It does not guess. Once you choose, each other city has one local representation of that instant.
A spring skip is not always one hour. Some regions move the clock by 30 minutes. After a missing time, the suggestion is the next local time that exists, searched forward up to three hours. Applying it fills the reference time. It does not change the time silently.
A fall repeat is labeled as the first occurrence and the second occurrence, each with the UTC offset that distinguishes it. Choose the earlier offset for the time before clocks fall back. Choose the later offset for the time after clocks fall back.
Named zones, not a frozen offset
New York is not always UTC−5. America/New_York is normally UTC−5 in winter and UTC−4 in summer. London can be UTC+0 in winter and UTC+1 in summer. Asia/Seoul stays at UTC+9. Offsets are not always whole hours: Asia/Kolkata is UTC+5:30, and Asia/Kathmandu is UTC+5:45. The offset on a result is calculated for the converted instant. It is not a number stored on the city.
One call, several clocks
- Put the meeting time in the city where someone will dial, then read that moment in the cities where the others will be.
- Take a departure in the departure city's local time and see the clock time where you will arrive.
- Check whether a teammate's afternoon is still your morning before you send something that needs a reply the same day.
- Read an event listed in one city and see that moment in the city whose calendar you keep.
What this comparison leaves out
- The page does not read your location or your IP address. The first cities follow the language of this page.
- The date and time fields open on the current moment in the reference city, read after the page loads. They are not a clock frozen when the site was built. The comparison uses the date and time you leave in those fields.
- Years run from 1900 through 2100. Browser time zone data is not a promise of perfect historical rules before modern time zone standards.
- The page does not save a history of the dates and times you convert, and it does not put them in the page address.
- There is one converter page. It does not publish a separate page or a share link for each city or each pair of cities.
- Eight comparison cities is the cap, besides the reference city. A missing or repeated reference time is not filled in automatically. The city list is not saved.
Questions about one shared moment
How do I compare one time in several cities?
Set the reference city, date, and time. Add the other cities. Each card shows that same moment, after a missing or repeated reference time has been chosen.
How many cities can share that moment?
Eight comparison cities, besides the reference city. A city already in the list is not added again. The list is not saved.
What if the local time does not exist?
When clocks jump forward, a range of local times is skipped. A skipped time is not converted until you choose a time that exists. The suggestion looks forward up to three hours.
What if the same local time happens twice?
When clocks move back, the page lists both occurrences and their UTC offsets. The comparison waits until you choose one.
Which years can I enter?
Years run from 1900 through 2100. The offset comes from the browser's time zone data for that moment, not from a number stored on the city.
Does this page use my location to pick the first cities?
No. It does not read your location or your IP address. The first cities follow the language of this page.
Is the city list still there tomorrow?
No. The comparison cities, the date, and the time are not saved, and they are not put in the page address.
How is this different from a board of current times?
This page uses the date and time you set. A board of current times is the other page. A city here can fall on the previous day, the same day, or the next day for that one moment.