Convert time between any two time zones and view the equivalent time across major cities worldwide.
| Zone | From (input) | UTC Offset |
|---|---|---|
| New York (ET) | Tue, Oct 6, 2026, 06:54:00 PM | UTC-04:00 |
| London (GMT/BST) | Tue, Oct 6, 2026, 11:54:00 PM | UTC+01:00 |
Equivalent time in major cities for the entered time.
| City / Zone | Time | Offset |
|---|---|---|
| UTC | Tue, Oct 6, 2026, 10:54:00 PM | UTC+00:00 |
| London (GMT/BST) | Tue, Oct 6, 2026, 11:54:00 PM | UTC+01:00 |
| Paris / Berlin (CET) | Wed, Oct 7, 2026, 12:54:00 AM | UTC+02:00 |
| Helsinki (EET) | Wed, Oct 7, 2026, 01:54:00 AM | UTC+03:00 |
| Moscow (MSK) | Wed, Oct 7, 2026, 01:54:00 AM | UTC+03:00 |
| Dubai (GST) | Wed, Oct 7, 2026, 02:54:00 AM | UTC+04:00 |
| Karachi (PKT) | Wed, Oct 7, 2026, 03:54:00 AM | UTC+05:00 |
| Kolkata (IST) | Wed, Oct 7, 2026, 04:24:00 AM | UTC+05:30 |
| Dhaka (BST) | Wed, Oct 7, 2026, 04:54:00 AM | UTC+06:00 |
| Bangkok (ICT) | Wed, Oct 7, 2026, 05:54:00 AM | UTC+07:00 |
| Singapore / Beijing (SGT) | Wed, Oct 7, 2026, 06:54:00 AM | UTC+08:00 |
| Tokyo (JST) | Wed, Oct 7, 2026, 07:54:00 AM | UTC+09:00 |
| Sydney (AEST) | Wed, Oct 7, 2026, 09:54:00 AM | UTC+11:00 |
| Auckland (NZST) | Wed, Oct 7, 2026, 11:54:00 AM | UTC+13:00 |
| Honolulu (HST) | Tue, Oct 6, 2026, 12:54:00 PM | UTC-10:00 |
| Los Angeles (PT) | Tue, Oct 6, 2026, 03:54:00 PM | UTC-07:00 |
| Denver (MT) | Tue, Oct 6, 2026, 04:54:00 PM | UTC-06:00 |
| Chicago (CT) | Tue, Oct 6, 2026, 05:54:00 PM | UTC-05:00 |
| New York (ET) | Tue, Oct 6, 2026, 06:54:00 PM | UTC-04:00 |
| São Paulo (BRT) | Tue, Oct 6, 2026, 07:54:00 PM | UTC-03:00 |
On 18 November 1883, railroads across North America moved onto four standard zones, ending a patchwork of local sun times that had made timetables guesswork. The lesson stuck: a clock reading means nothing without a zone attached to it. Converting between zones is still just an offset subtraction, but the offsets themselves change twice a year in many places, and that is where most scheduling mistakes come from.
Start with 9:00 AM on Sunday 15 March 2026 in New York. Converted, that is 1:00 PM in London, 6:00 PM in Karachi, 6:30 PM in Kolkata and 10:00 PM in Tokyo. Notice that London is four hours ahead, not the usual five.
Step one is finding the universal moment: UTC = local time - offset of the From zone. New York moved to daylight time on 8 March 2026, so its offset that day is UTC-4, and 9:00 + 4 hours = 13:00 UTC. The page does this by guessing that your entry is UTC, reading back what clock that instant shows in the From zone, and correcting by the difference, three times over.
Step two is the target clock: local time = UTC + offset of the To zone. London does not switch to summer time until 29 March, so on the 15th it sits at UTC+0 and 13:00 UTC is 1:00 PM. Karachi at +5 gives 18:00, Kolkata at +5:30 gives 18:30, Tokyo at +9 gives 22:00. None of those places use daylight saving.
The gap between any two zones is offset(To) - offset(From), so it can change with the date. Two weeks later, 1 April, the same 9:00 AM in New York is 2:00 PM in London, back to five hours. The four-hour window also appears from late October until the first Sunday in November. The result shows the weekday and date too, so 9:00 PM in New York on that Sunday reads as 10:00 AM Monday in Tokyo. Nothing is rounded; minutes are exact.
The United States and the United Kingdom change their clocks on different weekends. US clocks move forward on the second Sunday of March, UK clocks on the last Sunday, so for about three weeks the gap shrinks. A similar short window occurs again in autumn.
Trust the converted clock time. The UTC offset labels are read at the moment you open the page, not for the date you entered, so a date in a different season can show a label that is an hour out. The converted time itself uses the entered date.
Times like 2:30 AM on 8 March 2026 in New York never existed. The page reads such a time with the old offset, so it comes out an hour later than the wall clock would suggest. A repeated time, such as 1:30 AM on 1 November 2026, is read as the first of its two occurrences. Avoid scheduling inside those hours.
The list has 20 zones and Arizona is not among them. Phoenix has no daylight saving and sits at UTC-7, so in summer it matches Los Angeles and in winter it matches Denver. Pick UTC and add the offset by hand for anywhere else.
For the clock, yes. Both are UTC+8 all year with no daylight saving, which is why they share one entry. Conversions to either will match.