What is UTC?
UTC stands for Coordinated Universal Time. It is the global time standard against which every other time zone is measured. UTC isn't a country or a place — it's a coordinate. Whether you're checking server logs in Singapore, scheduling a flight from Sao Paulo to Frankfurt, or coordinating an online game, the underlying clock is UTC.
Where UTC comes from
UTC was introduced in 1972 to replace Greenwich Mean Time (GMT) as the international standard. While GMT was based on the average position of the sun over the prime meridian at Greenwich, UTC is generated by an ensemble of roughly 400 atomic clocks scattered across some 80 national laboratories. The Bureau International des Poids et Mesures (BIPM) in France blends those clocks into a single, ultra-stable timescale.
UTC stays close to mean solar time at Greenwich (within 0.9 seconds) by occasionally inserting a leap second. Leap seconds have been added roughly every 18 months on average, although the practice is being phased out and is expected to end by 2035.
Why is the acronym "UTC"?
Coordinated Universal Time should logically abbreviate to "CUT" in English or "TUC" in French ("Temps Universel Coordonné"). The acronym "UTC" was chosen as a compromise so that no single language got priority. It's an engineered acronym, not an oversight.
How UTC relates to your local clock
Every time zone in the world is defined as an offset from UTC. India is at UTC+5:30; New York City is at UTC−5 (or UTC−4 in summer); Tokyo is at UTC+9. When you read an email "Sent at 14:00 UTC", you can convert it mentally by adding or subtracting your offset.
| UTC | London | New York | Tokyo | Sydney |
|---|---|---|---|---|
| 00:00 | 00:00 / 01:00 | 19:00 / 20:00 (prev. day) | 09:00 | 10:00 / 11:00 |
| 06:00 | 06:00 / 07:00 | 01:00 / 02:00 | 15:00 | 16:00 / 17:00 |
| 12:00 | 12:00 / 13:00 | 07:00 / 08:00 | 21:00 | 22:00 / 23:00 |
| 18:00 | 18:00 / 19:00 | 13:00 / 14:00 | 03:00 (next day) | 04:00 / 05:00 (next day) |
(Pairs of values reflect winter / summer offsets where DST applies.)
Why every system uses UTC under the hood
UTC has three properties that make it unbeatable for software:
- It never repeats. Local time can repeat an hour each autumn when DST ends. UTC marches forward.
- It never skips. Local time can skip an hour each spring when DST starts. UTC keeps going.
- It's globally agreed. A timestamp in UTC means exactly the same instant in Tokyo, Lagos and Buenos Aires.
That's why server logs, database timestamps, GPS satellites, NTP servers, Bitcoin block headers and almost every networked protocol record time in UTC. Local time only enters the picture when the data is presented to a human.
What UTC is not
- Not a country's time zone. Iceland uses UTC+0 year-round and is the closest thing, but UTC itself is no one's local time.
- Not the same as GMT. They share an offset of zero, but UTC is an atomic standard while GMT is a historical solar zone.
- Not affected by DST. UTC never springs forward or falls back.
- Not "British time". The UK uses UTC+0 in winter and UTC+1 in summer.
Reading UTC timestamps
The most common machine-readable form is ISO 8601: 2026-04-27T14:00:00Z.
The trailing Z ("Zulu") explicitly marks UTC. Other valid forms
include 2026-04-27T14:00:00+00:00 and the older
2026-04-27 14:00 UTC. If you ever see a date with no zone, treat
it as suspicious — it could be local, server time or something else.
FAQ
Is UTC the same as GMT?
For practical purposes, yes — both have an offset of zero from the prime meridian. Technically, UTC is an atomic-clock standard, while GMT is a time zone.
Why does UTC have leap seconds?
To stay aligned with the actual rotation of the Earth, which slows down very slightly over time. Leap seconds keep UTC within 0.9 seconds of mean solar time at Greenwich.
What's the difference between UTC and Zulu time?
None. "Zulu time" is the aviation and military name for UTC, after the NATO phonetic letter Z used in ISO 8601 timestamps.