The same instant is “3pm” in London, “10am” in New York and “11:30pm” in Tokyo. Time zones are how a single planet keeps many clocks, and they are the main reason handling time is hard. This article explains the system — UTC, offsets, and the troublemaker that is daylight saving — and the one rule that prevents most time-zone bugs.
Compare any two zones with the Timezone Converter or see many at once with the World Clock.
UTC: the reference clock
Everything starts with UTC — Coordinated Universal Time, the global standard that every other zone is defined against. UTC is roughly the time at the Prime Meridian in Greenwich, it is based on extremely precise atomic clocks, and crucially it never changes — no daylight saving, no seasonal shifts. That stability is exactly why UTC is the anchor: a fixed point everyone can measure from.
You will also see GMT (Greenwich Mean Time) used almost interchangeably with UTC. There is a subtle technical distinction (UTC is an atomic standard; GMT is a sun-based zone), but in practice the two are the same for everyday purposes.
Offsets: local time as UTC ± something
Every time zone is simply UTC plus or minus an offset:
| Zone | Offset | When it is 12:00 UTC |
|---|---|---|
| Los Angeles | UTC−8 | 04:00 |
| New York | UTC−5 | 07:00 |
| London | UTC+0 | 12:00 |
| India | UTC+5:30 | 17:30 |
| Tokyo | UTC+9 | 21:00 |
Note India’s :30 — not all offsets are whole hours; a few are 30 or even 45 minutes off. The instant is identical everywhere in that row; only the local clock face differs.
Daylight saving: the offset that moves
Here is where it gets genuinely hard. Many regions shift their clocks forward an hour in spring and back in autumn — daylight saving time (DST) — to better match daylight to waking hours. That means a zone’s offset is not constant: New York is UTC−5 in winter but UTC−4 in summer.
And the transition days are pathological:
- Spring forward — clocks jump 2:00 → 3:00, so 2:30am never happens that day.
- Fall back — clocks repeat 1:00 → 2:00 → 1:00, so 1:30am happens twice.
The rule that prevents the bugs
Almost all time-zone pain disappears with one discipline, echoed throughout Understanding Dates & Time:
Keep every stored moment as a UTC timestamp or UTC ISO-8601 string. Apply the user’s time zone only at the last moment, when you render it. Because UTC never shifts, your stored data stays correct and comparable forever, and the messy DST conversion happens once, at the edge, where a good date library handles it for you.
A note on scheduling future events
One subtlety: for a future appointment like “9am next March,” people usually mean 9am local time, whatever the offset turns out to be then. Since governments occasionally change DST rules, the safest approach for future local events is to store the local time plus its zone name (e.g. America/New_York), not a fixed UTC instant — so it still means 9am local even if the rules shift. For logging when something happened, UTC remains correct.
In practice
Time zones are offsets from a fixed reference (UTC), complicated by daylight saving making those offsets move. Anchor everything to UTC, convert only at display time, and lean on a maintained time-zone database rather than hard-coded rules. Convert and compare zones with the Timezone Converter and World Clock, and see the full picture in Understanding Dates & Time.
Frequently asked questions
What is UTC?
UTC (Coordinated Universal Time) is the global time standard that all time zones are defined relative to. It is essentially the time at the Prime Meridian, does not observe daylight saving, and never shifts — which makes it the stable reference for storing and comparing times worldwide.
What is a time-zone offset?
An offset is how far a local time is ahead of or behind UTC, written like UTC+5:30 or UTC−8. New York at UTC−5 is five hours behind UTC; India at UTC+5:30 is five and a half hours ahead. The same instant is simply written on different clocks.
Is GMT the same as UTC?
In everyday use they are treated as the same, and the offset is identical. Technically UTC is a precise atomic-time standard while GMT is a time zone based on the sun at Greenwich, but for almost all practical purposes you can treat UTC and GMT as interchangeable.
Why does daylight saving time cause bugs?
Because it makes a zone's offset change twice a year, and the transition days have a missing or repeated hour. A time like 2:30am may not exist or may occur twice on those days, breaking naive date math. Storing times in UTC and converting only for display avoids most of these problems.