What Is UTC?
Coordinated Universal Time (UTC) is the primary time standard by which the entire world regulates clocks, schedules flights, timestamps financial transactions, and synchronizes computer networks. Every time you look at your phone, the time you see traces back to UTC â your device received a signal from a time server somewhere, and that server's authority ultimately derives from the global UTC standard.
UTC is maintained by the Bureau International des Poids et Mesures (BIPM) in Paris, which averages the output of more than 400 atomic clocks operated by over 80 national laboratories around the world. The result is a timescale so stable that it loses or gains less than a nanosecond per day. To put that in perspective: a UTC clock would drift by about one second every three million years.
Where Did the Name Come From?
The abbreviation "UTC" is deliberately weird. English speakers wanted "CUT" (Coordinated Universal Time). French speakers wanted "TUC" (Temps Universel CoordonnĂ©). The International Telecommunication Union, not wanting to give either language priority, settled on "UTC" â an abbreviation that doesn't properly match either name. It was a diplomatic solution, which is to say, it annoyed everyone equally.
You'll sometimes see UTC called "Zulu time," especially in military and aviation contexts. The NATO phonetic alphabet uses "Zulu" for the letter Z, and timestamps in UTC are marked with a "Z" suffix (as in 2026-03-13T15:30:00Z). A pilot saying "wheels up at fifteen-thirty Zulu" means 3:30 PM UTC, regardless of what local time zone the airport happens to be in.
UTC vs. GMT: What's the Difference?
UTC and GMT are often used interchangeably, and for everyday purposes they show the same time. But they're technically different standards with different foundations.
GMT â Greenwich Mean Time â is an astronomical standard. It's defined by the mean solar time at the Royal Observatory in Greenwich, England: basically, the average time at which the sun crosses the meridian at that location. GMT was the world's reference time from 1884 until UTC replaced it as the official standard in 1972.
The problem with GMT is that it depends on Earth's rotation, and Earth's rotation isn't constant. The planet wobbles. Tidal friction from the Moon gradually slows it down. Large earthquakes can shift mass around and change the rotation speed slightly (the 2011 TĆhoku earthquake shortened the day by 1.8 microseconds). For navigating sailing ships in the 19th century, none of this mattered. For synchronizing global telecommunications networks, it matters a lot.
UTC is based on atomic clocks â specifically, on the vibrations of cesium-133 atoms, which oscillate exactly 9,192,631,770 times per second. This frequency is so stable that it serves as the literal definition of the second. UTC gives us a timescale that doesn't depend on anything as fickle as a planet's spin.
How Leap Seconds Work
Here's the tension: UTC is based on atomic clocks, but we still want it to roughly match the sun's position in the sky. If we let UTC run purely on atomic time, it would gradually drift away from solar time as Earth's rotation slows. Over centuries, noon by the clock would no longer correspond to the sun being overhead.
The solution â introduced in 1972 â is the leap second. When the difference between atomic time and astronomical observations of Earth's rotation approaches 0.9 seconds, the International Earth Rotation and Reference Systems Service (IERS) announces a leap second. An extra second is inserted into the UTC timescale, usually at the end of June 30 or December 31. The clock reads 23:59:59, then 23:59:60 (a value that normally doesn't exist), then 00:00:00.
Since 1972, 27 leap seconds have been added. The most recent was December 31, 2016. Interestingly, no leap second has been needed since then â Earth's rotation actually sped up slightly in recent years, a trend that puzzled geophysicists. If the trend continued, we might have needed the first-ever negative leap second (removing a second), though that now seems unlikely.
Leap seconds are, frankly, a nightmare for software. The POSIX standard that underpins Unix-like operating systems defines a day as exactly 86,400 seconds. There's no concept of a 86,401-second day. Google handles this with a "leap smear" â distributing the extra second over a 24-hour period so that each second is slightly longer than normal. AWS does something similar. Other systems just insert the second, which can cause processes to see duplicate timestamps or clocks that appear to go backward. The 2012 leap second caused outages at Reddit, Cloudflare, and Qantas simultaneously.
The good news: the General Conference on Weights and Measures voted in 2022 to abolish leap seconds by 2035. After that, UTC and astronomical time will be allowed to diverge gradually, with corrections applied only when the gap reaches a much larger threshold â possibly a minute or more.
Why Developers Should Use UTC
If you write software that touches dates or times â and almost every application does â there's one rule that will prevent more bugs than any other: store timestamps in UTC, convert to local time only for display.
I've seen this advice ignored so many times, and it always ends in tears. A billing system that stores local times will double-charge or skip charges during DST transitions. A scheduling app that uses local timestamps can't reliably schedule a 2:30 AM event on the night clocks spring forward (because 2:30 AM doesn't exist that day). A logging system with local timestamps becomes impossible to sort correctly when events span multiple time zones.
UTC eliminates all of this. It never "springs forward" or "falls back." It never has an ambiguous hour. A UTC timestamp â whether expressed as an ISO 8601 string like 2026-03-13T15:30:00Z or as a Unix timestamp like 1741877400 â unambiguously identifies a single moment in the history of the universe.
The pattern is simple: your database stores UTC. Your backend processes UTC. The moment a timestamp needs to be shown to a human user, you convert it to their local timezone using the IANA timezone database. In JavaScript, that's Intl.DateTimeFormat with a timeZone option. In Python, it's datetime.astimezone(). In PostgreSQL, it's the AT TIME ZONE clause. The conversion happens at the last possible moment, as close to the user's eyeballs as you can get.
How UTC Gets to Your Devices
Your phone, your laptop, your server â they all know what time it is because they periodically ask a time server. The protocol they use is called NTP (Network Time Protocol), which has been around since 1985 and can synchronize clocks over the internet to within a few milliseconds.
NTP time servers are organized in a hierarchy called "strata." Stratum 0 devices are the atomic clocks themselves and GPS satellites (which carry atomic clocks). Stratum 1 servers are directly connected to these reference clocks. Stratum 2 servers synchronize from Stratum 1, and so on. Most consumer devices sync from Stratum 2 or 3 servers operated by companies like Apple, Google, and Microsoft, or by public pools like pool.ntp.org.
For applications that need even tighter synchronization â high-frequency trading, distributed databases, scientific experiments â there's PTP (Precision Time Protocol), which can synchronize clocks to within nanoseconds using specialized hardware. AWS offers a time synchronization service based on PTP that provides sub-microsecond accuracy to EC2 instances.
UTC in Everyday Life
You encounter UTC more than you probably realize. Aviation runs entirely on UTC â every flight plan, every air traffic control communication, every METAR weather report uses Zulu time. International shipping schedules are in UTC. Satellite communications use UTC. Financial markets coordinate settlement times using UTC.
Even your email headers contain UTC timestamps. The next time you view the raw headers of an email, look for the Date: field â it includes a UTC offset so that any email client, anywhere in the world, can display the correct local time when the message was sent.
The shift toward UTC as the universal reference has been one of the quiet triumphs of 20th-century standardization. Before UTC, international coordination relied on a patchwork of local times, astronomical conventions, and railroad schedules. Now, a timestamp like 2026-03-13T15:30:00Z means exactly the same thing to a server in Tokyo, a phone in Lagos, and a satellite orbiting over the Pacific.
Frequently Asked Questions
What does UTC stand for?
UTC stands for Coordinated Universal Time. The abbreviation is a compromise between the English "CUT" and the French "TUC" (Temps Universel Coordonne). The International Telecommunication Union chose "UTC" as a language-neutral acronym that does not perfectly abbreviate either language's name.
Is UTC the same as GMT?
For all practical purposes, yes. UTC and GMT both represent the time at the Prime Meridian (0 degrees longitude) with zero offset. The technical difference is that GMT is based on Earth's rotation (astronomical) while UTC is based on atomic clocks. They are kept within 0.9 seconds of each other through leap second adjustments.
What is a leap second?
A leap second is an extra second occasionally added to UTC to keep it synchronized with Earth's gradually slowing rotation. Since 1972, 27 leap seconds have been added. They are inserted at the end of June 30 or December 31. The ITU has proposed abolishing leap seconds by 2035.
Why should developers store timestamps in UTC?
Storing timestamps in UTC eliminates ambiguity caused by daylight saving time transitions, timezone differences, and political timezone changes. UTC provides a single, unambiguous reference point. Local time conversions should only be applied at the display layer.
Does UTC change with daylight saving time?
No. UTC never changes for daylight saving time. It remains constant year-round. Time zones are expressed as offsets from UTC, and those offsets change when a region enters or exits daylight saving time, but UTC itself stays the same.
What is the UTC offset?
A UTC offset is the difference in hours and minutes between a local time zone and UTC. For example, UTC-5 means 5 hours behind UTC (Eastern Standard Time), and UTC+5:30 means 5 hours and 30 minutes ahead of UTC (India Standard Time). Offsets range from UTC-12 to UTC+14.
How is UTC maintained?
UTC is maintained by the Bureau International des Poids et Mesures (BIPM) in Paris, which averages the output of over 400 atomic clocks in more than 50 national laboratories worldwide. This network of atomic clocks provides a timescale accurate to within nanoseconds.
Sources
- IERS: International Earth Rotation and Reference Systems Service (iers.org)
- BIPM: Bureau International des Poids et Mesures (bipm.org)
- ITU-R TF.460: Standard Frequencies and Time Signals