What is a Time Zone? How Time Zones Work, UTC, GMT, DST, and the IANA Database
Time zones seem simple — until you actually have to work with them. From UTC offsets and daylight saving shifts to the International Date Line and half-hour zones, here's everything you need to know about how the world tells time.
Table of Contents
- What is a Time Zone?
- A Brief History of Time Zones
- UTC vs GMT — What's the Difference?
- How UTC Offsets Work
- Major Time Zones Around the World
- Daylight Saving Time (DST)
- The IANA Time Zone Database
- Unusual and Half-Hour Time Zones
- The International Date Line
- Time Zones for Developers
- Common Mistakes with Time Zones
What is a Time Zone?
A time zone is a region of the Earth that observes a uniform standard time. The planet is divided into 24 primary time zones, each roughly 15 degrees of longitude wide, corresponding to one hour of time difference.
In practice, time zone boundaries don't follow neat longitude lines. They zigzag around political borders, follow coastlines, and accommodate the preferences of individual countries and territories. That's why there are actually over 38 distinct UTC offsets in use today, including half-hour and quarter-hour variations.
Every time zone is defined by its offset from Coordinated Universal Time (UTC). For example, New York is UTC-5 in winter and UTC-4 during daylight saving time. Tokyo is always UTC+9.
A Brief History of Time Zones
Before time zones, every city set its clocks by the local solar noon — when the sun was highest in the sky. A town 50 miles to the west would have a different "noon" by a few minutes. This worked fine when travel was slow, but the invention of railroads and telegraphs in the 19th century made it chaotic.
Key Milestones
| Year | Event |
|---|---|
| 1847 | British railways adopt Greenwich Mean Time (GMT) as "Railway Time" |
| 1876 | Sir Sandford Fleming proposes worldwide standard time zones after missing a train in Ireland |
| 1883 | North American railroads adopt four standard time zones |
| 1884 | International Meridian Conference in Washington D.C. establishes the Prime Meridian at Greenwich and the 24-hour time zone system |
| 1918 | The U.S. Congress passes the Standard Time Act, legalizing time zones and DST |
| 1972 | Coordinated Universal Time (UTC) becomes the world's time standard, replacing GMT in official use |
UTC vs GMT — What's the Difference?
People often use UTC and GMTinterchangeably, but they're not quite the same:
| Feature | GMT | UTC |
|---|---|---|
| Full Name | Greenwich Mean Time | Coordinated Universal Time |
| Based On | Earth's rotation (astronomical) | Atomic clocks (precise) |
| Accuracy | Varies slightly (Earth's rotation is irregular) | Atomic precision, corrected with leap seconds |
| Status | Still used as a time zone (UK winter) | The global standard for timekeeping |
| DST? | No (UK switches to BST in summer) | Never — UTC does not observe DST |
For all practical computing and most everyday purposes, UTC and GMT are the same time. The difference is in how they're measured — UTC uses atomic clocks and occasionally adds leap secondsto stay in sync with the Earth's actual rotation.
The abbreviation "UTC" is a compromise: English speakers wanted "CUT" (Coordinated Universal Time) while French speakers wanted "TUC" (Temps Universel Coordonné). Neither side won, so they agreed on UTC.
How UTC Offsets Work
Every time zone is expressed as an offset from UTC using the format UTC±HH:MM:
- Positive offsets (
UTC+) are east of Greenwich — ahead in time - Negative offsets (
UTC-) are west of Greenwich — behind in time - UTC+0 is the Prime Meridian itself
To convert between two time zones, calculate the difference between their offsets. For example, to convert from UTC+9 (Tokyo) to UTC-5 (New York EST):
Difference = (-5) - (+9) = -14 hours
If it's 3:00 PM in Tokyo:
3:00 PM - 14 hours = 1:00 AM (same day, New York)
Or equivalently:
3:00 PM Tokyo → 6:00 AM UTC → 1:00 AM New YorkMajor Time Zones Around the World
Here are some of the most commonly referenced time zones:
| Abbreviation | Name | Offset | Major Cities |
|---|---|---|---|
| UTC | Coordinated Universal Time | +0:00 | Reykjavik, Accra |
| EST/EDT | Eastern Time | -5:00 / -4:00 | New York, Toronto, Miami |
| CST/CDT | Central Time | -6:00 / -5:00 | Chicago, Houston, Mexico City |
| PST/PDT | Pacific Time | -8:00 / -7:00 | Los Angeles, Seattle, Vancouver |
| CET/CEST | Central European Time | +1:00 / +2:00 | Berlin, Paris, Rome |
| IST | India Standard Time | +5:30 | Mumbai, Delhi, Bangalore |
| CST | China Standard Time | +8:00 | Beijing, Shanghai, Taipei |
| JST | Japan Standard Time | +9:00 | Tokyo, Osaka, Seoul (KST) |
| AEST/AEDT | Australian Eastern Time | +10:00 / +11:00 | Sydney, Melbourne |
Note that abbreviations like CST are ambiguous — it could mean Central Standard Time (UTC-6), China Standard Time (UTC+8), or Cuba Standard Time (UTC-5). This is why developers should always use IANA identifiers like America/Chicago instead.
Daylight Saving Time (DST)
Daylight Saving Timeis the practice of advancing clocks by one hour during warmer months to extend evening daylight. It's the single biggest source of confusion in time zone handling.
How DST Works
- Spring forward — Clocks jump ahead by 1 hour (e.g., 2:00 AM becomes 3:00 AM). One hour "disappears."
- Fall back — Clocks move back by 1 hour (e.g., 2:00 AM becomes 1:00 AM). One hour is "repeated."
This means that during the "fall back" transition, a time like 1:30 AM occurs twice— first in daylight time, then again in standard time. This creates major headaches for scheduling systems and databases.
Who Uses DST?
About 70 countries observe DST, primarily in North America and Europe. However, many countries and regions have opted out:
- No DST: Most of Asia, Africa, and South America; Arizona (except Navajo Nation), Hawaii, most of India, China, Japan
- Uses DST: Most of the U.S. and Canada, most of Europe, parts of Australia, New Zealand
- Reversed seasons: Southern Hemisphere countries that use DST (Australia, New Zealand, parts of Brazil) shift in the opposite months from the Northern Hemisphere
The Controversy
DST was first proposed by Benjamin Franklin (half-jokingly) in 1784 and widely adopted during World War I to save fuel. Today it's increasingly controversial. Studies have linked the spring transition to increases in heart attacks, car accidents, and workplace injuries in the days following the change. The EU voted to abolish DST in 2019, though implementation has been repeatedly delayed. The U.S. Senate passed the Sunshine Protection Act in 2022 to make DST permanent, but it stalled in the House.
The IANA Time Zone Database
The IANA Time Zone Database (also called tz database or Olson database, after its creator Arthur David Olson) is the definitive source of time zone data used by virtually every operating system, programming language, and web application.
It uses identifiers in the format Area/Location, for example:
America/New_York— Eastern Time (handles EST/EDT transitions automatically)Europe/London— GMT in winter, BST in summerAsia/Tokyo— JST, no DSTAsia/Kolkata— IST (UTC+5:30)Pacific/Auckland— NZST/NZDT
The database contains historical datagoing back decades, tracking every time a country changed its offset, adopted or abolished DST, or shifted its boundaries. It's maintained by a community of volunteers and updated several times a year as countries make changes.
This is why IANA identifiers are superior to simple UTC offsets — America/New_York automatically knows when to switch between EST and EDT, while a raw UTC-5 does not.
Unusual and Half-Hour Time Zones
Not all time zones use whole-hour offsets. Several regions use half-hour or even quarter-hour offsets:
| Region | Offset | Why? |
|---|---|---|
| India | UTC+5:30 | Compromise between the country's east and west extremes |
| Iran | UTC+3:30 | Historical: best fit to solar noon across the country |
| Nepal | UTC+5:45 | The only country with a 45-minute offset, chosen to distinguish from India |
| Chatham Islands (NZ) | UTC+12:45 | Small island group east of New Zealand |
| Newfoundland (Canada) | UTC-3:30 | Historical: adopted a half-hour offset before joining Canada |
| China | UTC+8 (single zone) | Spans 5 geographical time zones but uses one nationwide |
China is a particularly interesting case. Despite spanning roughly 5,200 km east to west, the entire country uses Beijing Time (UTC+8). This means that in the western city of Kashgar, the sun doesn't rise until around 10:00 AM in winter by the official clock.
The International Date Line
The International Date Line (IDL) is an imaginary line roughly following the 180th meridian through the Pacific Ocean. When you cross it:
- Traveling west (Asia → Americas): Add one day
- Traveling east (Americas → Asia): Subtract one day
The Date Line isn't straight — it zigzags to avoid splitting countries. The most dramatic deviation happened in 2011 when Samoa jumped from UTC-11 to UTC+13, skipping Friday, December 30 entirely. The entire country went from Thursday straight to Saturday to align with its major trading partners, Australia and New Zealand.
Kiribati holds the record for the earliest time zone in the world: the Line Islands use UTC+14, meaning they're the first place on Earth to ring in each new year — a full 26 hours ahead of UTC-12 (Baker Island).
Time Zones for Developers
Working with time zones in code is notoriously error-prone. Here are the core principles every developer should follow:
1. Store Times in UTC
Always store timestamps in UTCin your database. Convert to the user's local time zone only at the presentation layer.
// JavaScript — get current time in UTC
const now = new Date();
console.log(now.toISOString());
// "2026-04-04T14:30:00.000Z" (Z = UTC)
// Convert to a specific time zone for display
console.log(now.toLocaleString('en-US', {
timeZone: 'America/New_York'
}));
// "4/4/2026, 10:30:00 AM"
console.log(now.toLocaleString('en-US', {
timeZone: 'Asia/Tokyo'
}));
// "4/4/2026, 11:30:00 PM"2. Use IANA Identifiers, Not Offsets
Store the user's time zone as an IANA identifier (America/New_York) rather than a fixed offset (-05:00). The fixed offset won't account for DST transitions.
3. Use the Intl API or Libraries
Modern JavaScript has the built-in Intl.DateTimeFormat API. For complex operations, consider libraries:
// Python — using pytz / zoneinfo
from zoneinfo import ZoneInfo
from datetime import datetime
utc_now = datetime.now(ZoneInfo("UTC"))
tokyo = utc_now.astimezone(ZoneInfo("Asia/Tokyo"))
new_york = utc_now.astimezone(ZoneInfo("America/New_York"))
print(f"UTC: {utc_now}")
print(f"Tokyo: {tokyo}")
print(f"New York: {new_york}")4. Use ISO 8601 for Serialization
When sending dates over APIs, use ISO 8601 format with an explicit offset or the Z suffix for UTC:
✅ "2026-04-04T14:30:00Z" (UTC)
✅ "2026-04-04T10:30:00-04:00" (EDT)
✅ "2026-04-04T23:30:00+09:00" (JST)
❌ "April 4, 2026 2:30 PM" (no timezone info)
❌ "1743782400" (ambiguous: seconds or ms?)Common Mistakes with Time Zones
❌ Assuming UTC offset is constant
New York is UTC-5 in winter but UTC-4 in summer. Hardcoding -5 will produce wrong times for half the year.
❌ Using 3-letter abbreviations
CST is ambiguous (Central, China, or Cuba). IST can mean India, Ireland, or Israel. Always use IANA names.
❌ Assuming all days have 24 hours
On DST transition days, a day can have 23 or 25 hours. "Add 24 hours" and "add 1 day" can produce different results.
❌ Storing local times without zone info
"2026-04-04 10:30:00" without a time zone is useless. Was that 10:30 in Tokyo or New York? That's a 13-hour difference.
❌ Assuming DST transitions happen everywhere at the same time
The U.S. and Europe switch on different dates. There are weeks where the offset between New York and London is 4 hours instead of the usual 5.
✅ The golden rule
Store UTC, display local. Use IANA identifiers. Let libraries handle DST math. Never roll your own time zone logic.
Convert Time Zones Instantly
Use our free Time Zone Converter to convert times between any time zones, see current times worldwide, and handle DST transitions — right in your browser.
Try Time Zone Converter →References
- IANA. Time Zone Database. https://www.iana.org/time-zones
- International Telecommunication Union. Coordinated Universal Time (UTC). ITU-R Recommendation TF.460-6.
- National Institute of Standards and Technology. A Walk Through Time: The History of Time Zones. https://www.nist.gov/pml/time-and-frequency-division/time-realization/history
- Bartky, I.R. (2007). One Time Fits All: The Campaigns for Global Uniformity. Stanford University Press.
- Mozilla Developer Network. Intl.DateTimeFormat. https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/DateTimeFormat