What is UTC, and why does it matter

UTC is the global time standard that every server, airline schedule, satellite, and software stack agrees on. If you've ever seen a timestamp ending in Z or +00:00, that's UTC.

The short answer

UTC = Coordinated Universal Time. It's the basis for all other time zones, expressed as offsets: New York is UTC−5 (or UTC−4 in DST), Tokyo is UTC+9, Mumbai is UTC+5:30. UTC itself never observes daylight saving — it's a fixed reference.

UTC vs. GMT

For most practical purposes, UTC and GMT are interchangeable — both align with the 0° meridian at Greenwich, England. The technical difference: UTC is defined by atomic clocks and corrected with leap seconds, while GMT is the older astronomical definition. Day-to-day, you can use them as synonyms.

Why everyone uses it

UTC is unambiguous. “Meet at 3pm” without context is ambiguous (whose 3pm?). “Meet at 14:00 UTC” is exact for everyone on the planet. That's why:

Aviation and military operate on UTC (called “Zulu time”)
Server logs and databases store timestamps in UTC
API protocols use UTC by default (ISO 8601, RFC 3339)
Distributed systems coordinate on UTC clocks

When UTC matters to you

Coding. Always store and transmit timestamps in UTC; convert to local time only at display.
Scheduling international meetings. If you've got 4+ time zones, picking a UTC anchor avoids the “wait, did you mean my 3pm or yours?” loop.
Reading airline schedules. Some itineraries quote departure in UTC for clarity across long-haul connections.

Common abbreviations and what they mean

Here's a quick reference for the most common UTC-anchored conversions:

UTC to EST — Eastern US (winter)
UTC to PST — Pacific US (winter)
UTC to CET — Central Europe
UTC to IST — India
UTC to JST — Japan