Time Zone Converter

Convert a meeting time from one time zone to another. Choose a date, time and zones, and the converter applies the correct daylight saving offset for that moment.

Date & Time • Daylight saving aware • 40+ zones • Updated November 18, 2026 • Reviewed by the GlobalCalcly editorial team
Convert a meeting time Daylight saving handled
Date and time
Times use the IANA time zone database, so daylight saving changes are applied for the chosen date.
Converted time
—

Choose a date, time and time zones.

From —
To —
UTC —
Time difference —

How time zone conversion works

Every time zone is defined by its offset from Coordinated Universal Time (UTC). New York is UTC−5 in winter and UTC−4 in summer, while London is UTC+0 in winter and UTC+1 in summer. Converting a time means finding the UTC instant, then formatting it in the target zone.

This calculator uses the IANA time zone database through your browser's built-in internationalisation support. That means it knows the historical and current daylight saving rules for each zone, rather than applying a fixed offset.

Daylight saving complications

Daylight saving transitions create two awkward cases. In spring, clocks jump forward and an hour that would normally exist is skipped. In autumn, clocks fall back and an hour occurs twice. The converter resolves the chosen wall-clock time using the offset in effect at that moment, which matches how calendars and phones behave.

Not every region observes daylight saving. Most of Asia, Africa and parts of Australia keep a fixed offset all year, while Europe and North America change twice a year on different dates.

Planning meetings across zones

When scheduling, always state the time zone along with the time. “3 PM” is ambiguous; “3 PM New York” is not. It also helps to share a UTC time, because UTC never changes for daylight saving and is understood internationally.

The calculation

UTC = local time − offsetfrom
target time = UTC + offsetto

The offsets are looked up for the specific date, so summer and winter conversions can differ by an hour in zones that observe daylight saving.

Worked examples

  • 09:00 New York to London in January: 14:00 London (UTC−5 to UTC+0).
  • 09:00 New York to London in July: 14:00 London (UTC−4 to UTC+1).
  • 15:00 London to Tokyo: 00:00 the next day in Tokyo (UTC+0 to UTC+9).
  • 10:00 Dubai to Mumbai: 11:30 Mumbai (UTC+4 to UTC+5:30).
  • 18:00 Sydney to Los Angeles: the previous day in Los Angeles, because the date line is crossed.

Half-hour and 45-minute offsets

Not all zones differ by whole hours. India is UTC+5:30, Nepal is UTC+5:45, and parts of Australia use UTC+9:30. The converter handles these offsets, which is why a meeting can land on the half hour rather than the hour.

When a conversion crosses midnight, the date changes too. Check the full date shown under the result, not just the clock time, before sending an invitation.

Common mistakes to avoid

Storing one offset per city is the usual error. New York switches between UTC−5 and UTC−4, and in 2026 it runs on UTC−4 from 8 March to 1 November, so a note saying "five hours behind London" is wrong for weeks at a time.

Mismatched switch dates cause the rest. US daylight saving begins on 8 March 2026 and European summer time on 29 March, so from 8 to 28 March the New York to London gap is four hours; the same thing happens from 25 October to 1 November at the other end of the year.

Watch the hemisphere. Sydney runs UTC+11 from October to April, so in January it sits 11 hours ahead of London, not the 10 that apply in July.

What changes the number most

Daylight saving status outweighs every other factor. One hour of DST shifts the result by 60 minutes and often applies to one side of a pair only. A 09:00 New York meeting is 13:00 in London on 15 March 2026 and 14:00 on 15 April.

The base offsets come next. Whole-hour zones differ by integers, so surprises come from the fractional ones: India at UTC+5:30, Nepal at UTC+5:45, Australia's central zone at UTC+9:30. Kathmandu to Adelaide is a 3-hour-45-minute gap in the southern winter.

The date line decides the day. Auckland at UTC+13 against Los Angeles at UTC−8 gives a 21-hour gap, so Monday 09:00 in Auckland is Sunday 12:00 in Los Angeles.

How to check the result

Route through UTC and compare. 09:00 in New York on 15 January 2026 is 14:00 UTC at UTC−5; London at UTC+0 shows 14:00 and Berlin at UTC+1 shows 15:00, so a Berlin answer of 14:00 means the New York offset was applied twice.

Test the direction. Going east adds hours and going west subtracts them: Dubai at UTC+4 is four hours ahead of London, so 11:00 in London is 15:00 in Dubai.

For anything you will actually book, confirm against the zone name rather than a stored offset, because offsets change when a government changes its rules.

Frequently asked questions

Does the converter handle daylight saving?

Yes. It reads the IANA time zone database for the chosen date, so summer offsets such as British Summer Time and winter offsets such as Eastern Standard Time are applied to the correct moment. Southern hemisphere zones reverse the pattern.

Why is the result on a different date?

Crossing the international date line or passing midnight shifts the local date. A 9 a.m. meeting in Tokyo is the previous evening in New York, so the converter always prints the full date beside the time.

What is UTC?

Coordinated Universal Time is the global reference standard kept by atomic clocks. It has no daylight saving, so offsets from UTC change seasonally for zones that observe summer time. Local clocks differ from UTC by whole, half or quarter hours.

Can I convert a time in the past or future?

Yes. Pick any past or future date and the converter applies the rules that were or will be in force. Historic transitions and scheduled changes are both handled from the same database. Unusual historical offsets may still appear in old records.

Why do some zones have 30-minute offsets?

Some regions chose offsets that track the sun more closely than whole hours allow. India uses UTC+5:30, Nepal UTC+5:45, and parts of Australia UTC+9:30, which keeps local noon nearer the actual sun. Chatham Islands uses UTC+12:45, one of the oddest.

Sources & methodology

  • IANA Time Zone Database — historical and current time zone rules.
  • International Telecommunication Union — UTC and time zone references.
  • Calculation method: wall-clock time converted to UTC using the zone offset, then formatted in the target zone.

Results are estimates for general information. For medical, legal or financial decisions, confirm with a qualified professional.