Time Zones Explained: UTC, DST, and Offsets (2025)

Table of Contents

Time zones are more confusing than they need to be. They were designed in the 19th century for railway schedules and have been accumulated, adjusted, and politicized ever since. Some countries do not observe Daylight Saving Time. Some time zones are offset by 30 or 45 minutes. Three different places call themselves IST. Countries change their time zones for political reasons.

This guide gives you a clear, practical understanding of how time zones work: what UTC is and why it matters, the difference between GMT and UTC, how Daylight Saving Time works and which countries observe it, how to read timezone names and abbreviations correctly, and how to convert times between zones without making the mistakes that trip up even experienced schedulers.

UTC: The Global Reference Standard

UTC (Coordinated Universal Time) is the global time standard. It is the reference point from which all time zones are defined. UTC has no Daylight Saving Time — it never changes. The current UTC time is the same in a database server in Singapore as it is in a log file in London.

Every time zone on Earth is defined as UTC plus or minus some offset. New York is UTC-5 in winter and UTC-4 in summer. Tokyo is UTC+9 year-round. India is UTC+5:30 (yes, a half-hour offset) year-round.

Why UTC matters for developers and global teams: When you store a timestamp in a database, store it in UTC. When you log an event, log it in UTC. When you schedule a job, schedule it in UTC. Converting to local time is a display concern, not a storage concern. Storing times in local time zones creates conversion problems when times span DST transitions, location changes, or cross-zone comparisons.

UTC vs Zulu time: Zulu time is another name for UTC, used in aviation and military contexts. The "Z" suffix in ISO 8601 timestamps (2025-03-15T14:30:00Z) stands for Zulu — it means the time is in UTC. GMT+0 and UTC+0 are functionally identical for practical purposes; the technical difference (UTC is based on atomic clocks; GMT is based on astronomical observation) amounts to fractions of a second.

Daylight Saving Time: What It Is and Who Observes It

Daylight Saving Time (DST) is the practice of advancing clocks by one hour in spring and reverting in autumn, shifting an hour of daylight from the morning to the evening during summer months. Clocks "spring forward" (lose an hour — the night is shorter) and "fall back" (gain an hour — the night is longer).

Countries that observe DST: Most of North America and Europe, parts of the Middle East, and a few other countries. Approximately 70 countries observe DST in some form.

Countries that do NOT observe DST: Most of Asia (including China, Japan, India, South Korea), most of Africa, most of the Middle East, and Australia's Northern Territory and Queensland. These countries have a fixed UTC offset year-round.

Transition dates vary by region:

United States and Canada: Second Sunday in March (spring forward) / First Sunday in November (fall back)
European Union: Last Sunday in March / Last Sunday in October
Australia: First Sunday in October / First Sunday in April (southern hemisphere — opposite season)
Israel, Iran, Jordan: Vary by year; follow separate schedules

The critical scheduling implication: A recurring meeting scheduled as "9am ET / 2pm GMT" will shift by one hour when the US springs forward before the EU does (a one-to-two-week window where the US is on EDT but the EU is still on standard time). Teams spanning the Atlantic must check meeting times around both transitions annually.

Time Zone Abbreviations: What They Actually Mean

Time zone abbreviations are frequently ambiguous. The same abbreviation can mean different things in different contexts.

IST is the worst example: IST means:

Indian Standard Time (UTC+5:30)
Irish Standard Time (UTC+1, during DST — otherwise IST = Irish Standard Time = UTC+0)
Israel Standard Time (UTC+2)

When someone says "the meeting is at 3pm IST," you must ask which one.

EST vs EDT: EST (Eastern Standard Time) is UTC-5 and applies November–March. EDT (Eastern Daylight Time) is UTC-4 and applies March–November. "ET" (Eastern Time) refers to whichever is currently in effect. When someone says "3pm EST" in July, they almost certainly mean EDT — they are using the wrong abbreviation. For scheduling, always specify the UTC offset if precision matters: "15:00 UTC-4" is unambiguous; "3pm EST" is not.

GMT vs UTC: GMT (Greenwich Mean Time) is UTC+0 during winter and BST (British Summer Time = UTC+1) during summer in the UK. When the UK is on BST, it is not on GMT. "GMT" is often used loosely to mean UTC, which is technically correct in the sense that GMT and UTC differ by less than one second — but the UK being on BST while called "GMT" in casual usage creates confusion.

A better approach for scheduling: Use UTC offsets explicitly. "15:00 UTC" or "15:00+05:30" is unambiguous. Abbreviations like IST, EST, and GMT are ambiguous and time-zone-context-dependent.

Convert times between zones precisely— Enter any time and see it in all relevant zones

Half-Hour and 45-Minute Time Zones

Most people expect time zones to be in whole-hour increments. Many are not.

Half-hour offset zones:

India (IST): UTC+5:30 — 1.4 billion people on a half-hour offset
Iran (IRST): UTC+3:30 standard / UTC+4:30 DST
Afghanistan (AFT): UTC+4:30
Myanmar (MMT): UTC+6:30
Australia's Northern Territory and South Australia: UTC+9:30 standard / UTC+10:30 DST

45-minute offset zones:

Nepal (NPT): UTC+5:45 — the most extreme non-standard offset
Chatham Islands (NZCT): UTC+12:45 standard / UTC+13:45 DST

Lord Howe Island (Australia): UTC+10:30 in winter, UTC+11 in summer — a 30-minute DST transition rather than the usual 60 minutes.

Why non-standard offsets exist: They are typically the result of political decisions to align with a neighboring country's time zone while still maintaining some differentiation, or to better match geographic solar time in a region on the edge of a full-hour zone.

Practical implication: When building software that handles time zones, never assume all offsets are in whole hours. The IANA timezone database (also called the Olson database) is the authoritative source and includes all non-standard offsets.

How to Convert Times Correctly

Time zone conversion requires three inputs: the source time, the source UTC offset (on the specific date), and the target UTC offset (on the specific date).

Manual conversion method:

1. Convert source local time to UTC: subtract the source UTC offset from the local time.

If it is 3pm (15:00) EDT (UTC-4): 15:00 + 4:00 = 19:00 UTC

2. Convert UTC to target local time: add the target UTC offset.

19:00 UTC to IST (UTC+5:30): 19:00 + 5:30 = 00:30 (next day)

The DST trap: The UTC offset changes on DST transition dates. If you are converting a time that falls on a DST transition day (or near one), verify which offset is in effect. On the "spring forward" day in the US, clocks go from 1:59 AM EST (UTC-5) directly to 3:00 AM EDT (UTC-4). The time 2:00 AM–2:59 AM does not exist on that day. On the "fall back" day, 1:00 AM–1:59 AM occurs twice — once in EDT (UTC-4) and again in EST (UTC-5).

ISO 8601 timestamp format: The international standard for unambiguous timestamp representation. Examples:

2025-03-15T14:30:00Z — UTC time (Zulu)
2025-03-15T09:30:00-05:00 — EST (UTC-5)
2025-03-15T20:00:00+05:30 — IST (UTC+5:30)

Including the offset in the timestamp makes it unambiguous and machine-parseable.

Frequently Asked Questions

What is the difference between UTC and GMT?

UTC (Coordinated Universal Time) is based on atomic clock measurements; GMT (Greenwich Mean Time) is based on the Earth's rotation. They differ by at most 0.9 seconds, kept synchronized by leap seconds. For practical purposes — scheduling, programming, time zone conversion — UTC and GMT are interchangeable. The key difference that matters: the UK is on GMT in winter but on BST (British Summer Time, UTC+1) in summer, so 'GMT' used loosely to mean UTC+0 is not always accurate for the UK.

Why do some countries not observe Daylight Saving Time?

Countries near the equator have minimal daylight variation between seasons, making DST pointless — India, most of Africa, and Southeast Asia fall into this category. Other countries abolished DST after research showed it provides minimal energy savings and has measurable negative effects on health (car accidents, heart attacks, and sleep disruption increase in the week after spring transitions). Japan, China, and Russia have all discontinued DST at various points. The EU voted to end mandatory DST transitions in 2021, though implementation has been delayed.

How do I handle time zones in programming?

Store all timestamps in UTC. Never store local times without an explicit UTC offset. Use the IANA timezone database (via libraries like Python's pytz, Java's ZoneId, JavaScript's Intl API, or the date-fns-tz library) for timezone conversion rather than manually applying offsets. Apply the local time zone offset only at the display layer — when presenting times to users. This prevents DST conversion bugs, avoids ambiguity, and makes cross-timezone comparisons reliable.

What happens to meetings during Daylight Saving Time transitions?

Recurring meetings set to a specific local time adjust automatically in calendar apps — a 9am Monday meeting stays at 9am local time after a DST transition. However, the UTC time of that meeting changes by one hour, which can cause issues for participants in zones that do not observe DST or that transition on different dates. A meeting at 9am ET / 2pm UTC in winter becomes 9am ET / 1pm UTC in summer when the US moves to EDT. Always verify recurring cross-timezone meetings after any DST transition.

Why is India on a half-hour time zone?

India's UTC+5:30 offset was established in 1947 as a compromise between the eastern and western extremes of the country, which span about 30 degrees of longitude. A single whole-hour offset would misrepresent solar time for either the eastern or western regions significantly. The half-hour offset provides a middle ground. India also does not observe DST, maintaining UTC+5:30 year-round — a stable, fixed offset used by 1.4 billion people.

Summary

Time zones exist because of geography and history, and they accumulate every quirk of the political decisions made along the way. Understanding the fundamentals — UTC as the reference standard, DST transitions and their dates, the ambiguity of abbreviations like IST and GMT, and the existence of non-whole-hour offsets — lets you navigate time zone arithmetic confidently without being tripped up by the edge cases.

For scheduling: specify UTC offsets explicitly rather than relying on abbreviations. For development: store timestamps in UTC. For recurring meetings: verify overlap after each DST transition in each participant's zone. The tools to handle all of these cases are straightforward; the knowledge of which edge cases to check for is what this guide provides.