How Timezones Work

A timezone is a region of the Earth that uses the same standard time. The world is divided into 24 main timezone zones, each roughly 15 degrees of longitude apart, corresponding to one hour of time difference. Timezones exist because the Earth rotates 360° in 24 hours — that's 15° per hour. As you move east, clocks are set forward; as you move west, clocks are set back. Before standardised zones, every town kept its own "local mean time" based on the sun, which made railway timetables chaotic — the spread of railways and the telegraph in the 19th century is what forced the world to agree on shared zones.

UTC (Coordinated Universal Time) is the primary time standard by which the world regulates clocks. It does not observe daylight saving time and is effectively the same as GMT at the Greenwich Meridian (0° longitude) in London. All timezones are defined as offsets from UTC: • UTC-5 = 5 hours behind UTC (e.g. New York in winter) • UTC+1 = 1 hour ahead of UTC (e.g. Paris in winter) • UTC+5:30 = 5 hours and 30 minutes ahead (e.g. India) UTC replaced GMT as the world standard in 1972, though they remain practically identical for everyday use. UTC is kept in step with atomic clocks, which is why it is the reference used by computers, aviation, finance and the internet.

GMT (Greenwich Mean Time) is the time at the Royal Observatory in Greenwich, London (0° longitude). It was established in 1884 as the world's time standard. GMT is still used in the UK during winter. In summer, the UK switches to BST (British Summer Time = GMT+1). The key difference: GMT is a timezone, UTC is a time standard. For everyday purposes they're the same, but UTC is more precise and never changes for DST. If you see "GMT" on an invitation in July from someone in London, they almost always mean BST (GMT+1) — a frequent source of one-hour errors.

Many countries shift their clocks forward 1 hour in spring and back 1 hour in autumn to make better use of daylight. This is called Daylight Saving Time (DST). • USA: Clocks spring forward 2nd Sunday of March, fall back 1st Sunday of November • EU: Last Sunday of March / October • Australia: First Sunday of October / April (opposite hemisphere) Not all countries observe DST — including China, Japan, India, most of Africa, and Iceland. Because the northern and southern hemispheres have opposite seasons, the time difference between, say, London and Sydney is not constant: it changes several times a year as each side shifts independently.

The International Date Line (IDL) runs roughly along the 180° meridian in the Pacific Ocean. When you cross it heading east, you subtract one day; heading west, you add one day. This is why countries like Samoa (UTC+13) and New Zealand (UTC+12) can be a full day ahead of countries like Hawaii (UTC-10) — even though they're geographically close. The line is not straight: it zig-zags to keep island nations like Kiribati on a single calendar day.

Most timezones differ by whole hours, but some have unusual offsets: • India: UTC+5:30 • Nepal: UTC+5:45 • Iran: UTC+3:30 • Sri Lanka: UTC+5:30 • Lord Howe Island (AU): UTC+10:30 / +11 These exist for geographic, political, or historical reasons, and make scheduling across certain borders more complex. Nepal's UTC+5:45 is the only commonly used 45-minute offset in the world.

If your team is spread across countries, the practical problem isn't the theory of time zones — it's finding the hours when everyone is awake and working at the same time. That shared window is called the overlap. A few rules of thumb: • US East Coast and Western Europe share roughly 8:00–12:00 New York time (13:00–17:00 London) • Western Europe and India overlap in the European afternoon • US West Coast and East Asia barely overlap at all, so those teams lean on asynchronous work The bigger the spread, the smaller the overlap — and beyond about a 10-hour gap, real-time meetings stop being fair to someone. Tools like Timezone Matcher lay each city's local time on a single grid so the overlap is visible at a glance, instead of doing the math in your head and risking a one-hour DST mistake.

Most scheduling errors come from a handful of recurring traps: • Assuming an offset is fixed all year — it isn't, DST moves it twice a year. • Confusing a city's current offset with its timezone name (e.g. "EST" vs "America/New_York", which is EST in winter and EDT in summer). • Saying "my 3pm" without naming the zone — always anchor to a zone or to UTC. • Forgetting the calendar date can differ: 9am Monday in Sydney is still Sunday evening in California. • Trusting that two countries in "the same" zone switch DST on the same date — the EU, US and Australia all change on different days, so overlaps drift for a few weeks each year.