UTC vs. GMT: What's the Actual Difference?

	GMT (Greenwich Mean Time)	UTC (Coordinated Universal Time)
What it measures	Mean solar time at the Royal Observatory, Greenwich	Atomic time, kept within 0.9 seconds of solar time
Basis	Astronomical observation	Atomic clocks (via International Atomic Time, TAI)
Adjusted how	Not adjusted for leap seconds	Leap seconds inserted periodically
Is it a time zone?	Yes — the UK’s winter time zone	No — it’s a time standard, not a zone
Used for	Everyday reference, UK civil time	Aviation, computing, navigation, science
Practical difference from local clock time	Can differ from true solar time by a small, fixed amount depending on definition	Effectively identical to GMT for most everyday purposes

For almost every day-to-day purpose, GMT and UTC tell the same time. The difference between them is a technicality that matters to physicists, network engineers, and international standards bodies — but understanding it clears up a common source of confusion: why software documentation insists on “UTC” instead of the more familiar “GMT.”

Why “mean” time, specifically

The word “mean” in Greenwich Mean Time is a specific technical term, not a casual qualifier. True solar time — literally when the sun crosses the meridian each day — varies slightly day to day across the year, because the Earth’s orbit isn’t a perfect circle and its axis is tilted, which together mean solar noon drifts by up to roughly 15 minutes either side of clock noon over the course of a year (an effect astronomers call the equation of time). “Mean” time averages this out into a smooth, consistent 24-hour day rather than one that lengthens and shortens with the seasons, which is what made GMT usable as a stable civil time standard in the first place rather than a value that would have shifted slightly every single day.

GMT is older, and it’s astronomical

Greenwich Mean Time dates back to the 19th century, when it was defined by the average time the sun crossed the meridian running through the Royal Observatory in Greenwich, London. It became the world’s reference point for civil time after the International Meridian Conference of 1884 recommended it as the basis for a global standard, and railway and telegraph networks adopted it because they needed one shared clock instead of thousands of local solar times that varied town to town.

GMT is fundamentally tied to the Earth’s rotation. The problem is that the Earth’s rotation is not perfectly constant — it slows down and speeds up slightly due to tidal friction, changes in the planet’s core, and other geophysical effects. A time standard based purely on watching the sun is precise enough for daily life but not precise enough for modern science, satellite navigation, or telecommunications, all of which need a clock that doesn’t drift with geology.

UTC is the atomic-clock successor

Coordinated Universal Time was introduced in the 1960s and formalized in its current form in 1972. It’s derived from a network of atomic clocks around the world (combined into International Atomic Time, or TAI), which tick with extreme regularity because they’re based on the vibration frequency of cesium atoms rather than the Earth’s rotation.

The catch is that an atomic clock and the Earth’s rotation slowly drift apart. If UTC just followed TAI exactly, clocks would eventually be out of sync with the actual day-night cycle — noon would gradually stop meaning “the sun is roughly overhead.” To prevent that, the international timekeeping authority inserts an occasional leap second into UTC to nudge it back into alignment with the Earth’s rotation, keeping UTC within 0.9 seconds of the older, solar-based standard. More than two dozen leap seconds have been added since 1972, most recently in December 2016.

That reliance on leap seconds has itself become a point of debate. In 2022, the international body responsible for time standards (the General Conference on Weights and Measures) voted to phase out leap seconds by 2035, since they cause headaches for computer systems that don’t expect a minute to occasionally contain 61 seconds. Whatever replaces the current leap-second mechanism, the practical effect for everyday users will be invisible — UTC will continue to track civil time closely.

How computers actually get the correct time

None of this matters much unless a device’s clock is accurate to begin with, and that accuracy comes from a different but related piece of infrastructure: the Network Time Protocol (NTP). Most computers, phones, and servers periodically synchronize their internal clock against NTP time servers, which are themselves ultimately referenced against UTC. This is why, in practice, essentially every device you own agrees on the current time down to a fraction of a second, without anyone manually setting a clock — the whole chain, from atomic clocks through NTP servers down to your laptop, is built around UTC as the shared reference, with GMT playing no functional role in that infrastructure at all beyond being numerically equivalent for everyday purposes.

So which one should you actually say?

In casual conversation, “GMT” and “UTC” are interchangeable — nobody will misunderstand you if you tell a colleague a meeting is “3pm GMT” versus “3pm UTC,” because the two are the same clock time in practice for the entire span of a human lifetime’s worth of leap seconds. The confusion mostly comes from one extra wrinkle: GMT is also the name of the UK’s winter time zone (the UK switches to British Summer Time, one hour ahead, from late March to late October), so “GMT” sometimes refers to a specific country’s local time rather than the global standard. UTC never changes with the seasons anywhere — it has no daylight saving time, by definition.

That’s exactly why technical systems should say UTC and not GMT:

• UTC is unambiguous. It isn’t tied to any single country’s civil calendar, so it can’t accidentally shift by an hour because a legislature changed a DST rule.
• UTC is the actual standard behind the scenes. Timestamps in databases, log files, and APIs are virtually always UTC even when they’re labeled “GMT” in a legacy system, because UTC is the modern definition that all major operating systems, programming languages, and network protocols implement.
• Aviation and the military already settled on this. Pilots and air traffic controllers use “Zulu time” (denoted with a “Z” suffix, as in 14:00Z), which is UTC — chosen specifically because it removes local-time ambiguity when a flight crosses a dozen time zones. The ISO 8601 date-time standard used across computing does the same thing, appending Z to a timestamp to mean UTC.

If you’re writing code, designing an API, or storing timestamps anywhere, the rule is simple: store and transmit everything in UTC, and only convert to a local time zone at the moment you display it to a person. That single habit sidesteps an entire category of bugs caused by daylight saving time changes, ambiguous local clock readings, and countries adjusting their own time zone rules with little advance notice. Our companion article on why developers should store UTC goes into the specific bugs this convention avoids. And if you just need to know what time it is right now somewhere else in the world, the time zone converter on this site does the UTC-to-local conversion for you, using the IANA time zone database rather than a hand-maintained offset table.