Skip to content
thecalculatorstudio

Time Zone Converter: What Time Is It There?

Choose the place and the time you start from, add the places you want to compare, and the page shows the local time, date and UTC offset in each, with daylight saving applied for that date.

Last reviewed

Convert to

Working out the times in your browser…

What this converter does

Pick the place and the time you are starting from, add up to eight places to compare, and the page shows the local time, the date, and the offset from UTC in each of them. If you leave the date blank, it uses today in the place you start from. The Use the current time button fills in the date and time right now.

The result is for the date you choose, not for today. That matters because the gap between two places can change during the year, as the next section explains.

How a time zone conversion works

Every place keeps its clocks a fixed number of hours and minutes away from UTC, Coordinated Universal Time. That distance is the UTC offset. New York is UTC-5 in winter and Karachi is UTC+5 all year.

To convert, the page does three steps:

  1. Turn the local time you typed into one exact moment, by subtracting the starting place’s offset on that date.
  2. Add each destination’s offset on that same date to the moment.
  3. Read off the local clock and calendar date, which may be the day before or the day after.

Worked example. 12:00 in New York on Thursday 15 January 2026. New York is at UTC-5, so the moment is 12:00 + 5 hours = 17:00 UTC. Then add each place’s offset:

Place Offset Local time Date
London UTC+0 17:00 Thu 15 Jan
Karachi UTC+5 22:00 Thu 15 Jan
Kolkata UTC+5:30 22:30 Thu 15 Jan
Kathmandu UTC+5:45 22:45 Thu 15 Jan
Tokyo UTC+9 02:00 Fri 16 Jan
Sydney UTC+11 04:00 Fri 16 Jan
Honolulu UTC-10 07:00 Thu 15 Jan

Tokyo and Sydney are already into Friday. The converter marks those rows “next day”, and a place behind the starting time as “previous day”, so you cannot miss it.

Daylight saving and why the date matters

Many places move their clocks by an hour for part of the year. The United States, for example, starts daylight saving time at 2:00 a.m. on the second Sunday of March and ends it at 2:00 a.m. on the first Sunday of November. Because places change on different dates, and the southern hemisphere moves the other way, the gap between two cities is not constant.

Take the same 12:00 in New York in July (15 July 2026). New York is then at UTC-4, so the moment is 16:00 UTC. London, on summer time at UTC+1, shows 17:00, and Sydney, on winter time at UTC+10, shows 02:00 the next day. In January the same 12:00 in New York was 04:00 in Sydney. The gap between the two cities went from 16 hours in January to 14 in July.

A time that does not exist

When the clocks go forward, an hour is skipped. In the United States in 2026 the clocks jump from 2:00 to 3:00 on 8 March. So 2:30 on that morning does not exist in New York, and the converter says so instead of picking a time for you. One minute apart, 01:59 is 06:59 UTC and 03:00 is 07:00 UTC.

A time that happens twice

When the clocks go back, an hour repeats. On 1 November 2026, 1:30 in New York happens twice: first at UTC-4, which is 05:30 UTC, and an hour later at UTC-5, which is 06:30 UTC. The converter uses the earlier one and shows a note. If you meant the later one, move the time on by an hour.

Reference: offsets in January and July 2026

Place 15 January 15 July
UTC +0:00 +0:00
Honolulu -10:00 -10:00
Los Angeles -8:00 -7:00
Denver -7:00 -6:00
Phoenix -7:00 -7:00
Chicago -6:00 -5:00
New York -5:00 -4:00
London +0:00 +1:00
Paris +1:00 +2:00
Dubai +4:00 +4:00
Karachi +5:00 +5:00
Kolkata +5:30 +5:30
Kathmandu +5:45 +5:45
Tokyo +9:00 +9:00
Sydney +11:00 +10:00
Auckland +13:00 +12:00

Phoenix keeps the same offset all year, which is why it matches Denver in winter and Los Angeles in summer.

Where the rules come from

The converter does not carry its own list of rules. It asks your browser for the offset of each place on the date you chose, and the browser answers from the IANA Time Zone Database, the shared record of local time that operating systems and software use. It is updated several times a year because governments change their rules, often with little notice. For example, release 2026e of 29 September 2026 notes that Manitoba moves to a permanent UTC-5 on 31 October 2026.

Two things follow. A device with an out-of-date system can give an out-of-date answer for a recent rule change. And a conversion for a date years away is only as good as today’s rules. For that reason the page works for the years 1980 to 2100.

Planning a call across time zones

  • Check the date as well as the time. A 09:00 call in Tokyo is the previous evening in New York.
  • Convert on the day of the call, not from a rule of thumb, when it falls near a clock change. Two cities can be an hour closer or further apart for a few weeks each spring and autumn.
  • Write the zone and the date when you invite people, such as “17:00 UTC, Thursday 15 January”.

Frequently asked questions

How does the converter handle daylight saving?

It looks up the UTC offset of each place on the date you chose, not today. 12:00 in New York on 15 January is 04:00 the next day in Sydney (UTC+11); on 15 July the same 12:00 is 02:00 the next day (UTC+10), because Sydney is on winter time and New York on summer time.

Why does a time show as not existing?

When clocks go forward, an hour is skipped. In the United States in 2026 the clocks jump from 2:00 to 3:00 on 8 March, so 2:30 that morning never happens in New York. The converter says so instead of guessing; choose a time outside the skipped hour.

What if the time happens twice?

When clocks go back, an hour repeats. On 1 November 2026 in New York, 1:30 occurs twice, once at UTC-4 and once an hour later at UTC-5. The converter uses the earlier one and tells you that the time was repeated.

Does it use my computer's clock?

Only for the "Use the current time" button and for a blank date, which means today in the place you start from. Every other result comes from the date and time you type and the time zone rules built into your browser.

Why are some offsets not whole hours?

Several places keep time at a half or quarter hour from UTC. Kolkata is UTC+5:30, Kathmandu is UTC+5:45 and Adelaide is UTC+10:30 in January. When it is 17:00 UTC, it is 22:30 in Kolkata and 22:45 in Kathmandu.

Why only 1980 to 2100?

In the past some places used offsets with seconds in them, and far in the future governments may change their rules, so a result for 2090 only reflects the rules known today. The converter stays within the range where offsets are whole minutes and the database is dependable.

Related calculators

Sources