UTC and Time Zones

Definition

UTC is the world’s reference time scale; a time zone is a local offset from it, which can change with daylight saving or by law. Storing instants in UTC and converting to a local zone only for display avoids ambiguous and missing hours.

In plain terms

A timestamp like “2026-03-02 08:30” means nothing until you know the zone. Local clocks also skip and repeat hours when daylight saving starts and ends, and governments change the rules, so a zone is not a fixed number of hours. Recording an instant in UTC gives every system the same unambiguous answer; the local view is derived from it.

Calendar days depend on the zone too. “Yesterday’s count” means different sets of events in Tokyo and in Los Angeles, so a daily metric must say which day boundary it uses.

Example

One event, seen from three places:

In the United States in 2026, clocks jump from 02:00 to 03:00 on 8 March, so 02:30 does not exist that night, and they go back from 02:00 to 01:00 on 1 November, so 01:30 happens twice. A local-time column cannot tell the two 01:30s apart; a UTC instant can.

Common misunderstandings

• “UTC and GMT are the same thing.” In everyday use they agree, but UTC is the defined standard and GMT is a time zone used in the United Kingdom.
• “A time zone is a fixed offset.” Offsets change with daylight saving and with new laws; use a maintained time-zone database, not a hard-coded number.
• “A date has no time zone.” Which calendar day an instant falls on depends on the zone.