GMT vs UTC: What's the Difference?

If you've ever looked at a world clock or a flight itinerary and seen both "GMT" and "UTC" used seemingly interchangeably, you're not imagining things. For the overwhelming majority of practical purposes — scheduling meetings, booking travel, setting calendar events — GMT and UTC are identical. They refer to the same moment in time, to a precision well within any margin that matters for human scheduling.

But they're not the same thing technically, and understanding the distinction is actually interesting: one is tied to the movement of the Earth, the other to the vibration of atoms. Here's what that means and when, if ever, the difference matters to you.

What GMT is

GMT stands for Greenwich Mean Time. It takes its name from the Royal Observatory in Greenwich, southeast London, which sits on the prime meridian — zero degrees longitude. Since the late 19th century, GMT has been the reference point from which all other time zones are measured.

The way GMT is defined is astronomical: it's the mean solar time at Greenwich, meaning the average time for the sun to cross the meridian at that location over the course of the year. "Mean" is important here — the sun doesn't actually reach its highest point at exactly the same moment each day due to the Earth's elliptical orbit and axial tilt, so GMT smooths this out into a consistent 24-hour cycle.

GMT was adopted internationally at the 1884 International Meridian Conference in Washington, DC, where 25 countries agreed to standardise time measurement and navigation around a single reference point. The Greenwich meridian was chosen largely because 72% of the world's shipping at the time already used it as the basis for navigation charts.

What UTC is

UTC stands for Coordinated Universal Time — and the abbreviation is intentionally a compromise. English speakers wanted "CUT"; French speakers, working from Temps Universel Coordonné, wanted "TUC". The international standards body settled on "UTC" as a three-letter code that neither language fully owns.

UTC was introduced in 1972, replacing GMT as the international civil time standard. Where GMT is based on the Earth's rotation, UTC is based on International Atomic Time (TAI) — a weighted average of signals from more than 400 atomic clocks maintained by national standards laboratories in over 50 countries, coordinated by the International Bureau of Weights and Measures in Paris.

Atomic clocks are extraordinarily precise. A modern caesium atomic clock will neither gain nor lose a second over hundreds of millions of years. The Earth's rotation, by contrast, is slightly irregular and has been gradually slowing over geological time — by about 1.4 milliseconds per day per century. This means that if you ran UTC and GMT side by side for long enough using their respective measurement methods, they would eventually diverge.

The one mechanism that keeps them aligned: leap seconds

Because UTC is based on atomic clocks and the Earth's rotation is not perfectly constant, the two would slowly drift apart if left uncorrected. To prevent this, the international timekeeping community occasionally inserts a "leap second" into UTC — an extra second added at the end of June or December to keep UTC within 0.9 seconds of UT1, the modern successor to GMT based on Earth rotation observations.

Since UTC was introduced in 1972, 27 leap seconds have been added. They're announced in advance by the International Earth Rotation and Reference Systems Service (IERS), and applied simultaneously worldwide at 23:59:60 UTC on the designated date — a moment that doesn't exist in ordinary timekeeping.

Leap seconds cause occasional headaches in computing and telecommunications: systems that assume every minute has exactly 60 seconds can malfunction when an unexpected one arrives. For this reason, a 2022 decision by the General Conference on Weights and Measures decided to eliminate leap seconds by 2035, instead allowing UTC and Earth-rotation time to drift apart by up to a minute before a larger correction is applied. The full implications of this are still being worked through by the timekeeping community.

Where you'll see GMT vs UTC in practice

The two terms show up in different contexts, which is one reason the distinction matters at all:

• UTC is used in computing, software, databases, network protocols, GPS satellites, scientific data, and any system where precision matters. When your phone stores a calendar event, it stores the underlying time in UTC. When a web server logs a request, it logs it in UTC. The reason is simple: UTC is unambiguous and doesn't change for daylight saving.
• GMT is used in everyday speech, particularly in the UK, in broadcasting schedules ("the programme airs at 21:00 GMT"), and in aviation weather reports (METARs, TAFs, and NOTAMs all use UTC, but aviation professionals often call it "Zulu time" — the NATO phonetic for Z, which is appended to UTC timestamps to mark them as universal).
• GMT offsets are still widely used for expressing time zones — "GMT+5:30" for India, "GMT-5" for New York in winter — even though the underlying standard is now UTC. You'll see both "GMT+1" and "UTC+1" used for the same offset; they mean exactly the same thing in this context.

The key practical difference: GMT can mean London's local time, UTC cannot

There is one subtlety worth noting. "GMT" is sometimes used loosely to mean the current time in London — but London is not always on GMT. The UK observes British Summer Time (BST, UTC+1) from late March to late October. During BST, London is UTC+1, not UTC+0. Saying "the meeting is at 3 PM GMT" in July is technically incorrect if you mean London time — London is on BST in July, so 3 PM London is 3 PM BST (= 14:00 UTC).

UTC, by contrast, is a fixed reference that never moves for daylight saving. "14:00 UTC" means the same moment regardless of what month it is or what any country's clocks are doing. This is why technical systems prefer UTC: it's completely stable.

Does the difference matter to you?

For the vast majority of everyday purposes — scheduling a video call, booking a flight, setting an alarm, reading a world clock — no. GMT and UTC are the same. You can use either term and be understood correctly.

It starts to matter in three specific situations:

1. You're writing software that stores or compares timestamps. Always use UTC internally. Never store local times without an offset. This is the single rule that prevents the largest category of time-zone bugs in software.
2. You need to be precise about London's time. "GMT" spoken in July probably means BST (UTC+1). Specify UTC+0 or UTC+1 to be unambiguous.
3. You're doing precision science or engineering where the difference between UTC and Earth-rotation time (UT1) matters at the sub-second level. For everything else, the gap is well under a second and entirely irrelevant.

The short version

GMT is the original: a solar time standard based on the meridian at Greenwich, adopted internationally in 1884. UTC is the modern replacement: an atomic-clock-based standard introduced in 1972, kept within 0.9 seconds of GMT by occasional leap seconds. For anything a human is scheduling, they're the same. For software and precision science, always use UTC — it's unambiguous, constant, and never moves for daylight saving.

More ZoneKit guides

• What is UTC? A plain-English guide to Coordinated Universal Time
• How daylight saving time disrupts remote teams
• The remote worker's complete guide to time zones
• Time difference between London and New York
• Convert UTC to EST
• Convert GMT to IST