UTC and IANA Time Zones: What They Are and Why They Matter
You’ll see “UTC−5” and “America/New_York” in calendar apps and scheduling tools, often used interchangeably. They’re not the same thing, and the difference matters.
UTC: the shared reference
Coordinated Universal Time is the baseline everything else is measured against. No daylight saving, no regional quirks. Every time zone is defined as UTC plus or minus some number of hours.
When you say “the meeting is at 15:00 UTC,” anyone in the world can convert that to their local time. It’s the most reliable thing you can put in a message — more reliable than “3pm EST,” which shifts twice a year and means different things depending on the month.
The limitation of a raw offset like “UTC−5” is that it’s a snapshot. It tells you the current gap from UTC, but nothing about when that gap changes. “UTC−5” is correct for New York in January and wrong in June.
IANA names: the full picture
The IANA Time Zone Database (also called the tz database) tracks the complete rules for every time zone in the world — including when clocks change, and when governments have historically changed those rules. Every calendar app and operating system uses it under the hood.
IANA names use a Region/City format:
| IANA name | What it encodes |
|---|---|
America/New_York | US Eastern time, including all daylight saving transitions |
Europe/London | UK time — GMT in winter, BST in summer |
Asia/Kolkata | India Standard Time (always UTC+5:30, no daylight saving) |
Pacific/Auckland | New Zealand time with DST rules |
The difference from an offset: America/New_York knows that New York is UTC−5 in winter and UTC−4 in summer, and on exactly which dates those transitions happen. “UTC−5” doesn’t know any of that.
Which to use when
In written communication — use UTC offsets or the UTC time itself. “The call is at 14:00 UTC” is unambiguous and every recipient can convert it.
When setting up calendars or recurring meetings — share the IANA name. If a new teammate sets their calendar to America/Chicago rather than a fixed offset, their events will stay correct through DST transitions without anyone having to update anything.
Avoid three-letter abbreviations when precision matters. “CST” could mean Central Standard Time (UTC−6) or China Standard Time (UTC+8). “IST” could mean India, Ireland, or Israel. They’re fine in casual conversation; they cause real problems in scheduling tools.
meetwhen lets you work with city names directly and handles the IANA mapping for you.
Buy me a coffe