UTC and GMT Explained: Time Zone Offsets in Plain English

Every world clock, flight schedule, and “what time is the call?” message quietly runs on one shared reference clock. Understand that clock — UTC — and time zones stop being confusing. Here is the plain-English version.

What is UTC?

UTC stands for Coordinated Universal Time. It is the single global reference from which every local time is measured. UTC never changes with the seasons, never “springs forward,” and is the same instant everywhere on Earth. When someone says an event is at 14:00 UTC, that is one exact moment — in London it might be 3 PM, in New York 10 AM, in Tokyo 11 PM, but it is the same instant for all of them.

Think of UTC as the master clock and your local time as UTC plus (or minus) a fixed number of hours. That number is your offset.

UTC vs GMT — what’s the difference?

For everyday purposes, GMT (Greenwich Mean Time) and UTC are the same time. Both put the reference meridian at Greenwich, London, and both read the same on your watch. The difference is technical: GMT is an older, astronomy-based time standard, while UTC is defined by extremely precise atomic clocks and is the modern international standard. Unless you are doing satellite navigation or astronomy, you can treat “3 PM GMT” and “15:00 UTC” as identical.

One common trap: in the UK, GMT only applies in winter. In summer the UK moves to British Summer Time (BST), which is UTC+1. So “London time” is not always GMT — a good reason to reason in UTC offsets rather than country abbreviations.

What an offset actually means

An offset is written as UTC+h or UTC−h and tells you how far ahead of or behind the reference clock a place is:

To find the difference between two cities, subtract their offsets. Dubai (UTC+4) minus London-in-summer (UTC+1) = 3 hours, so Dubai is 3 hours ahead of London during British Summer Time. Our London → Dubai time page shows that live, including the exact current gap.

Why “Europe/London” beats “BST”

Abbreviations like EST, PST, CET, and BST are ambiguous — several zones share the same letters, and they don’t tell you whether daylight saving is currently active. Software instead uses IANA time zone names such as Europe/London, America/New_York, or Asia/Dubai. Each IANA name carries the full history of that region’s offset changes and daylight-saving rules, so it is always unambiguous. Every clock on our World Clock is driven by IANA zones, which is why the offsets stay correct year-round.

Half-hour and 45-minute offsets

Not every zone is a whole number of hours from UTC. India runs on UTC+5:30, Nepal on the unusual UTC+5:45, and parts of Australia on UTC+9:30. These aren’t quirks to memorise — they’re just why you should let a converter do the arithmetic rather than rounding to the nearest hour. The World Clock converter handles half-hour and 45-minute offsets automatically.

Worked example: “UTC−4 to my time”

Suppose a webinar is listed as 18:00 UTC−4 and you want it in your own clock. Two steps:

  1. Convert the source to plain UTC. UTC−4 means the source is 4 hours behind UTC, so add 4 hours: 18:00 + 4 = 22:00 UTC.
  2. Apply your own offset. If you’re in Berlin (UTC+2 in summer), add 2: 22:00 + 2 = 00:00 — midnight the next day.

That two-step method — source → UTC → your zone — works for any pair of places and is exactly what the converter automates.

Convert your local time to UTC (and back)

Going the other way is the same idea in reverse: to turn your local time into UTC, subtract your offset if you’re ahead of UTC, or add it if you’re behind. Berlin at 09:00 in summer (UTC+2) is 07:00 UTC. Rather than doing this by hand every time, drop your zone and a target zone into the World Clock and read the answer directly — it also shows the working-hours overlap so you can pick a sensible meeting slot.

Next steps