UTC, GMT and Zulu Time: What the Difference Actually Is

The one sentence answer

UTC is the modern reference standard for civil time, kept by atomic clocks. GMT is a solar time standard from the nineteenth century that is also, confusingly, the winter time of the United Kingdom. Zulu is the military and aviation name for UTC. In everyday use they point at the same instant, so if you are booking a meeting you can treat them as identical.

Where they came from

Greenwich Mean Time was defined by the sun: the mean solar time at the Royal Observatory in Greenwich. It was adopted as an international reference in 1884 because Britain had the shipping and the charts, and the world needed a common meridian to make sea navigation and railway timetables work.

The problem is that the earth is not a good clock. Its rotation is slightly irregular and slowly slowing, so solar time drifts against anything measured physically. Once atomic clocks arrived in the middle of the twentieth century it became possible to measure time far more precisely than the planet could keep it.

Coordinated Universal Time, introduced in 1960 and given its current form in 1972, resolves this. It runs on atomic seconds, and occasionally a leap second is inserted to keep it within a second of solar time. The compromise name UTC exists because English speakers wanted CUT and French speakers wanted TUC, so the standards body picked neither.

Why GMT is genuinely ambiguous

GMT does double duty and this is the real source of confusion.

Used as a standard, GMT means the zero meridian reference. Used as a time zone, GMT is what the United Kingdom is on from late October to late March. In summer the UK is on British Summer Time, UTC+1. So "10:00 GMT" in July is not "10:00 in London". London is an hour ahead of GMT at that point.

This bites people who write GMT when they mean London. If you mean the city, write London. If you mean the standard, write UTC.

Zulu

Aviation, shipping and the military need a time reference that cannot be misread across nationalities, so they use UTC and label it with a single letter. Each fifteen degree band of longitude gets a letter, and the zero meridian band got Z. In the NATO phonetic alphabet Z is Zulu, so UTC became Zulu time, written as 1430Z.

You will also see the Z in machine readable timestamps. An ISO 8601 string like 2026-08-06T14:30:00Z means half past two in the afternoon UTC. That trailing Z is the same convention, and it is the reason a timestamp with no Z and no offset is ambiguous and should be treated with suspicion.

When the difference matters

For scheduling, it does not. For anything that gets audited or replayed, it can.

Log files and databases. Store timestamps in UTC with an explicit offset or a trailing Z. A log line recorded in local time is nearly useless once daylight saving moves, because one hour occurs twice a year and one hour never occurs at all. Debugging an incident that spans a clock change with local timestamps is genuinely painful.

Deadlines. A contract or filing deadline written as "17:00 GMT" is ambiguous in summer. Written as "17:00 UTC" it is not.

Leap seconds. If you work with precise timing, note that UTC has had leap seconds added and that the practice is scheduled to be discontinued by 2035. Systems that assume every minute has sixty seconds have failed on leap second days before.

Practical rules

Write UTC when you mean the reference standard. Write the city name when you mean a place. Avoid GMT in anything that will be read in summer. Store machine timestamps in UTC and convert only for display.

To see what a UTC moment is in the cities you care about, put them side by side in the time zone converter, which shows the offset in force on the date you pick rather than a remembered average.

About the author

Nishanth Narayanan builds and maintains GlobalTimeTools from Coimbatore, India. He works with distributed teams across Indian, European and US time zones, which is where most of these questions came from.