Time Zones Explained: A Beginner's Guide to UTC, GMT and Offsets

Updated on April 27, 2026

Why Does My 3 PM Meeting Feel Like Everyone Else's Midnight?

I remember the first time I tried to schedule a video call with someone in London while I was sitting in Chicago. I picked what felt like a perfectly reasonable time — 2 PM on a Tuesday — and sent out the calendar invite. My London colleague replied almost immediately: "That's 8 PM for me, could we do earlier?" I had no idea. I thought time zones were just... shifting the clock by a few hours and that was it. Easy.

It is not easy. Not at first, anyway. But once you understand the actual logic behind how time zones work, it clicks in a way that genuinely changes how you think about scheduling across countries. So let's break it down from scratch, no math degree required.

The Earth Spins. That's the Whole Story.

Here's the core thing: the Earth rotates once every 24 hours. As it spins, different parts of the planet face the Sun at different moments. When it's noon in New York (Sun is roughly overhead), it's the middle of the night in Tokyo (Sun is on the other side of the planet).

So way back in the 1800s, when railroads started connecting cities and train schedules needed to actually make sense, people agreed to divide the globe into zones. Each zone would share the same clock time. You cross into a new zone, you adjust your watch. Simple idea, messy execution — but we'll get there.

What is UTC and Why Should You Care?

UTC stands for Coordinated Universal Time. (Yes, the abbreviation doesn't match — that's because it's a compromise between the English "CUT" and the French "TUC." International agreements are weird.)

Think of UTC as the referee of all time zones. It's the universal baseline — the one clock that everyone else measures themselves against. UTC doesn't observe daylight saving. It doesn't shift in summer or winter. It just ticks forward, steadily, no drama.

When you see a timestamp written like 2024-03-15T14:30:00Z, that little "Z" at the end means "Zulu time," which is just another name for UTC. Software developers and airline systems love UTC because it removes ambiguity completely.

Wait — What's GMT Then? Is That Different?

Here's where people get confused. GMT stands for Greenwich Mean Time, named after the Royal Observatory in Greenwich, London. Historically, GMT was the global timekeeping standard. UTC eventually replaced it for technical reasons (UTC uses atomic clocks; GMT uses the Earth's rotation, which is slightly irregular).

For everyday purposes? GMT and UTC are the same thing. When someone says "GMT+5:30" they mean exactly what someone else means by "UTC+5:30." The difference only matters to physicists measuring things in microseconds. If you're scheduling a meeting, treat them as identical.

Understanding Offsets: The + and − Numbers

This is the part that actually lets you convert between time zones. An offset is simply how many hours (and sometimes minutes) a location is ahead of or behind UTC.

  • UTC+0 — London in winter, Iceland always
  • UTC+5:30 — India (yes, 30 minutes, not a whole hour — India did this intentionally)
  • UTC+9 — Japan, South Korea
  • UTC−5 — New York in winter (Eastern Standard Time)
  • UTC−8 — Los Angeles in winter (Pacific Standard Time)

So if it's 12:00 UTC and you're in Japan (UTC+9), your local time is 12 + 9 = 21:00 (9 PM). If you're in New York in winter (UTC−5), it's 12 − 5 = 07:00 (7 AM). That's the whole calculation. The plus or minus tells you which direction to go.

Some offsets are especially surprising. Nepal is UTC+5:45 — yes, 45 minutes. Chatham Islands in New Zealand sit at UTC+12:45 in standard time. The world didn't organize itself neatly around whole-hour lines, because political borders rarely follow the geographic ones.

Daylight Saving Time: The Part That Trips Everyone Up

Now here's where scheduling across borders gets genuinely confusing. Daylight Saving Time (DST) is when many countries shift their clocks forward by one hour in spring and back again in fall. The goal is to make better use of natural daylight during the longer summer days.

But here's the trap: not every country does this, and the ones that do don't all do it on the same day.

The United States and most of Europe both observe DST, but they switch on different weekends. There's a stretch of a few weeks in spring where the US has already sprung forward but Europe hasn't yet — and during that window, the usual offset between, say, New York and London is temporarily different. New York goes from being 5 hours behind London to being only 4 hours behind. If you have a recurring weekly meeting during that window, it will appear to move.

Australia does DST too — but because they're in the southern hemisphere, their summer is our winter. So when it's winter in New York and clocks fall back, it's summer in Sydney and clocks spring forward. The gap between them widens dramatically for part of the year.

And then there are places that simply don't bother with DST at all: India, China, Japan, most of Africa, Iceland, and Arizona in the US (yes, just Arizona — the Navajo Nation within Arizona does observe it, but the rest of the state doesn't, which creates its own little chaos). These places stay on a fixed offset year-round, which makes them surprisingly reliable anchor points when you're scheduling internationally.

A Practical Example: Scheduling Across Three Continents

Let's say it's January and you need to find a meeting time that works for:

  1. Someone in New York (UTC−5 in January)
  2. Someone in London (UTC+0 in January — they've also fallen back)
  3. Someone in Singapore (UTC+8, no DST ever)

New York's 9 AM is London's 2 PM and Singapore's 10 PM. That's already rough. Your New York colleague wants to be awake, your London colleague is fine, and Singapore is done with their workday. The painful truth of cross-continental scheduling is that someone usually ends up on the edge of their work hours. The goal isn't to find a perfect time — it's to find the least terrible time and rotate who bears the inconvenience.

A good rule of thumb: look for overlap in the late morning of your westernmost participant. That tends to land in the late afternoon or early evening for Europe and somewhere workable for Asia-Pacific, depending on how far east you're reaching.

Tools That Actually Help

You don't need to do this math in your head every time. A few tools make this dramatically easier:

  • World Time Buddy — visual overlap tool, free, lets you drag across the day to find common working hours
  • Every Time Zone — clean single-page visualization of where each time zone sits right now
  • Google Calendar — when you add a guest from a different time zone, it shows their local time in the invite. Use it.
  • Time Zone Converter tools — simple "what time is it in X when it's Y in Z" — fast for one-off checks

The single most useful habit you can build: always write times with the time zone explicitly attached. Instead of "let's meet at 3 PM," write "3 PM EST" or even better "3 PM UTC−5." It takes two seconds and eliminates 90% of scheduling confusion.

The One Piece of Advice That Actually Sticks

When in doubt, convert everything to UTC first. It's the neutral ground. If you and a colleague both know how to read UTC, you can compare without anyone needing to know the other person's local time zone at all. "Let's meet at 14:00 UTC" is unambiguous in a way that "let's meet at 2 PM" simply isn't.

Time zones exist because of physics — the Earth spins and we all have to agree on what "noon" means locally. UTC is the common language we built on top of that physics. Offsets tell you how far each location sits from that baseline. And DST is the chaotic human patch that got layered on for political and agricultural reasons and has caused scheduling confusion ever since.

Once you understand those three layers — the spinning Earth, the UTC baseline, and the seasonal DST shuffle — you're not confused by time zones anymore. You're just doing arithmetic. And arithmetic, at least, you can always look up.