UTC vs GMT: What’s the Difference?

By WorldTimeWise · Updated October 17, 2026

Ask someone the time in London in January and you might hear "it's noon GMT" or "it's noon UTC." Both are correct — and yet GMT and UTC are not quite the same thing. The difference is invisible in everyday life and crucial in a handful of technical fields. Here's the full story.

What GMT is

Greenwich Mean Time is the older of the two, and it began with the sun. In 1884, the International Meridian Conference in Washington, D.C. established the prime meridian — 0° longitude — at the Royal Observatory in Greenwich, England. GMT was defined as the mean (average) solar time at that meridian: essentially, noon GMT is when the sun is, on average, highest in the sky over Greenwich.

For most of the 20th century, GMT was the world's time standard. When the BBC broadcast the time, when navigators set their chronometers, when the world needed a common reference — it was GMT. The term is still everywhere: the UK's winter time zone is officially called GMT, and weather forecasts, shipping schedules, and plenty of software still label UTC+0 as GMT.

But GMT has a fundamental limitation: it's based on the Earth's rotation, and the Earth's rotation is not constant. Tidal friction from the moon is gradually slowing the planet down, earthquakes redistribute mass and nudge the spin rate, and seasonal shifts in the atmosphere cause small wobbles. A "second" defined by the Earth's rotation is a slightly elastic thing.

What UTC is

Coordinated Universal Time is the modern standard, and it's based on atoms, not astronomy. In the 1950s and 60s, physicists developed atomic clocks that measure time by counting the vibrations of cesium atoms — 9,192,631,770 oscillations per second, by definition. These clocks are stable to within a second over millions of years.

UTC was formally adopted in its current form in 1972. It combines the atomic precision of International Atomic Time (TAI) with occasional adjustments — leap seconds — that keep it within 0.9 seconds of the Earth's actual rotation. The odd name is a compromise: English speakers wanted "CUT" (Coordinated Universal Time) and French speakers wanted "TUC" (Temps Universel Coordonné), so everyone settled on UTC, which belongs to no language.

Today UTC is the standard that actually runs the world. Internet servers synchronize to it via NTP, GPS satellites broadcast it, airlines file flight plans in it (pilots call it "Zulu time"), and every time zone on Earth is formally defined as an offset from it — including, these days, GMT itself.

So what's the actual difference?

For everyday purposes: effectively nothing. Both describe the time at 0° longitude, and they never differ by more than about a second. If someone says a meeting is at "14:00 GMT" or "14:00 UTC," you will arrive at the same moment.

The technical difference is what each one *is*:

  • GMT is an astronomical time scale — mean solar time at Greenwich, now precisely defined as UT1 (a corrected measure of Earth's rotation angle).
  • UTC is an atomic time scale — counted by atomic clocks, with leap seconds inserted to track Earth's rotation approximately.

Think of it this way: GMT follows the Earth; UTC follows the atom, and glances at the Earth once in a while to stay roughly in sync.

When the distinction actually matters

There are a few domains where using the right term — and the right scale — is important:

  • Aviation and maritime navigation use UTC (as "Zulu") for all operations. A one-second ambiguity doesn't matter to a passenger, but air traffic control systems and flight data recorders need the precision.
  • Scientific and astronomical work sometimes needs UT1 (the modern GMT-equivalent) specifically, because telescopes and satellite tracking depend on the Earth's actual orientation in space, not atomic time.
  • Computing and timestamps should always use UTC. The Unix timestamp — the number of seconds since January 1, 1970 — is defined against UTC. Mixing up time scales in logs and databases is a classic source of subtle bugs.
  • Legal and contractual contexts in the UK often still say GMT, and that's fine — in winter, UK civil time *is* GMT, and in summer it's BST (British Summer Time, UTC+1).

If you're writing software, label it UTC. If you're telling a friend when to call, either works.

A brief word on leap seconds

Leap seconds are UTC's way of compromising between atoms and astronomy. Because Earth's rotation is gradually slowing, atomic time would slowly drift ahead of solar time. To prevent that, the International Earth Rotation and Reference Systems Service occasionally declares that a minute will have 61 seconds — usually at the end of June or December.

Twenty-seven leap seconds have been added since 1972, the most recent on December 31, 2016. They're announced only about six months in advance, because Earth's rotation is unpredictable enough that nobody can schedule them far ahead. Leap seconds have caused real incidents — in 2012, a leap second crashed systems at Reddit, LinkedIn, and several airlines, because software assumed every minute has 60 seconds.

The tech industry dislikes them enough that a decision was made in 2022 to abolish leap seconds by 2035, letting UTC drift from solar time very slowly instead (it would take centuries to matter for everyday life). Until then, UTC keeps its occasional extra second — and GMT, tracking the Earth directly, never needs one.

Which should you use?

Use UTC when precision, computing, or international coordination is involved — it's the current global standard, and it's what every time zone is defined against. Use GMT when you're talking about UK winter time, or in the casual contexts where the term is traditional and everyone understands it.

And if you ever need to convert between them and any other zone on Earth, the time zone converter handles it — treating them, correctly, as the same moment.