UTC vs GMT: How the World Keeps Time

Every clock on Earth is really measuring its distance from one shared reference. That reference is UTC — Coordinated Universal Time. Once you understand UTC, the whole tangle of world time turns into simple arithmetic: your local time is just UTC plus or minus a few hours.

The idea of a single reference

Imagine trying to agree on a meeting time if everyone measured hours differently. You need one master clock everybody trusts, and then each region describes itself in relation to it. UTC is that master clock. New York is "UTC minus 5 hours" in winter. Tokyo is "UTC plus 9." India is "UTC plus 5 and a half." Every zone is a signed offset from the same origin.

What UTC actually is

UTC is not set by watching the sun. It is kept by a global network of extremely precise atomic clocks, averaged together to produce a single, rock-steady timescale. Because the Earth's rotation is slightly irregular, UTC occasionally has a leap second added to keep it aligned with the planet's actual spin. For everyday purposes you never notice this — but it is why UTC is considered a scientific standard rather than just "London time."

So where does GMT come from?

GMT — Greenwich Mean Time — is the older idea. It was defined by the Royal Observatory in Greenwich, London, based on the moment the sun crossed the meridian there. In the 19th century, as Britain's railways and navy standardized on Greenwich, it effectively became the world's timekeeper. When international time zones were formalized, they were all defined as offsets from Greenwich.

For decades, GMT was the reference. UTC was introduced in the 20th century to put that reference on a rigorous atomic footing.

UTC vs GMT: the honest answer

In everyday use, UTC and GMT point to the same clock time — if it is 15:00 UTC, it is 15:00 GMT. The differences are technical:

• UTC is a precise standard kept by atomic clocks. It is what science, aviation, computing, and international coordination use.
• GMT is a time zone (and a historical standard). Today it is mostly used as the name of the zone covering the UK and parts of West Africa in winter.

A useful way to hold it in your head: UTC is the standard; GMT is a zone that happens to sit on it. If you are writing software or scheduling internationally, say UTC. If you are describing what time it is in London in January, GMT is fine.

Reading an offset

Offsets look intimidating but read plainly. "UTC+9" means add nine hours to UTC to get local time. "UTC-5" means subtract five. The half-hour and 45-minute zones simply add a fraction: India's UTC+5:30, Nepal's UTC+5:45.

If it is 12:00 UTC, then it is 07:00 in New York (UTC-5), 13:00 in Paris (UTC+1), 17:30 in Delhi (UTC+5:30), and 21:00 in Tokyo (UTC+9).

"Z" and "Zulu"

You will sometimes see a time written like 2026-01-15T09:00Z. That trailing Z means UTC — pilots and the military pronounce it "Zulu." It is shorthand for "this timestamp is in UTC, no offset applied," which removes all ambiguity about where in the world it was recorded.

Why computers store everything in UTC

Good software almost never stores your local time. It stores the moment in UTC and converts to local time only when showing it to you. Why? Because UTC never jumps. Local time does — it leaps forward and back for daylight saving, and governments occasionally change zone rules outright. By anchoring to UTC and converting at the last second, a system stays correct no matter where its users are or what their governments decide. This site works the same way: it reasons in absolute instants and renders each city in its own zone.