How Time Zones Work

A time zone is not a place — it's a rule for how a place's clock relates to one worldwide reference. Get that one idea straight and every confusing conversion, from a 9 AM call across the Atlantic to "why is my calendar invite an hour off in November," falls into place.

UTC and offsets: the one reference that never moves

All time-zone math hangs off UTC (Coordinated Universal Time) — the shared reference clock, with no daylight saving and no local quirks. Every zone is expressed as an offset: how far its local clock sits ahead of or behind UTC. Tokyo runs at UTC+9 (nine hours ahead), New York at UTC−5 in winter (five behind), India at UTC+5:30.

One convention to internalize: the offset means local time minus UTC. A positive offset means that place's clock is ahead. When it's 09:00 in London in winter, it's already 14:30 in India and 18:00 in Tokyo.

The conversion formula

To convert between any two zones, convert to UTC and back out again — or do it in one step:

target time = source time + (target offset − source offset)

Example: a 9:00 AM call in New York (UTC−5) for colleagues in Paris (UTC+1) works out as 9:00 + (1 − (−5)) = 9:00 + 6 hours = 3:00 PM in Paris.

A long-haul example in the other direction: 9:00 PM Friday in Los Angeles (UTC−8) is 21:00 plus 17 hours in Tokyo (UTC+9), which is 2:00 PM Saturday. Notice that the day changed: large offsets can push a time into tomorrow (or back into yesterday) on the other side of the world.

Named zones vs fixed offsets

"New York is UTC−5" is only true for part of the year. Real software uses named zones from the IANA database — identifiers like America/New_York or Europe/Paris — which are rule sets, not fixed offsets. Each named zone carries its daylight-saving schedule and even its history: most of Arizona stays on UTC−7 all year, while New York flips between UTC−5 and UTC−4 twice a year.

That's why "just use the offset" fails: the offset for a given place changes, and two places that share an offset in summer can diverge in winter. Always convert by zone name plus a date, never by a hardcoded offset.

Daylight saving: the offset that moves

DST shifts a zone's offset by an hour for part of the year:

• United States: from the second Sunday in March to the first Sunday in November (New York is UTC−4 in summer, UTC−5 in winter).
• European Union: from the last Sunday in March to the last Sunday in October.
• Southern hemisphere: roughly reversed — New Zealand's summer DST runs from late September into April.

Near the equator, where day length barely changes over the year, most places skip DST entirely. The transitions are the sharp edge: on the switch days, some local clock times simply don't exist (spring forward) or happen twice (fall back) — which is why a meeting set for 2:30 AM on the changeover morning is a gamble.

The strange edges: half-hour zones and the date line

Most zones sit on whole hours, but not all of them. India runs at UTC+5:30, Nepal at UTC+5:45, and New Zealand's Chatham Islands at UTC+12:45. The offsets also stretch further than most people guess: from UTC−12 to UTC+14, a 26-hour spread. Kiribati's Line Islands sit at UTC+14 — the first inhabited places to see each new day.

Crossing the International Date Line compounds this: the same physical instant can be Saturday afternoon on one side of the line and Sunday afternoon on the other. Flying east across it you "arrive before you left" in clock terms — the calendar, not the clock, absorbed the difference.

Four rules that prevent time-zone bugs

• Store instants in UTC (or as a timestamp), and convert to a local view only when displaying them.
• Name the reference zone when scheduling. "3 PM New York" is unambiguous; "3 PM" exchanged between two cities is not.
• Re-check recurring meetings twice a year. A call fixed at 9 AM New York / 3 PM Paris drifts to 4 PM Paris during the weeks when one side has switched to DST and the other hasn't.
• Test the boundaries: times near midnight, times near DST transitions, and dates like February 29.

Try it yourself

Pick any two zones and convert between them with the Time Zone Converter, which uses real named zones and applies the correct daylight-saving rules for the date you choose. Planning a call across several cities? The Time Zone Meeting Planner lays out the same instant in every participant's local time, so you can spot the ones that land at 2 AM. And for counting whole days rather than clock hours, the Date Countdown tells you exactly how many days separate a date here from a date there.