UTC vs GMT explained

UTC and GMT look interchangeable on a calendar invite, but they are not the same thing. UTC is a precise time standard derived from atomic clocks; GMT is a time zone historically based on the position of the sun over the Greenwich meridian. For 99% of everyday use they tick at the same instant — but the words mean different things, and getting them right matters in software, broadcasting and aviation.

What is GMT?

Greenwich Mean Time was originally the mean solar time at the Royal Observatory in Greenwich, London. It became the global civil time reference in 1884 when the Royal Observatory was chosen as the prime meridian. For most of the 20th century, GMT was both a time zone (covering the British Isles in winter) and a de-facto international standard.

Today, GMT is best understood as the local time zone of the United Kingdom in winter, sitting at UTC+0. From late March to late October the UK shifts to British Summer Time (BST, UTC+1), so calling something "GMT" in July is technically incorrect — the actual UK clock is on BST.

What is UTC?

Coordinated Universal Time was introduced in 1972 to replace GMT as the world's primary time standard. UTC is generated by a network of atomic clocks coordinated by the Bureau International des Poids et Mesures (BIPM) and the International Earth Rotation and Reference Systems Service (IERS). It is adjusted with occasional leap seconds to keep it within 0.9 seconds of mean solar time.

Crucially, UTC is not a time zone. Nobody's local clock is set to UTC for civil purposes. UTC is the reference against which all other time zones express their offset (UTC+5:30 for India, UTC−5 for Eastern Time, and so on).

Are UTC and GMT exactly the same?

Almost, but not quite. UTC and GMT both have an offset of 0 from the prime meridian, and for 99% of everyday clocks they show the same time. The differences are:

• Source. GMT is astronomical (mean solar time at Greenwich). UTC is atomic (a weighted average of hundreds of atomic clocks).
• Stability. GMT drifts slightly with the rotation of the Earth. UTC is held tightly stable through leap seconds.
• Use. GMT is a time zone, used by the UK and a handful of African countries. UTC is the time standard used by every networked computer, aircraft and satellite.

When to use which

• Software timestamps and logs: always UTC.
• API responses and database storage: always UTC, ideally ISO 8601 (e.g. 2026-04-27T14:00:00Z).
• Scheduling a meeting in the UK: use BST in summer or GMT in winter, not "UTC".
• Aviation and broadcasting: UTC, often spoken as "Zulu time".
• Marketing copy and casual conversation: GMT is fine, but be aware it will confuse readers in summer if the UK is actually on BST.

Common mistakes

1. Saying "GMT" when you mean current UK time. In July the UK is on BST (UTC+1), not GMT. A 09:00 GMT meeting in July is actually 10:00 in London — an easy way to be an hour late.
2. Storing timestamps as "GMT". Storage should be UTC, with an offset or zone identifier if local time matters. The string "9 PM GMT" is ambiguous twice a year.
3. Treating UTC as a country. UTC has no clocks, no holidays and no daylight saving. It is a coordinate, not a place.

Why this matters in code

If you use the IANA time zone database (the source of truth used by every modern operating system), you'll see Europe/London rather than GMT. Europe/London correctly switches between GMT and BST. Etc/GMT exists too, but it represents a fixed offset of zero and never changes — which is rarely what an end user actually wants.

FAQ

Related guides

• UTC vs local time explained
• What is UTC?
• Time zone abbreviations
• Daylight saving and meetings