UTC vs GMT — What's the Difference, and Which Should You Use?

The short answer

For everyday purposes, UTC and GMT show the same time — if it's 12:00 UTC, it's 12:00 GMT. The difference is in how the time is defined:

• GMT (Greenwich Mean Time) is the older, astronomical standard: mean solar time at the Royal Observatory in Greenwich, London. It's defined by the Earth's rotation relative to the sun.
• UTC (Coordinated Universal Time) is the modern, atomic standard: time kept by a worldwide ensemble of atomic clocks, occasionally nudged to stay within 0.9 seconds of the Earth's actual rotation.

Since 1972, UTC has been the official basis of civil timekeeping worldwide. When precision matters — aviation, science, computing, international standards — the correct term is UTC. "GMT" survives mainly as the name of a time zone (the UK's winter time, also used in Iceland, Ghana, and elsewhere) and in everyday speech.

Why GMT came first

Britain's Royal Observatory at Greenwich became the world's timekeeping reference for a practical reason: navigation. To find your longitude at sea, you compare local solar time (measured from the sun) with the time at a known reference point — which requires carrying an accurate clock set to that reference. British ships carried chronometers set to Greenwich time, and the nautical charts most of the world used were drawn with Greenwich as 0° longitude. When the 1884 International Meridian Conference chose a global prime meridian, Greenwich was the natural pick, and GMT became the world's time anchor.

Why atomic clocks replaced the sky

There's a problem with defining time by the Earth's rotation: the Earth is a slightly unreliable clock. Tidal friction from the Moon gradually slows the rotation, and shifts in the planet's core, oceans, and atmosphere make the day irregularly longer or shorter by milliseconds. A "second" defined as 1/86,400 of a day is therefore a second that keeps changing length.

Atomic clocks solved this. Since 1967, the second has been defined by the vibration frequency of the caesium-133 atom — 9,192,631,770 oscillations, identical everywhere and always. International Atomic Time (TAI) is computed by averaging hundreds of atomic clocks in laboratories around the world, and it is stable to about a nanosecond per day.

Leap seconds: keeping atoms and sunrises in agreement

Perfectly uniform atomic time creates its own problem: if the Earth's rotation drifts while the atomic clock doesn't, then over centuries "noon" would slide away from the actual midday sun. The compromise is UTC: it ticks with atomic regularity, but whenever it drifts more than 0.9 seconds from Earth-rotation time, a leap second is inserted — a minute with 61 seconds, where clocks read 23:59:60.

Twenty-seven leap seconds were added between 1972 and 2016. They are notoriously disruptive to computer systems (several major internet outages have been traced to leap-second handling), and in 2022 the international metrology community voted to abandon them by 2035. Until then, UTC = TAI − 37 seconds.

What about "Zulu time"?

Zulu time (Z) is simply UTC in military and aviation notation. The NATO phonetic alphabet assigns letters to time zones; "Z" (Zulu) marks zero offset. A flight plan reading 1430Z means 14:30 UTC. You'll also see the "Z" suffix in the ISO 8601 timestamp format used by computers everywhere: 2026-07-07T14:30:00Z.

Converting UTC to your local time

Every time zone is defined as an offset from UTC. To convert, add your offset:

Two traps to watch for:

1. Daylight saving time changes the offset. New York is UTC−5 in winter but UTC−4 in summer. Never memorize a city's offset as a constant — check it live. (More in our DST guide.)
2. The date can roll over. 20:00 UTC on Friday is already 05:00 Saturday in Seoul. Always convert the date along with the hour.

Why UTC is the right tool for global coordination

UTC's killer feature is that it's unambiguous. "9 a.m. EST" forces everyone to remember what EST means, whether DST is active, and whether the writer actually meant EDT. "14:00 UTC" means exactly one moment, everywhere, forever. That's why pilots, servers, satellites, financial systems, and astronomers all log in UTC — and why, when you schedule across continents, anchoring on UTC (or on one explicitly named city) eliminates a whole class of mistakes.

On gworldtime, every one of our 337 cities is computed live from a network-synchronized UTC reference, so you can see any city's current local time — and its offset — without doing the arithmetic yourself.

Open the World Clock →

Read next: How time zones work · Daylight Saving Time explained · Atomic time, NTP, and leap seconds