UTC and GMT show the same time on the clock, but they are not the same kind of thing. GMT (Greenwich Mean Time) is a time zone based on the sun's position over the Greenwich meridian in London, while UTC (Coordinated Universal Time) is a global time standard kept by atomic clocks and adjusted with leap seconds. In everyday use, GMT and UTC+00:00 are interchangeable, which is why the whole UTC vs GMT question feels slippery: the difference is about authority and definition, not about what you read off a watch.
Content Table
What UTC actually is
UTC is the reference time scale the entire planet syncs to. It is produced by the International Bureau of Weights and Measures (BIPM) from a weighted average of roughly 400 atomic clocks in national labs around the world, then published as an official monthly bulletin.
Three things define it:
- It runs on atomic seconds. Its tick rate comes from International Atomic Time (TAI), which is based on the caesium-133 transition, not on the Earth's rotation.
- It gets nudged to match the Earth. Because the Earth's spin is slightly irregular, leap seconds are inserted so UTC never drifts more than 0.9 seconds from solar time (UT1).
- It is not a time zone. UTC has no country, no summer time, and no offset. Every civil time zone is defined as UTC plus or minus something: New York is UTC-05:00 in winter, Tokyo is UTC+09:00 all year.
The relationship between atomic seconds and the corrected civil scale is worth a read on its own if you work with precise timing: see why atomic time and coordinated time diverge.
What GMT actually is
GMT started as astronomy, not engineering. It is mean solar time at the Royal Observatory in Greenwich, meaning the average time it takes the sun to return to the same position over that meridian. Astronomers began publishing it in the 1840s, Britain's railways adopted it, and the 1884 International Meridian Conference made Greenwich the prime meridian for the world.
From 1884 to 1972, GMT was the global reference. Then it was retired from that job: on 1 January 1972, UTC in its current leap-second form took over as the basis for civil timekeeping worldwide.
GMT did not disappear, though. It survived as:
- A civil time zone equal to UTC+00:00, used in the UK in winter, plus Iceland, Ireland (as Irish Standard Time in summer), Portugal, Ghana, Senegal, and others.
-
A legacy label in protocols.
HTTP still requires the literal string "GMT" in date headers, as specified in
RFC 9110. A header reads
Date: Fri, 15 Nov 2024 08:12:31 GMT, but the value is really UTC. - Casual shorthand for "the zero meridian time" in news, aviation chatter, and schedules.
UTC vs GMT side by side
| Aspect | UTC | GMT |
|---|---|---|
| Type | Time standard / reference scale | Time zone (and a historic solar time scale) |
| Based on | Atomic clocks (TAI) plus leap seconds | Mean position of the sun over Greenwich |
| Maintained by | BIPM and IERS, with ITU-R recommendations | Originally the Royal Observatory; now just a zone label in the IANA tz database |
| Offset | None. It is the zero point. | UTC+00:00 |
| Daylight saving | Never | The zone itself does not shift, but countries using it switch to BST, IST, or WEST in summer |
| Official status since 1972 | Global civil time reference | No longer a scientific standard |
| Precision | Nanosecond-level, published in BIPM Circular T | Milliseconds at best, and ambiguous by definition |
Is GMT and UTC the same in practice?
For almost everything you will ever do, yes. If a webinar starts at 14:00 GMT and your calendar says 14:00 UTC, you will not miss it. The clock readings are identical to within a fraction of a second.
The times it genuinely matters:
- Satellite, GNSS, and geodesy work. Here "GMT" may be sloppily used to mean UT1, which is pure Earth-rotation time and can differ from UTC by up to 0.9 seconds. That is enough to move a GPS-derived position by hundreds of metres in some calculations.
- Astronomy and historical records. Before 1925, GMT was counted from noon, not midnight. A pre-1925 astronomical "GMT 1925 January 1.5" is not the same instant as a modern civil timestamp.
- Legal and regulatory texts. UK legislation still refers to Greenwich mean time as the legal basis for time, while financial and telecom rules typically cite UTC. Reading one as the other can create a genuine off-by-one-hour error when British Summer Time is active.
-
Software and APIs.
Some libraries treat "GMT" as an alias for UTC with a fixed zero offset, while others map it to the
Europe/Londonzone, which does observe summer time. That single ambiguity is the source of most real-world GMT bugs.
Europe/London
will silently shift every record by one hour from late March to late October. Store UTC, display local.
Leap seconds, the real technical difference
This is where UTC and GMT genuinely part company. GMT follows the Earth. UTC follows atoms and then gets corrected to stay near the Earth.
Because tidal friction and core-mantle coupling slowly change the length of the day, the IERS in Paris announces leap seconds about six months ahead. UTC has gained 27 leap seconds since 1972, and they are due to stop by 2035; the full history is in our guide to leap seconds.
If leap seconds are dropped, UTC will slowly pull away from true Greenwich mean solar time, and the "same clock" part of this comparison will finally start to crack. At current rates the gap would take many decades to reach a minute, so no one will notice without instruments.
Leap seconds also explain why POSIX time ignores them completely, which trips people up when converting epoch values: see how Unix timestamps handle UTC, timezones, and offsets.
The GMT time zone trap: GMT is not always UK time
People often use "GMT" as a synonym for "London time". It is only true for about five months of the year.
- Late October to late March: London is on GMT, which is UTC+00:00.
- Late March to late October: London is on British Summer Time, which is UTC+01:00.
So a meeting written as "9:00 GMT" in July is genuinely ambiguous. Did the organiser mean 9:00 UTC (10:00 in London) or 9:00 London time (8:00 UTC)? Our timezone converter shows both readings for any date. Both readings exist in the wild. Writing 09:00 UTC or 09:00 UTC+1 removes the guesswork, and a quick check against a multi-city clock comparison settles it in seconds.
The same logic applies to other GMT-zone countries. Ireland switches to Irish Standard Time (UTC+01:00) in summer. Portugal moves to WEST. Iceland, by contrast, stays on UTC+00:00 all year and never changes.
How to write a timestamp so nobody can misread it
Use the ISO 8601 /
RFC 3339
form with an explicit offset. The trailing
Z
("Zulu") means UTC.
2024-07-15T09:00:00Z # unambiguous: 09:00 UTC
2024-07-15T09:00:00+01:00 # unambiguous: 09:00 London summer time
2024-07-15 09:00 GMT # ambiguous in July, avoid
# Print current UTC from a shell
date -u +"%Y-%m-%dT%H:%M:%SZ"
# JavaScript
new Date().toISOString() // "2024-07-15T09:00:00.000Z"Which one should you use?
A simple rule: UTC for anything technical, GMT only when a format or law forces it.
-
Databases and logs:
store UTC, ideally as an epoch integer or a
timestamptzvalue. Never store a bare local time with a "GMT" label. -
APIs:
emit RFC 3339 with
Z. Date.prototype.toISOString() does this by default in browsers and Node. - HTTP headers and legacy email: keep the literal "GMT" string, because the spec mandates it. The underlying value is still UTC.
-
Time zone handling:
use IANA identifiers like
Europe/LondonorAmerica/Chicago, not the three-letter abbreviations. Abbreviations are not unique (IST means Irish Standard Time, Indian Standard Time, and Israel Standard Time). - Scheduling and cron: pin jobs to UTC so a daylight saving change does not run them twice or skip them.
- Debugging: convert suspect values back and forth with an epoch and UTC clock reference before assuming the code is wrong.
Machines get UTC from NTP servers, which distribute the standard down to millisecond accuracy over ordinary networks. If your clocks are drifting, that layer is usually the culprit: here is how NTP synchronization keeps clocks accurate.
In short: GMT is a place-based time zone with a long history and a fuzzy definition. UTC is the precisely defined standard that the whole world, including the GMT zone itself, is now measured against. Same clock face, very different authority.
Stop guessing whether "9:00 GMT" means UTC or London time
Our free world clock shows current times and UTC offsets side by side, so the UTC vs GMT confusion (and summer time shifts like BST) never costs you a meeting again.
Check times across time zones →
Frequently asked questions
Yes, the clock reading is the same. GMT as a civil time zone is defined as UTC+00:00, so both show identical hours, minutes and seconds. The difference is definitional: UTC is an atomic-clock standard, GMT is solar time at the Greenwich meridian used as a zone label.
The Earth's rotation is uneven, so solar-based GMT could not deliver the stable second that physics, telecoms and navigation needed. Caesium atomic clocks proved far more consistent, so from 1 January 1972 UTC took over, combining atomic stability with leap seconds to stay aligned with the sun.
Never. UTC is a fixed reference with no seasonal adjustment anywhere in the world. Daylight saving changes only the offset a country applies to UTC. London moves from UTC+00:00 to UTC+01:00 in summer, but UTC itself stays exactly where it is.
Z stands for "Zulu time", the NATO phonetic name for the zero offset. In ISO 8601 and RFC 3339 it marks the timestamp as UTC with no offset applied. It is functionally the same as writing +00:00, and it is the safest way to publish machine-readable times.
Backwards compatibility. The original HTTP date format predates widespread UTC labelling, and RFC 9110 still requires the literal string "GMT" so that decades of existing clients keep parsing correctly. The value itself is UTC, so no conversion is needed, only the legacy wording.