Time Zones Explained: UTC, Offsets and Daylight Saving

Coordinated Universal Time (UTC) is the time standard the world's clocks are set against. It is kept by a network of atomic clocks, it never changes for daylight saving, and it has no country. Every time zone is expressed as an offset from it: London is UTC+0 in winter and UTC+1 in summer; Istanbul is UTC+3 all year; New York is UTC−5 in winter and UTC−4 in summer; Tokyo is UTC+9 all year.

UTC is essentially the same as GMT (Greenwich Mean Time) for everyday purposes, and you will see both names. The technical difference is that GMT is a time zone based on the sun at Greenwich, while UTC is an atomic standard; they never differ by more than a second. Aviation calls UTC "Zulu" (Z), which is why flight plans and weather reports write 1430Z.

The practical value of UTC is that a timestamp in UTC means the same instant everywhere. That is how computers, phones and the internet keep in sync: your device stores time as UTC (or as a Unix timestamp, which is seconds since 1 January 1970 UTC) and only converts to local time for display.

In theory the world divides into 24 zones of 15 degrees of longitude, each one hour apart. In practice zones follow borders and politics. There are currently 38 distinct offsets in use, from UTC−12 to UTC+14:

• Half-hour offsets: India (+5:30), Iran (+3:30), Afghanistan (+4:30), Myanmar (+6:30), Newfoundland (−3:30), and central Australia (+9:30).
• Quarter-hour offsets: Nepal (+5:45) and the Chatham Islands of New Zealand (+12:45).
• One zone for a huge country: China spans about five geographical zones but uses a single national time, UTC+8. Western China's sun rises around 10 a.m. by the clock.
• Many zones for one country: Russia has 11; the United States has 6 plus territories; France, thanks to overseas departments, technically has 12.
• Beyond +12: Kiribati moved part of its territory to UTC+14 in 1995 so the whole country would share a calendar date, which is why it is the first place to see each new year.

Because of this spread, at certain moments three calendar dates exist on Earth at once. The world clock shows the date under each city's time for exactly this reason.

Daylight saving time (DST) moves the clocks forward by an hour in spring and back in autumn, changing a region's UTC offset twice a year. The trouble is that regions change on different dates, and many do not change at all:

Region	Spring forward	Fall back
European Union, UK, Switzerland, Norway	Last Sunday of March, 01:00 UTC	Last Sunday of October, 01:00 UTC
United States, Canada (most areas)	Second Sunday of March, 02:00 local	First Sunday of November, 02:00 local
Australia (south-east states)	First Sunday of October	First Sunday of April
Chile, parts of Brazil (varies by year)	September	April
Türkiye, Russia, China, Japan, India, most of Africa, South-East Asia, Arizona, Hawaii	No daylight saving

The consequences: for the two or three weeks between the US and EU changes in March and again in October/November, the gap between New York and London is four hours instead of five. A weekly 9:00 a.m. New York call that Londoners join at 14:00 suddenly appears at 13:00. Between Istanbul and Berlin the difference is one hour in summer and two in winter, all year round the Istanbul side never moved. Anyone who memorises "London is five hours ahead of New York" will be wrong for about a month every year.

The fix is to never store or remember a difference; store the zone for each party and let a tool compute the current offset. That is what the time zone converter does, using the official IANA database of zone rules.

1. Name the zone, not the offset. "Europe/Berlin" or "Berlin time" is unambiguous; "CET" is not, because Berlin is on CEST in summer, and "UTC+1" is wrong for half the year.
2. Attach the date. The same wall-clock time converts differently on 10 March and 20 March if one party is crossing a DST boundary. Always convert for the specific date of the meeting.
3. Pick a reference zone for recurring events. A weekly call is anchored to one party's local time (usually the organiser's), and the other parties accept that it will move for them twice a year. Say which zone is the anchor in the invitation.
4. Check the day. 22:00 in Los Angeles on Monday is 15:00 on Tuesday in Sydney. Cross-date-line conversions are the ones people get wrong most often.
5. Beware of "EST", "PST", "IST". Abbreviations collide: IST is India, Israel and Ireland; CST is Central US, China and Cuba. Use city names.

Calendar apps handle most of this automatically once each event has a zone attached, but they only work if the organiser entered the zone rather than a bare time. When in doubt, paste the proposed time into the converter with the actual date and read off the result for every city.

With two cities you are looking for an hour inside both working days. With three or more, the overlap shrinks fast. London (UTC+0/+1), New York (−5/−4) and San Francisco (−8/−7) share only 16:00–17:00 London time. Add Singapore (+8) and there is no hour in which all four are at work; the meeting will be early or late for someone, and fair teams rotate who suffers. Put every participant's city into the world clock, look for the block of hours where all are between 8 and 18, and if there is none, alternate between two slots on alternate weeks. Once the slot is agreed, the meeting timer keeps the call itself on schedule, and the countdown can show the time remaining until a launch that happens at a single global instant.