Every day, billions of people coordinate across 24 primary time zones that wrap the globe. Understanding how these zones work is essential for scheduling international calls, booking flights, managing remote teams, and making sense of timestamps in data. What seems straightforward on the surface has surprising complexity once you factor in political boundaries, daylight saving rules, and historical quirks.
Before the 1880s, every city kept its own local solar time — noon was when the sun reached its highest point overhead. This worked fine until railroads connected distant cities and telegraph operators needed to coordinate schedules. In 1884, delegates from 25 nations met at the International Meridian Conference in Washington, D.C. and agreed to divide the Earth into 24 zones, each spanning 15 degrees of longitude, centered on the prime meridian at Greenwich, England.
In theory, each zone is exactly one hour apart. In practice, political borders, economic ties, and national preferences create a far messier map. China spans five geographical time zones but uses a single time (UTC+8) nationwide. Russia has 11 time zones. And some zones use half-hour or even quarter-hour offsets.
Coordinated Universal Time (UTC) replaced GMT as the world’s reference point in 1960. UTC is maintained by a network of over 400 atomic clocks worldwide and is accurate to within a nanosecond per day. Every other time zone is defined as an offset from UTC — for example, Eastern Standard Time is UTC−5, meaning it is five hours behind UTC.
| Time Zone | UTC Offset | Major Cities |
|---|---|---|
| EST / EDT | UTC−5 / −4 | New York, Toronto, Miami |
| CST / CDT | UTC−6 / −5 | Chicago, Houston, Mexico City |
| MST / MDT | UTC−7 / −6 | Denver, Phoenix, Calgary |
| PST / PDT | UTC−8 / −7 | Los Angeles, Seattle, Vancouver |
| GMT / BST | UTC+0 / +1 | London, Dublin, Lisbon |
| CET / CEST | UTC+1 / +2 | Paris, Berlin, Rome |
| IST | UTC+5:30 | Mumbai, Delhi, Bangalore |
| CST (China) | UTC+8 | Beijing, Shanghai, Hong Kong |
| JST | UTC+9 | Tokyo, Seoul, Osaka |
| AEST / AEDT | UTC+10 / +11 | Sydney, Melbourne, Brisbane |
Use the Time Zone Converter to translate any time between zones instantly.
The International Date Line (IDL) runs roughly along the 180° meridian through the Pacific Ocean. It marks where one calendar day ends and the next begins. If it were perfectly straight, it would cut through Russia, Fiji, and several island groups, so it zigzags to keep countries on a single date. Kiribati extended its zone in 1995 to become the first place to welcome each new year, placing some of its islands at UTC+14 — the farthest ahead of any location on Earth.
The formula is straightforward: Target Time = Source Time + (Target UTC Offset − Source UTC Offset). For example, converting 3:00 PM EST (UTC−5) to CET (UTC+1): 3:00 PM + (1 − (−5)) = 3:00 PM + 6 = 9:00 PM CET. During daylight saving periods, make sure to use the DST-adjusted offset.
Common Pitfall: “EST” and “ET” are not the same thing. EST always means UTC−5 (standard time), while ET is a shorthand that automatically adjusts for daylight saving — so ET could be either UTC−5 or UTC−4 depending on the season. When scheduling across zones, specify whether you mean standard or daylight time.
Several countries break from the standard one-hour increments. India uses UTC+5:30 for the entire nation despite spanning enough longitude for two zones. Nepal is UTC+5:45, the only country with a 45-minute offset. The Chatham Islands of New Zealand use UTC+12:45. Afghanistan sits at UTC+4:30. These choices typically reflect a compromise between geography and national unity.
Modern software relies on the IANA Time Zone Database, an open-source project that tracks every time zone rule past and present. When a government changes its DST policy, the database is updated and distributed through operating system patches. This is why storing timestamps in UTC and converting to local time on display is a best practice for developers — it prevents errors when rules change. The World Clock tool uses this same database to show accurate local times for hundreds of cities worldwide.
Use UTC as your anchor. When coordinating across more than two zones, express the meeting time in UTC first, then let each participant convert to their local time. This eliminates confusion from directional terms like “ahead” or “behind.”
Account for date changes. A 10 PM meeting in New York is already the next morning in Tokyo. Always include the date when scheduling internationally.
Remember seasonal shifts. Not all countries change clocks on the same date. The US and Europe shift DST on different weekends, creating a brief period each spring and fall where the usual time difference changes by an hour. Use the Time Zone Map to visualize current offsets around the world.
Try it now. Use the free Time Zone Converter to translate between any two zones, check the World Clock for current times worldwide, or explore the Time Zone Map for a visual overview — no signup required.
Related tools: Time Zone Converter · Time Zone Map · World Clock · DST Tracker