What UTC is
UTC stands for Coordinated Universal Time. It is the global civil time reference: a single, unambiguous clock that every U.S. time zone — and every zone in the world — is defined as an offset from. UTC itself never observes daylight saving time. Its seconds are kept in step with atomic clocks, with occasional leap seconds added to track the Earth's rotation.
You can think of UTC as the timeline; you can think of each U.S. zone as a label that says "we display the time on the timeline shifted by N hours."
UTC vs GMT
The two terms are often used interchangeably, and for everyday purposes they refer to the same clock. The technical distinction:
- GMT — Greenwich Mean Time — is a time zone (the local civil time in parts of the United Kingdom in winter). It is also a historical name for the global reference clock.
- UTC is the modern global reference standard, defined by atomic clocks, that replaced GMT in international use beginning in 1972.
For any precision under a second, the two can drift apart slightly. For human-scale scheduling, "UTC" and "GMT" are interchangeable. In writing aimed at a global audience, prefer UTC.
U.S. time zones as UTC offsets
Every U.S. zone has two offsets — one for standard time and one for daylight time. The rule for which one is in effect on a given date is on the daylight saving time page.
| Zone | Standard offset | Daylight offset |
|---|---|---|
| Eastern | UTC-5 | UTC-4 |
| Central | UTC-6 | UTC-5 |
| Mountain | UTC-7 | UTC-6 |
| Pacific | UTC-8 | UTC-7 |
| Alaska | UTC-9 | UTC-8 |
| Hawaii–Aleutian | UTC-10 | UTC-9 (Hawaii itself doesn't observe DST) |
| Arizona (outside the Navajo Nation) | UTC-7 | (does not observe DST) |
| American Samoa | UTC-11 | — |
| Guam, N. Mariana Islands | UTC+10 | — |
Converting in your head
The mental model: subtract to go from UTC to a U.S. zone, add to go the other way. Two worked examples make the rule stick.
Example 1 — UTC to U.S. East Coast in summer
Suppose a server log shows an event at 14:30 UTC on July 4. Eastern Daylight Time is UTC-4 in summer. Subtract 4 hours: 10:30 a.m. EDT. That's it.
Example 2 — Pacific to UTC in winter
You're in Los Angeles in January and want to convert 9:00 a.m. PST to UTC for an international call. Pacific Standard Time is UTC-8 in winter. To go from PST to UTC, you add 8 hours: 17:00 UTC (i.e., 5:00 p.m. UTC).
The trap: the date can change
If a U.S. local time is late in the evening, the equivalent UTC time often falls on the next calendar day. "10 p.m. EST on January 5" is "03:00 UTC on January 6," not "03:00 UTC on January 5." When precision matters, always include the date alongside the time.
Why DST makes UTC conversion awkward
The trickiest part of working with U.S. time and UTC is that the offset isn't constant. The same zone — Eastern Time, say — is UTC-5 for part of the year and UTC-4 for the rest. If you write down "Eastern Time = UTC-5" and stop there, you'll be off by an hour for roughly eight months a year.
For ad-hoc conversions, look up which abbreviation is in effect for the date in question (EST = UTC-5; EDT = UTC-4) and apply that offset. The abbreviations reference lists every U.S. zone in both forms.
UTC formats you'll see in the wild
UTC times appear in several conventional formats. They all describe the same instant; they just differ in syntax.
14:30 UTC— plain English, common in articles and announcements.14:30Z— the "Zulu" suffix, used in aviation, military, and some technical contexts. Z is shorthand for "zero offset."2026-05-07T14:30:00Z— ISO 8601 with the Z suffix, the standard for software and APIs.2026-05-07T14:30:00+00:00— equivalent ISO 8601 with an explicit offset.2026-05-07T10:30:00-04:00— the same instant, written in EDT local time with the offset attached. This form is unambiguous and survives calendar export-and-import without information loss.
UTC for software
If you're building anything that schedules across zones, the durable rule is: store every timestamp in UTC, and convert to a local zone only at the moment you display it. The reason is that a UTC instant is unambiguous; a local-time string without an offset is not, especially during DST transitions.
For future events that depend on local time — "the team meeting is at 9 a.m. New York time, every Wednesday" — store the IANA zone (America/New_York) along with the local time, and let the time-zone library compute the UTC instant at delivery. Storing only the UTC instant of the first occurrence will quietly drift across DST transitions.
Common UTC mistakes
- Treating UTC as a U.S. time zone. UTC is not a civil time zone in any U.S. jurisdiction. No place in the United States lives by UTC.
- Forgetting the date can shift. Late-evening U.S. local time can be the next day in UTC.
- Using GMT for technical work. GMT carries connotations of British civil time and observes DST in the form of British Summer Time. Use UTC.
- Treating "UTC-5" as a substitute for "Eastern Time." They line up in winter only. In summer, Eastern Time is UTC-4.
Quick reference
To go from UTC to a U.S. zone, subtract the offset. To go from a U.S. zone to UTC, add it. The offset to use depends on whether daylight saving time is in effect for the date. The current local time in every U.S. zone is on the homepage; for a one-shot conversion, the converter handles UTC alongside every U.S. zone.