Table of Contents
It's 3 PM in New York, 8 PM in London, and 5 AM tomorrow in Tokyo. Time is complicated. Why do clocks differ so much, and which point on Earth is the reference? This guide explains UTC and GMT, how time zones are drawn, daylight saving rules, who does and doesn't change clocks, the International Date Line, and practical ways to schedule across zones. You'll find quick rules and real examples that people actually use when arranging calls, travel, or systems logging.
1UTC and GMT: the global reference
Most time conversion starts with a single reference: Coordinated Universal Time (UTC). People still use 'GMT' casually — it's close to UTC for everyday use — but UTC is the standard kept by atomic clocks and used by computers and international services.
What UTC and GMT mean
UTC is the time scale based on atomic clocks, maintained by international laboratories and coordinated through bodies such as the BIPM. GMT began as a navigation reference in the 19th century based on the Greenwich meridian. For scheduling, treat UTC as the authoritative offset reference (UTC+0), and think of GMT as the older name you'll still see in many places.
How offsets are written and why half-hour zones exist
Offsets use the format UTC±hh[:mm], for example UTC+09:00 (Tokyo) or UTC-05:00 (New York in winter). Some places use 30- or 45-minute offsets (India UTC+05:30, Nepal UTC+05:45). These reflect political and historical choices rather than neat 15-degree longitude slices.
2Time zone map and major cities
A world map of time zones shows bands, but political borders, islands, and convenience often bend those lines. Major cities are handy anchors: use them to think quickly about relative time.
Reading a time zone map
Maps show UTC offsets, but beware of daylight saving overlays. A map gives you a quick visual: roughly 15° longitude per hour is the rule of thumb, but most decisions are political. Islands and countries can pick offsets that best fit business ties or daylight patterns.
Major city examples
Memorize a few anchors: New York (UTC-05:00 standard, UTC-04:00 DST), London (UTC+00:00 standard, UTC+01:00 DST), Tokyo (UTC+09:00, no DST), New Delhi (UTC+05:30, no DST). These let you estimate many other places quickly.
3Daylight Saving Time (DST): who changes clocks and when
DST is a seasonal shift to move an hour of daylight into evening hours. Rules vary: some countries change twice a year, some stopped, and others never used it. Knowing the dates is key when scheduling near transition days.
How DST rules work and common patterns
Most DST systems advance clocks by one hour in spring and set them back in autumn. The exact dates differ: the US switches on the second Sunday in March and the first Sunday in November; the EU used to switch the last Sunday in March and October but has been debating change. Always check the current year's calendar for exact transition moments.
Country examples and notable exceptions
Many countries in Europe and North America observe DST; most of Asia and Africa do not. Russia stopped using DST in 2011 (and shifted rules again later), Japan and China do not observe DST, and countries near the equator seldom use it because daylight length changes little over the year.
4Countries without DST and special cases
Not changing clocks simplifies scheduling but creates other oddities when partners do switch. Some large countries use a single time for political reasons, producing surprising local times across long distances.
Countries that don't use DST
Major no-DST examples: China (single UTC+08:00), Japan (UTC+09:00), India (UTC+05:30), most of Africa, and many Pacific islands. The US has exceptions: Arizona (except Navajo Nation) and Hawaii do not observe DST.
Political choices: single time zones and dateline shifts
China uses a single national time though it spans five geographic time zones. Samoa moved the International Date Line in 2011 to better align business days with Australia and New Zealand; they skipped a calendar day to do it. These political moves show timekeeping is partly about trade and culture, not only geography.
5International Date Line: why the date sometimes jumps
Crossing the International Date Line (IDL) changes the calendar date. The IDL mostly follows 180° longitude but zigzags to avoid splitting countries and islands.
What happens when you cross it
Travel west across the line and you add a day; travel east and you subtract a day. For example, flying west from Honolulu to Tokyo you'll arrive two calendar days ahead compared to the departure date in some routings.
Oddities and historical moves
Several island nations have adjusted the line for convenience. Kiribati moved its eastern islands into the same date as the rest of the country in 1995, creating the Line Islands with UTC+14:00 — the earliest time on Earth. Samoa's 2011 shift shows such moves can affect business, calendars, and recurring schedules.
6Scheduling across time zones: practical steps and pitfalls
Setting meetings across zones is part logistics, part etiquette. Use UTC for backend scheduling, and be explicit for human attendees. Watch DST changes and date-line crossings when your meeting involves the Pacific.
Tools, formats, and best practices
Use ISO 8601 timestamps (e.g., 2026-01-16T14:00:00Z) when sharing exact times for systems. For people, list local times for key participants (e.g., '09:00 PST / 12:00 EST / 17:00 GMT'). Add the time zone name and offset, and clarify whether DST applies.
Common mistakes and real examples
One common error is assuming offsets don't change — run a meeting right after a DST transition and someone may miss it. Software and calendars that mix local time and UTC incorrectly can create double-bookings. For global teams, the safest approach is: publish times in both UTC and local, and confirm your attendees' time zones.
Pro Tips
- 1Quick trick: local time = UTC + offset (e.g., New Delhi = UTC+05:30). For conversions, find each place's UTC offset and subtract one from the other.
- 2Memorize anchors: New York (UTC-5/−4 DST), London (UTC+0/+1 DST), Tokyo (UTC+9 no DST) — they help estimate others.
- 3For software or logs, record timestamps in UTC (ISO 8601 with Z) to avoid ambiguity.
- 4Before scheduling, check DST transition dates for each participant's country; transitions often happen on different weekends.
- 5Remember the International Date Line: crossing it can change the calendar day; check if your trip or meeting crosses the Pacific.
Time zones are a blend of astronomy, politics, and convenience. UTC gives you a dependable anchor; from there, offsets, DST rules, and the International Date Line determine local clock time. Try our converters when scheduling: use a timezone converter for human meetings and UTC-based timestamps for logs and automation. With a couple of quick checks — UTC reference, DST status, and whether the date line might affect the day — most headaches vanish.
