UTC vs GMT vs Zulu Time: The Real Difference Explained

For everyday purposes, UTC and GMT show the same time: 12:00 UTC is 12:00 GMT. The difference is what they are. UTC (Coordinated Universal Time) is the world’s time standard, kept by atomic clocks and published by the BIPM in France. GMT (Greenwich Mean Time) is the old astronomical standard based on the Sun at Greenwich, and today it is mainly the name of a time zone: the winter time of the UK, Ireland’s winter time label, and the all-year time of countries such as Iceland and Ghana. Zulu time (“Z”) is simply UTC as written by pilots, the military and weather services. The one practical trap is the UK: London is on GMT only from late October to late March and on BST (UTC+1) the rest of the year, while UTC never changes. This guide explains the differences, the leap seconds that link them, and a big change coming on May 20, 2027. Facts are as of November 2026.

At a glance

  • UTC = GMT on the clock, to within a second. UTC is the standard; GMT is now a time zone name.
  • UTC never has daylight saving time. London does: in 2027 it is on GMT for 148 days and on BST (UTC+1) for 217 days.
  • Zulu time, written “Z” (as in 1400Z), means UTC.
  • UTC is 37 seconds behind atomic time (TAI) after 27 leap seconds since 1972.
  • From May 20, 2027, UTC will run continuously with no more leap seconds (BIPM, CGPM Resolution 5, 2026).

UTC vs GMT vs Zulu side by side

UTC GMT Zulu (Z)
What it is The international time standard A time zone name (formerly the world standard) A military and aviation name for UTC
Based on Atomic clocks, kept close to Earth’s rotation Historically, the mean Sun at Greenwich; today, UTC+0 UTC
Daylight saving time Never No, but the UK switches from GMT to BST in summer Never
Who uses it Computers, science, aviation, the internet UK, Ireland (winter), Iceland, much of West Africa Pilots, military, weather forecasts
How to write it 14:00 UTC, UTC+5:30 14:00 GMT, GMT+1 1400Z

What GMT is, and why it was replaced

The Royal Observatory Greenwich defines GMT as “the yearly average (or ‘mean’) of the time each day when the Sun crosses the Prime Meridian” at Greenwich. Greenwich was recommended as the world’s prime meridian in 1884, and GMT served as the international standard of civil time until 1972, according to the same Royal Museums Greenwich page. The problem is that the Sun is not a perfect clock: Earth’s rotation speeds up and slows down by tiny amounts. Atomic clocks are far steadier, so in 1972 the world moved to UTC, an atomic time scale that is nudged to stay close to the Sun.

GMT did not disappear. UK law still says that, unless stated otherwise, a time in an Act “be held to be Greenwich mean time” (subject to summer time), and many countries keep “GMT” as the name of their UTC+0 zone. In the time zone database your phone uses, London, Dublin, Reykjavik and Accra all show the label “GMT” in winter.

What UTC is, and how leap seconds linked the two

UTC ticks at the rate of atomic time, but until now it has been kept within 0.9 seconds of Earth-rotation time. NIST explains that “Leap seconds are added in order to keep the difference between UTC and astronomical time (UT1) to less than 0.9 seconds.” That is why UTC and GMT can be treated as the same: the gap between them has never been allowed to reach a full second.

From the official leap second file in the time zone database (leap-seconds.list, version 2026e), we counted 27 leap seconds since UTC started with a 10-second offset in 1972, so UTC is now 37 seconds behind International Atomic Time (TAI). The IERS, which monitors Earth’s rotation, confirms “UTC-TAI = -37 s” and that “NO leap second will be introduced at the end of December 2026”. The last one was added at the end of December 31, 2016. The US Naval Observatory states that “GPS is ahead of UTC by 18 seconds”, and that TAI is ahead of GPS by 19.

The 2027 change: no more leap seconds

In October 2026, the General Conference on Weights and Measures (CGPM) adopted Resolution 5, which “decides that continuous UTC will become effective on 20 May 2027” and that the maximum allowed difference between UT1 and UTC will be 3 600 seconds (1 hour). In practice, UTC will stop being adjusted to the Sun second by second, and the gap will be allowed to grow very slowly. For anyone reading a clock nothing changes: UTC and GMT will keep showing the same hour and minute for many decades. It matters for astronomers, navigation systems and software that had to handle the odd 61-second minute.

The real-world trap: London is not always on GMT

People often write “GMT” when they mean “London time”. That is only right in winter. The UK changes clocks on these 2027 dates (computed from the tz database):

Period in 2027 London time Offset
January 1 to March 27 GMT UTC+0
March 28 to October 30 BST (British Summer Time) UTC+1
October 31 to December 31 GMT UTC+0

So a webinar “at 15:00 GMT” in July is at 16:00 on London clocks. If you mean London, write “London time” or “UK time”. If you mean the fixed world reference, write UTC. Our GMT page and UTC page show the live time for each.

Zulu time: reading 00Z and 12Z

The US National Weather Service bases its data and product times on UTC, “formerly known as Greenwich Mean Time [GMT] or Zulu {zero} Time [Z]”, and adds a “Z” to show it. Weather products often refer to 00Z and 12Z. Here is what those mean on local clocks, computed for mid-January and mid-July 2027:

City 00Z, January 15 12Z, January 15 00Z, July 15 12Z, July 15
Los Angeles 4 PM (previous day) 4 AM 5 PM (previous day) 5 AM
Vancouver 5 PM (previous day) 5 AM 5 PM (previous day) 5 AM
New York 7 PM (previous day) 7 AM 8 PM (previous day) 8 AM
London 12 AM (midnight) 12 PM (noon) 1 AM 1 PM
India 5:30 AM 5:30 PM 5:30 AM 5:30 PM
Tokyo 9 AM 9 PM 9 AM 9 PM
Sydney 11 AM 11 PM 10 AM 10 PM

Vancouver’s row is the same in both seasons because British Columbia stopped changing clocks in 2026 and now stays on UTC−7 (see our daylight saving time explainer).

“GMT+5” vs “UTC+5”, and a sign trap for developers

“GMT+5” and “UTC+5” mean the same thing: five hours ahead of UTC (for example Karachi). Many devices still say “GMT+” out of habit. One real trap is the time zone database’s fixed zones called Etc/GMT+5: by an old POSIX convention the sign is reversed, so Etc/GMT+5 is actually UTC−5, and Etc/GMT−3 is UTC+3. We confirmed both on this machine’s tz data. If you configure a server, pick a city zone such as America/New_York or plain UTC instead.

Which should you use?

  • Logs, databases, flight plans, APIs: UTC. It never jumps and every system understands it.
  • Talking about the UK: “UK time” or “London time”, or GMT in winter and BST in summer.
  • Invitations across countries: a local time plus offset, such as “3 PM UTC−5”, or our time zone converter.
  • Aviation, weather, military: Z, which is UTC.

How we checked

Offsets and labels come from the IANA tz database version 2026e via Python’s zoneinfo, cross-checked with the operating system’s date command. The leap second count comes from the leap-seconds.list file shipped with the same tz release and matches the IERS value of 37 seconds.

Sources

Frequently asked questions

Is UTC the same as GMT?

On the clock, yes, to within a second. Technically, UTC is the atomic world standard and GMT is a time zone name equal to UTC+0.

Is London on GMT or UTC?

London uses GMT (UTC+0) in winter and BST (UTC+1) in summer. In 2027 it is on BST from March 28 to October 30.

What is Zulu time now?

Zulu time is UTC. Check the live clock on our UTC page.

Does UTC change for daylight saving time?

No. UTC never changes; local times change relative to it.

Are leap seconds ending?

Yes. Under CGPM Resolution 5 (2026), UTC becomes continuous on May 20, 2027, so no further leap seconds are planned. The last one was at the end of 2016.

Why does my phone say GMT−5 instead of UTC−5?

Habit. Both mean five hours behind the world standard.

Similar Posts