Three-letter time zone abbreviations feel precise, but they are one of the least reliable ways to communicate a time. EST, CST, IST and their relatives were invented for regional broadcast schedules and shipping timetables long before software had to parse them automatically, and several of the most common ones now refer to more than one place at once.
This guide decodes the abbreviations you will run into most often, flags the ones that clash, and explains why an offset from UTC is almost always the safer thing to put in an email or a calendar invite.
The abbreviations that split into a summer and winter form
Many zones use two different abbreviations depending on whether daylight saving time is in effect, which is a common source of confusion because the same city uses a different label for half the year.
- EST / EDT — US and Canada Eastern time. EST (UTC-5) applies in winter, EDT (UTC-4) in summer.
- CET / CEST — Central European Time (UTC+1) in winter, Central European Summer Time (UTC+2) in summer.
- BST / GMT — the United Kingdom uses British Summer Time (UTC+1) from spring to autumn, then reverts to GMT (UTC+0) for winter. See our GMT vs UTC guide for how GMT relates to UTC the rest of the year.
The underlying mechanism — clocks moving forward and back on a set schedule — is covered in detail in our guide to how daylight saving time works.
Abbreviations that mean more than one thing
The more serious problem is abbreviations that are reused by unrelated regions. Two letter-for-letter matches cause the most trouble in scheduling:
| Abbreviation | Possible meanings |
|---|---|
| IST | India Standard Time (UTC+5:30), Israel Standard Time, Irish Standard Time |
| CST | US Central Standard Time (UTC-6), China Standard Time (UTC+8), Cuba Standard Time |
A calendar invite that simply says "3pm IST" is genuinely ambiguous: it could mean 3pm in Mumbai, 3pm in Jerusalem, or 3pm in Dublin, and those three moments are hours apart on the UTC clock. The same is true of "9am CST" for a colleague in Chicago versus one in Shanghai.
Why offsets are the safer choice
An offset such as UTC-6 or UTC+5:30 has exactly one meaning everywhere on earth, whereas an abbreviation depends on local convention and the season. Writing "15:00 UTC-6" or, better still, a full date and time with a named IANA zone such as America/Chicago, removes the ambiguity entirely. IANA zone identifiers, unlike three-letter abbreviations, encode both the region and its daylight saving rules, so software can compute the correct local time on any date, past or future.
A practical rule for invitations and documents
- Give the UTC offset alongside any abbreviation, for example "2pm EDT (UTC-4)".
- For recurring meetings that span a daylight saving transition, name the city or IANA zone rather than the abbreviation, since the offset itself will change partway through the series.
- When in doubt, check the current local time directly on a world clock rather than trusting a label typed into an email months earlier.
Abbreviations are a convenience, not a standard
There is no global authority that assigns or polices time zone abbreviations the way there is for country codes or currency codes. They arose informally, region by region, which is why overlaps like IST and CST were never resolved. Treat them as a friendly label for humans reading a schedule, and let the underlying offset or IANA zone do the actual work of pinning down a moment in time.