How Time Zones Work — A Complete Beginner's Guide
Time zones feel obvious until you actually think about them: why 24 zones? Why does India use a half-hour offset? Why does China, wider than the continental US, use just one? Here's the whole picture in plain English.
Why time zones exist at all
Local time was originally solar time: noon was simply the moment the sun stood highest in the sky wherever you were. Because the Earth rotates, that moment sweeps continuously westward — solar noon in Boston happens about 12 minutes before solar noon in New York. For most of human history nobody cared, because you couldn't travel or communicate fast enough for a 12-minute difference to matter.
Railways broke that. By the mid-1800s, a train line crossing a country would pass through dozens of towns each keeping its own slightly different local time, which made timetables nearly impossible and occasionally caused collisions. The fix, pioneered by railway companies and formalized at the International Meridian Conference of 1884, was to divide the world into standard zones, each keeping a single uniform time.
How the zones are laid out
The Earth rotates 360° in about 24 hours, so it turns 15° of longitude per hour. The idealized scheme divides the world into 24 slices of 15° each, anchored at the Prime Meridian in Greenwich, London (0° longitude). Each zone is described by its offset from UTC (Coordinated Universal Time — see our UTC vs GMT guide):
- London is at UTC+0 (UTC+1 in summer),
- New York is at UTC−5 (UTC−4 in summer),
- Seoul and Tokyo are at UTC+9 year-round.
In practice, though, zone boundaries follow political borders, not neat meridian lines. Countries choose whatever offset suits them, which produces some famous quirks:
- China spans five "geographic" zones but uses a single national time, UTC+8. In far-western Xinjiang, solar noon can arrive around 3 p.m. on the clock.
- India uses UTC+5:30 — a half-hour compromise between the two meridians that bracket the subcontinent.
- Nepal goes further with UTC+5:45, one of only a handful of 45-minute zones (the Chatham Islands in New Zealand use UTC+12:45).
- France counts 12 time zones — more than any other country — thanks to its overseas territories from French Polynesia to Réunion.
Counting every half-hour and 45-minute variant, the world today uses around 38 distinct UTC offsets, not 24.
The International Date Line
If you keep adding an hour as you travel east, you'd eventually arrive back home a full day ahead of your neighbors. The International Date Line (IDL), running roughly along 180° longitude through the Pacific, is where the calendar resets: cross it heading west and you skip forward a day; cross it heading east and you repeat one.
Like zone boundaries, the IDL zigzags for political reasons. Kiribati famously bent it in 1995 so the whole country could share one calendar day, creating the UTC+14 zone — the first place on Earth to greet each new day. At any given moment, three different calendar dates can exist simultaneously somewhere on the planet.
Offsets change — that's why databases exist
A city's offset is not a law of nature; it's legislation, and legislation changes. Countries adopt or abandon daylight saving time, switch offsets to align with trading partners, or shift for political symbolism. Recent decades saw Samoa jump across the date line entirely (2011), North Korea create and then abolish its own half-hour zone (2015–2018), and numerous countries scrap DST.
All of these rules — current and historical — are maintained in the IANA Time Zone Database (also called the tz database or zoneinfo). Every entry is an identifier like Asia/Seoul or America/New_York paired with the complete rule history for that region. Your phone, your laptop, every major operating system, and every programming language relies on this single, volunteer-maintained database. It's one of the quiet pieces of infrastructure holding the connected world together.
This is exactly how gworldtime stays correct: each of our 337 cities is mapped to its IANA identifier, and local times are computed from a network-synchronized UTC reference using your browser's built-in copy of the database. When a country changes its rules, browser vendors ship the update and the clock stays right.
Reading a time zone offset without mistakes
A few practical rules that prevent the most common errors:
- The sign tells you the direction. Positive offsets (UTC+9, Seoul) are east of Greenwich and ahead in time; negative offsets (UTC−5, New York) are west and behind.
- Time differences between two cities = difference of their offsets. Seoul (UTC+9) vs New York (UTC−5): 9 − (−5) = 14 hours apart in winter — but only 13 in summer, when New York moves to UTC−4. DST changes pairwise differences, which is why they must never be memorized as constants.
- Zone abbreviations are ambiguous — don't trust them. "CST" means Central Standard Time (UTC−6), China Standard Time (UTC+8), and Cuba Standard Time (UTC−5). Always prefer the city or the explicit offset.
- The date can differ, not just the hour. When it's Friday evening in California, it's already Saturday morning in Seoul. Any cross-zone plan needs a date attached, not just a time.
Quick reference: offsets of major cities
| City | IANA zone | Standard offset | Summer (DST) offset |
|---|---|---|---|
| Los Angeles | America/Los_Angeles | UTC−8 | UTC−7 |
| New York | America/New_York | UTC−5 | UTC−4 |
| São Paulo | America/Sao_Paulo | UTC−3 | — (no DST) |
| London | Europe/London | UTC+0 | UTC+1 |
| Paris / Berlin | Europe/Paris | UTC+1 | UTC+2 |
| Moscow | Europe/Moscow | UTC+3 | — (no DST) |
| Dubai | Asia/Dubai | UTC+4 | — (no DST) |
| New Delhi | Asia/Kolkata | UTC+5:30 | — (no DST) |
| Beijing | Asia/Shanghai | UTC+8 | — (no DST) |
| Seoul / Tokyo | Asia/Seoul · Asia/Tokyo | UTC+9 | — (no DST) |
| Sydney | Australia/Sydney | UTC+10 | UTC+11 (southern summer) |
| Auckland | Pacific/Auckland | UTC+12 | UTC+13 (southern summer) |
See it, don't calculate it
Offsets and arithmetic are error-prone; a picture isn't. On the gworldtime 3D globe you can watch the day/night line sweep across the planet in real time, pin up to five cities, and read their live times and differences side by side — no mental math required.
Read next: UTC vs GMT — what's the difference? · Daylight Saving Time explained · How the world's clocks stay accurate