Work

What Is UTC and Why Does It Matter?

Coordinated Universal Time is the reference every time zone is defined against. It never changes for daylight saving, which is why it appears in flight times, server.

· 2 min read

What Is UTC and Why Does It Matter?

In short

UTC, Coordinated Universal Time, is the global reference time from which every time zone is defined as an offset. London is UTC+0 in winter and UTC+1 in summer; New York is UTC-5 or UTC-4. UTC itself never shifts for daylight saving, which is why it is used for aviation, computing, science and anything coordinated across borders, and why it is the safest way to state a time internationally.

Every time zone in the world is defined as an offset from one reference, and that reference is UTC. Understanding it explains most of the confusion that occurs when people in different countries try to agree on when something happens.

What it is

Coordinated Universal Time is the international time standard, maintained by a network of atomic clocks and adjusted by occasional leap seconds to stay aligned with the Earth’s rotation. It is the time at the Greenwich meridian, with no daylight saving ever applied.

Every zone is expressed relative to it. Central European Time is UTC+1. India is UTC+5:30. Japan is UTC+9. Eastern US is UTC-5. When a country applies daylight saving, its offset changes: the UK moves from UTC+0 to UTC+1 in summer, and the label changes from GMT to BST, but UTC itself stays exactly where it was.

UTC versus GMT

In daily life they are interchangeable. Both mean the time at Greenwich without summer adjustment.

The technical distinction is that GMT is a time zone based historically on astronomical observation, while UTC is a standard based on atomic time. The difference is under a second and only matters to people who run satellites. The practical difference is that the UK is on GMT only in winter, whereas UTC is constant, so “GMT” as a reference is ambiguous in July and “UTC” is not.

Why it is used for anything that crosses borders

Because it does not move. A flight schedule, a server log, a financial transaction or a scientific measurement stamped in UTC means the same thing in every country and in every month. Stamped in local time, it needs a location and a date to interpret, and two systems on different sides of a daylight saving change will disagree.

This is why computer systems store time internally as UTC and convert to local time only for display. It is also why aviation runs entirely on UTC, written with a Z suffix and spoken as Zulu.

The daylight saving trap

Most cross-border meeting mistakes come from daylight saving, and specifically from the fact that countries change on different dates. The US moves its clocks in mid-March and early November; the EU and UK in late March and late October. For about two or three weeks each year the usual offset between London and New York is four hours instead of five.

A recurring meeting set as “3pm London, 10am New York” is correct for most of the year and wrong during those weeks, and calendar software does not always warn you. Setting the meeting in one place’s local time and letting the calendar convert it for the other is more reliable than fixing both times by hand.

Stating a time so it cannot be misread

Give the UTC offset explicitly: “14:00 UTC+1” or “14:00 BST (UTC+1)”. Or give the time in UTC and let each person convert. Never write just “2pm” in a message to someone in another country, and be cautious with “GMT” in summer, since many people use it to mean UK time when UK time is actually an hour ahead.

Common questions

Is UTC the same as GMT?

For everyday purposes, yes: both are the time at the Greenwich meridian with no daylight saving. Technically GMT is a time zone and UTC is a standard maintained by atomic clocks, and they can differ by fractions of a second. The UK uses GMT in winter and BST in summer; UTC stays fixed.

What is Zulu time?

The military and aviation name for UTC. The letter Z, spoken as Zulu in the phonetic alphabet, marks UTC in timestamps, so 14:30Z means 14:30 UTC.

Why do meeting times go wrong across time zones?

Almost always because one side applied daylight saving and the other did not, or because the countries switch on different dates. The US and Europe change clocks about two weeks apart in spring and a week apart in autumn, and meetings booked as a fixed local time in both places drift during those windows.

Sources

Every factual claim above traces to one of these. Follow them rather than taking this article's word for it.

  1. National Physical Laboratory GOV.UK

Try it yourself

Free, instant, and nothing you enter leaves your browser.