UTC and GMT Explained

You have probably seen both “UTC” and “GMT” used to describe the same time — on flight tickets, in software logs, in meeting invites. They are nearly identical in practice but come from very different origins, and the distinction matters in some technical and legal contexts. This guide explains what both mean and when each is used.

What is GMT?

Greenwich Mean Time (GMT) is the time observed at the Royal Observatory in Greenwich, London. It was established as the international reference point in 1884 at the International Meridian Conference in Washington, D.C., when delegates from 25 nations voted to make the Greenwich meridian (0° longitude) the prime meridian — the line from which all longitudes and time zones are measured.

GMT is an astronomical time standard, meaning it is based on the rotation of the Earth relative to the Sun. Because the Earth’s rotation is not perfectly uniform — it wobbles and gradually slows — GMT can drift by fractions of a second over time.

What is UTC?

Coordinated Universal Time (UTC) is the modern international time standard, introduced in 1960 and formally adopted worldwide in 1972. Unlike GMT, UTC is based on atomic clocks rather than Earth’s rotation. Atomic clocks measure time by the vibration of cesium atoms, which are accurate to about one second in 300 million years.

Because atomic time and astronomical time slowly drift apart, UTC is kept in sync with Earth’s rotation by the occasional addition of a “leap second.” The International Earth Rotation and Reference Systems Service (IERS) announces leap seconds when the difference between atomic time and solar time approaches 0.9 seconds. As of 2025, 27 leap seconds have been added since 1972.

UTC vs GMT: what is the practical difference?

For everyday purposes, UTC and GMT show the same time — both are 0:00 when it is noon at the Greenwich meridian. The difference only matters in narrow technical contexts:

• Precision: UTC is more precise. It is maintained by atomic clocks and kept within 0.9 seconds of astronomical time. GMT can drift by up to a few seconds between leap second adjustments.
• Leap seconds: UTC has them. GMT does not define a mechanism for leap seconds.
• Legal use: Some jurisdictions (notably the UK and Commonwealth countries) still cite GMT in legislation. UTC is the standard in aviation, meteorology, and international communications.
• Software: All modern operating systems and programming languages use UTC internally. You will almost never encounter true astronomical GMT in software.

How UTC offsets work

Every time zone in the world is defined by its offset from UTC — the number of hours (and sometimes minutes) ahead of or behind UTC. The notation is UTC+X or UTC−X:

• UTC+0 — Greenwich/London in winter (GMT)
• UTC+1 — London in summer (BST), Paris/Berlin in winter (CET)
• UTC+5:30 — India Standard Time (IST) — note the 30-minute offset
• UTC+5:45 — Nepal Standard Time — a 45-minute offset
• UTC−5 — US Eastern Standard Time (EST)
• UTC−4 — US Eastern Daylight Time (EDT), active in summer
• UTC+14 — The Line Islands (Kiribati) — the furthest ahead of UTC
• UTC−12 — Baker Island — the furthest behind UTC

The world spans UTC−12 to UTC+14, a range of 26 hours — which means at any given moment, up to three calendar dates can be simultaneously current in different parts of the world.

Why software stores times in UTC

When you store a local time without its UTC offset, you lose information. “3:00 PM” by itself is ambiguous — it could mean 3:00 PM in New York (UTC−5), 3:00 PM in London (UTC+0), or 3:00 PM in Tokyo (UTC+9), each representing a completely different moment in time.

UTC eliminates this ambiguity. A UTC timestamp represents exactly one moment in time, regardless of where the reader is located. When displaying the time to a user, software converts from UTC to the user’s local timezone. This is why server logs show UTC, why databases store UTC, and why email headers include UTC timestamps with offsets.

The ISO 8601 standard represents this as: 2026-06-15T14:30:00Z(the “Z” means UTC), or with an explicit offset:2026-06-15T09:30:00-05:00.

Converting between local time and UTC

To convert your local time to UTC, subtract your UTC offset. To convert UTC to your local time, add your offset:

• New York in summer (UTC−4): 3:00 PM EDT = 3:00 + 4 = 7:00 PM UTC
• London in winter (UTC+0): 3:00 PM GMT = 3:00 PM UTC (no conversion needed)
• Mumbai (UTC+5:30): 3:00 PM IST = 3:00 − 5:30 = 9:30 AM UTC
• Tokyo (UTC+9): 3:00 PM JST = 3:00 − 9 = 6:00 AM UTC

Use the timezone converter to do these conversions instantly for any city and any time.

A note on abbreviations

The abbreviation “UTC” is itself a compromise. English speakers wanted “CUT” (Coordinated Universal Time) while French speakers wanted “TUC” (Temps Universel Coordonné). The International Telecommunication Union settled on “UTC” — an abbreviation that fits neither language perfectly — as a language-neutral compromise.