How to Convert Time Zones (UTC, GMT, and Offsets)

UTC, GMT, and Offsets

UTC, Coordinated Universal Time, is the world’s reference clock. Every time zone is described as an offset from it: UTC+5 is five hours ahead, UTC−3 is three hours behind. Get a time into UTC and you can move it to anywhere on Earth.

GMT, Greenwich Mean Time, is for practical purposes the same clock and the two are often used interchangeably. The technical distinction is that UTC is defined by atomic clocks while GMT is a time zone based on the sun at Greenwich, but for everyday conversion they are identical.

Not every offset is a whole number of hours. India runs at UTC+5:30, Nepal at UTC+5:45, and parts of Australia at UTC+9:30, which is why converting to those places needs care with the minutes as well as the hours.

How to Convert

Going through UTC as a middle step is what keeps the direction straight. Trying to jump directly between two zones and guessing whether to add or subtract is where most errors happen, especially when one or both use half-hour offsets.

Worked Examples

New York to London

It is 9:00 AM in New York (UTC−5). To UTC: 9:00 + 5 = 14:00 UTC. To London (UTC+0): 14:00 + 0 = 2:00 PM in London. London is five hours ahead.

London to India

It is 2:00 PM in London (UTC+0). To UTC: 14:00. To India (UTC+5:30): 14:00 + 5:30 = 7:30 PM in India. The half hour is easy to drop and lands you thirty minutes off.

Dubai to New York

It is 6:00 PM in Dubai (UTC+4). To UTC: 18:00 − 4 = 14:00 UTC. To New York (UTC−5): 14:00 − 5 = 9:00 AM in New York.

The Daylight Saving Trap

Daylight saving time is what turns a simple offset into a moving target.

Many countries move their clocks forward an hour in spring and back in autumn, so a city’s offset from UTC changes twice a year. London is UTC+0 in winter but UTC+1 in summer. New York swings between UTC−5 and UTC−4. That means the gap between London and New York is usually five hours but not always, and there are short windows each year when it is four or six, because the two countries change on different dates.

It gets less symmetrical still. Much of Asia, the Gulf, and countries near the equator do not observe daylight saving at all, so their offset is fixed year-round while their partners’ shifts around them. The gap between Dubai and London is four hours in winter and three in summer, purely because London moves and Dubai does not.

This is the single biggest reason to use a converter that knows the current date rather than a memorised offset. An offset that was correct last month may be an hour wrong today.

Scheduling Across Zones

For a call spanning several countries, a few habits prevent the classic hour-early or hour-late mistake.

Agree the time in UTC and let each person convert to their own clock, which removes ambiguity entirely. When you write it down, name the zone explicitly, and prefer the city name over an abbreviation, since abbreviations like CST and IST are reused for completely different zones. And when a meeting is weeks away and crosses a daylight-saving changeover, confirm it again closer to the date, because one side’s clocks may have moved in between.

For anyone working with a fixed remote team, learning the usual overlap of working hours is more useful than converting each time from scratch. There is often only a narrow window where two distant zones are both awake and at work.

Common Mistakes

1. Dropping the minutes on half-hour and quarter-hour zones like India and Nepal.
2. Assuming a fixed gap between two cities when daylight saving makes it vary through the year.
3. Adding when you should subtract, best avoided by routing through UTC.
4. Trusting a time-zone abbreviation, several of which refer to more than one zone.
5. Forgetting that the two countries may change their clocks on different dates, creating brief mismatched windows.

Frequently Asked Questions

How do I convert between time zones?

Convert the source time to UTC by subtracting its offset, then add the target zone’s offset. Routing through UTC keeps the direction of the arithmetic clear, which matters most when one of the zones uses a half-hour offset like India’s UTC+5:30.

What is the difference between UTC and GMT?

For everyday conversion, none. UTC is defined by atomic clocks and GMT is a sun-based time zone at Greenwich, but they keep the same time. Use either as your reference point; the practical answer will be identical.

Why does the time difference between two cities change?

Daylight saving time. Many countries shift their clocks an hour in spring and autumn, changing their offset from UTC, and they do it on different dates. So the gap between two cities can vary by an hour or two through the year, and briefly be unusual during the changeover windows.

Do all countries use daylight saving time?

No. Large parts of Asia, the Gulf, Africa, and countries near the equator keep a fixed offset all year. When one city observes daylight saving and the other does not, the gap between them changes seasonally even though only one of them moved.

How do I handle half-hour time zones?

Treat the minutes as part of the offset and add or subtract them along with the hours. India is UTC+5:30 and Nepal UTC+5:45, so converting to them shifts both the hour and the minutes. Dropping the minutes is a common and easily avoided error.

What is the best way to schedule an international meeting?

Agree the time in UTC, then let each participant convert to their local clock. Name zones by city rather than abbreviation, and for meetings weeks out that cross a clock change, reconfirm nearer the date. This avoids the usual hour-off mistakes.

Are time zone abbreviations reliable?

Not entirely. Several abbreviations are ambiguous, with CST meaning both a North American and an Asian zone, and IST covering India, Ireland, and Israel at different times. Using the full city or region name removes the ambiguity that abbreviations introduce.

The Bottom Line

Convert through UTC every time: source to UTC by subtracting its offset, UTC to target by adding the target’s. Watch the minutes on half-hour zones, and never assume the gap between two cities is fixed, because daylight saving moves it around and the two ends often change on different dates. For scheduling, agree times in UTC and name zones by city. The time zone converter tracks every offset and daylight-saving shift so you do not have to hold the current rules in your head.