What does "8/7 Central" mean?

It is a broadcast convention meaning the show airs at 8:00 PM Eastern and 7:00 PM Central simultaneously. The Central time broadcast is the Eastern feed shown one hour earlier. Mountain and Pacific get their own feeds.

Is UTC the same as Greenwich Mean Time?

For practical purposes, yes. GMT is a time zone; UTC is a time standard. The difference is less than one second, so for daily life, they are interchangeable.

Does UTC ever observe daylight saving time?

No. UTC has no DST. It is constant year-round. That is the entire point. It is a reference standard, not a local time.

What time is it in UTC right now?

If you are on Eastern Time in winter, take away 5 hours from your local time. In summer, take away 4. If it is 3:00 PM EST, it is 20:00 UTC. If it is 3:00 PM EDT, it is 19:00 UTC.

Why is the abbreviation UTC instead of CUT?

The abbreviation is a compromise between English ("Coordinated Universal Time" → CUT) and French ("Temps Universel Coordonné" → TUC). UTC was the agreed middle ground.

How many time zones does the US have?

The IANA time zone database lists 29 zones for the United States, reflecting historical and regional variations. The contiguous 48 states span four main zones: Eastern, Central, Mountain, and Pacific. --- ## What to Do Next Start thinking in UTC for anything that crosses time zones. Set your phone to show UTC in your world clock. When scheduling international calls, use UTC as the common language. For the full breakdown of boundaries, states, and DST rules, read the US time zones explained guide. Coordinating with colleagues or family across the country? The best times to call across US time zones page lays out the windows that will not wake someone at 6 AM. The mental model is simple: UTC is the world's clock. Everything else is just a local variation on it. Master that one idea, and time zones stop being confusing.

What Is UTC? Understanding the World's Time Standard

On 15 January 2026, at noon in Washington D.C., it was 17:00 UTC. The same moment in London was 17:00 UTC, in Mumbai 22:30 UTC, and in Tokyo 03:00 UTC the next morning. Four cities, four different local times, one shared number: 17:00. That number is Coordinated Universal Time, the anchor that stops global time from dissolving into chaos.

UTC (Coordinated Universal Time) is the primary world time standard. It is the zero point from which every time zone on Earth is measured. When you see "UTC−5" or "UTC+1," the number tells you how many hours that place sits behind or ahead of the world's reference clock.

Think of it like the prime meridian for time. Just as the Greenwich Meridian marks 0° longitude, UTC marks 0 hours. Everything else is a calculation from that baseline.

But here is what trips most people up: UTC is not a time zone. It does not observe daylight saving time. It does not shift with the seasons. It is the same number in January as it is in July. That is precisely why it is so useful.

UTC vs GMT: The Distinction That Matters

You have probably heard "GMT" and "UTC" used interchangeably. For most practical purposes they are the same thing, but there is a technical distinction worth understanding.

GMT (Greenwich Mean Time) is a time zone. It is what the United Kingdom uses in winter, tied to the Earth's rotation relative to the sun's position over the Greenwich meridian.

UTC is a time standard. It is atomic, measured by incredibly precise cesium clocks, and adjusted with leap seconds to stay within 0.9 seconds of astronomical time.

The abbreviation "UTC" is itself a compromise. English speakers wanted "CUT" (Coordinated Universal Time). The French wanted "TUC" (Temps Universel Coordonné). They met in the middle: UTC. Neither side got its way entirely, which is perhaps the most diplomatic outcome possible.

For Americans: if someone says "GMT," they almost always mean UTC. The difference is about 0.9 seconds. Utterly irrelevant in daily life, absolutely critical if you are building GPS satellites or financial trading systems.

How UTC Offsets Work Across US Zones

The United States spans multiple time zones across the contiguous states, Alaska, Hawaii, and its territories. Each has a UTC offset that changes with daylight saving time.

Eastern Time (ET): UTC−5 in winter (EST), UTC−4 in summer (EDT) Central Time (CT): UTC−6 in winter (CST), UTC−5 in summer (CDT) Mountain Time (MT): UTC−7 in winter (MST), UTC−6 in summer (MDT) Pacific Time (PT): UTC−8 in winter (PST), UTC−7 in summer (PDT) Alaska Time (AKT): UTC−9 in winter (AKST), UTC−8 in summer (AKDT) Hawaii-Aleutian Time (HT): UTC−10 year-round (HST). Hawaii does not observe DST.

So when someone says "2 PM UTC," that is 9 AM in Washington during standard time (UTC−5), but 10 AM during daylight time (UTC−4). This is why "8/7 Central" works for TV, and why international scheduling requires a calculator.

Why Aviation, the Military, and Developers Rely on UTC

The military uses UTC for operations. You have probably heard it called "Zulu time" in films. Pilots use it exclusively. Software developers store timestamps in it. Financial markets use it to synchronise trades.

Why? Because UTC eliminates ambiguity. When it is 15:00 UTC, it is 15:00 UTC everywhere on Earth. No DST confusion. No "is that Eastern or Central?" problems. No "wait, which day is it in Tokyo?" moments.

For travellers, UTC is the Rosetta Stone of scheduling. Your flight departs at 2:30 PM local time and arrives at a different local time. The UTC offset tells you exactly how much time will actually pass in the air.

For developers, storing time in UTC is non-negotiable. If you store times in local time, you have to know the DST rules for every time zone at every historical moment. That is a rabbit hole of complexity. Store UTC, convert for display. It is the only sane approach.

Converting UTC to US Time Zones

Converting UTC to US time zones does not require a maths degree. Here is the quick mental model.

During standard time (winter): - Eastern: take away 5 hours - Central: take away 6 hours - Mountain: take away 7 hours - Pacific: take away 8 hours

During daylight time (summer): - Eastern: take away 4 hours - Central: take away 5 hours - Mountain: take away 6 hours - Pacific: take away 7 hours

So 18:00 UTC (6 PM) is 1 PM Eastern in winter, or 2 PM Eastern in summer. That is the entire trick.

The tricky part is knowing when DST starts and ends. The US begins DST on the second Sunday in March and ends on the first Sunday in November. But Europe changes on different dates. Japan does not change at all. India is offset by 30 minutes (UTC+5:30). Yes, half hours exist.

UTC and the International Date Line

The International Date Line runs roughly along the 180th meridian, but it is not a straight line. It jogs around islands and countries to keep them on sensible dates. When it is 12:00 UTC, it is simultaneously noon in London and the early hours of the next day in Tokyo.

Here is the mind-bender: when it is 8:00 PM Eastern on Friday, it is already Saturday in Australia. The date line is why "what day is it?" is not always a simple question. UTC solves this by being the reference point. If you know the UTC time, you can always work out the date everywhere else.

Why Developers Store Time in UTC

If you have ever seen a timestamp like "2026-09-29T14:30:00Z," you have seen UTC in action. The "Z" stands for "Zulu," military shorthand for UTC.

Developers store time in UTC because it is deterministic. A Unix timestamp, the number of seconds since January 1, 1970, is the same everywhere on Earth. Convert to local time only when displaying to users.

This matters because DST is political. It changes. Time zone databases are updated multiple times per year as countries change rules. If your code assumes a fixed offset, it will break. Storing UTC future-proofs your application against the whims of legislatures.

Leap Seconds: When a Minute Gets 61 Seconds

Earth's rotation is slowing down. Not by much, milliseconds per century, but enough that atomic time and astronomical time drift apart. To keep them in sync, scientists occasionally add a "leap second" to UTC.

This has happened 27 times since 1972. The last was December 31, 2016. When it happens, the final minute of the day has 61 seconds instead of 60.

For most people, a leap second is invisible. For software engineers, it is a nightmare. Systems can handle "impossible" times (2:59:60) in unexpected ways. There has been debate about abolishing them, but for now, they are part of how UTC works.