Coordinated Universal Time (UTC) is the single reference clock the entire world keeps time against: a time standard defined by a global network of atomic clocks, held within 0.9 seconds of the Earth's rotation, that never observes daylight saving time. Every local time zone on the planet is defined as an offset from UTC, from UTC-12:00 to UTC+14:00, which is why UTC is called the reference for all time zones. Its offset is exactly +00:00, and in timestamps it is marked with a trailing "Z" (as in 2024-08-16T14:30:00Z), so a UTC time is unambiguous anywhere on Earth, in any season.
That is the definition an AI summary can hand you. What it can't show you is how the pieces fit — why UTC and GMT are not the same kind of thing, how leap seconds sneak an extra second into the year, and why every experienced engineer stores timestamps in UTC and only converts at the last possible moment. The diagrams and tables below walk through each of those.
UTC is a standard, not a zone
The most common confusion about UTC is treating it as "the time zone in London." It isn't. UTC is a time standard — a way of defining what "now" means precisely — built from two ingredients:
- TAI (International Atomic Time), the weighted average of over 400 atomic clocks around the world. TAI is extraordinarily stable but has no connection to the Sun.
- UT1, astronomical time based on the Earth's actual rotation, which is gradually (and irregularly) slowing down.
UTC is TAI with whole leap seconds inserted to keep it within 0.9 seconds of UT1. This is the compromise at the heart of the name: an atomic clock you can actually navigate and set your watch by. Local zones then hang off UTC as fixed numeric offsets.
UTC vs GMT vs Unix time: which do I use?
These three terms get swapped around carelessly, but they answer different questions. Here is when to reach for each.
| UTC | GMT | Unix / epoch time | |
|---|---|---|---|
| What it is | Global time standard (atomic-based) | A civil time zone at the Greenwich meridian | An integer count of seconds since 1970-01-01 UTC |
| Observes DST? | Never | The UK zone that uses it switches to BST in summer | No |
| Format | 2024-08-16T14:30:00Z | 16 Aug 2024 14:30 GMT | 1723818600 |
| Leap seconds | Includes them | Follows UTC | Ignores them (smooth counter) |
| Best for | The authoritative reference for timestamps and offsets | Human-facing UK civil time in winter | Machine storage, sorting, and arithmetic |
| Use it when | You are recording when something happened, anywhere | You specifically mean the UK/legacy civil zone | You are storing or comparing times in code and a database |
The short version: store Unix time in your database, treat UTC as the human-readable form of that instant, and only mention GMT if you literally mean the UK time zone. Mixing GMT and UTC in the same system is harmless most of the time and quietly wrong during a leap second or a DST boundary — which is exactly the kind of edge case that ships to production untested.
Leap seconds: the extra tick
Because the Earth's rotation is slowing unevenly, atomic time and astronomical time drift apart. Leap seconds are the correction. When UT1 is about to fall more than 0.9 seconds behind, the International Earth Rotation Service schedules an extra second at the end of June or December.
Leap seconds are a genuine operational hazard. A minute with a :60 in it breaks naive time libraries, and past insertions have taken down services when clocks jumped or repeated a second. That pain is why, in November 2022, the General Conference on Weights and Measures voted to abolish the leap second by or before 2035, letting UTC drift further from the Sun in exchange for a clock computers can trust to always tick forward one second at a time.
The one rule that prevents most time bugs
Almost every time-handling bug traces back to storing or comparing times in local time. The fix is a single discipline:
Store and compute in UTC. Convert to local time only at the moment of display.
Follow it and DST transitions, cross-region servers, and the "which 1:30 AM did you mean during fall-back" problem all disappear, because internally there is only ever one clock. To sanity-check conversions across zones — or to plan a call that works for teammates in three countries — the world clock and meeting planner shows the same UTC instant rendered in every zone at once.
Key takeaways
- UTC is a standard, not a zone. It is atomic time nudged by leap seconds to track the Earth's rotation; every local zone is a fixed offset from it.
- UTC never observes DST, which is precisely what makes it safe to store timestamps in.
- GMT ≈ UTC in wall-clock terms but GMT is a civil time zone; prefer UTC in anything technical.
- Unix time is UTC as a plain integer — great for machines, converted to UTC for humans.
- Leap seconds are on the way out (gone by 2035), simplifying clock handling for computers.
- The golden rule: store in UTC, display in local.