Also available in: Español · Português · Français · العربية
Time zone abbreviations
What EST, CST, IST and the rest actually denote, taken from the IANA database rather than from another list.
What is a time zone abbreviation?
A time zone abbreviation is the short label a region uses for its local time: EST for Eastern Standard Time, CET for Central European Time, IST for India Standard Time. They turn up in email headers, log files, meeting invitations and the corner of a clock app, and they are the thing people actually say out loud when arranging a call.
They are also, in a specific technical sense, not identifiers. The IANA time zone database — the one behind essentially every operating system, phone and programming language — identifies a zone by a name like America/New_York or Africa/Cairo. The abbreviation is a display label attached to whatever rule is in force at a given moment, and the database's own maintainers are explicit that abbreviations are not standardised and should not be used to identify anything.
This page lists the abbreviations that database actually emits: 48 of them, with every distinct UTC offset each one denotes and the zones that use it. That number is much smaller than most published lists, for a reason worth understanding before you trust any of them.
How to use it
- Type the abbreviation you were given. EST, CST, BST — the search ranks an exact abbreviation first, so you get the answer rather than every zone whose name happens to contain those letters.
- Read the offsets underneath it. Each row is one UTC offset the abbreviation denotes, with the zones that use it. Most abbreviations have exactly one row, which means the label is unambiguous and you can act on it.
- If it has more than one row, stop and ask which was meant. Four abbreviations are genuinely ambiguous, and the Ambiguous only filter shows just those. You can also search by zone name or by offset — Havana, or +05:30 — when you have one and want the other.
Only four abbreviations are actually ambiguous
The famous complaint about time zone abbreviations is that they collide, and CST is the usual example: it is United States Central Standard Time at UTC−06:00, Cuba Standard Time at UTC−05:00, and China Standard Time at UTC+08:00 — three readings spanning fourteen hours. That is entirely true, and it is rarer than the complaint suggests.
Measured across the whole database, exactly four of the 48 abbreviations denote more than one UTC offset. CST is one. IST is another, and it is the sharpest of them, because Irish Standard Time at UTC+01:00, Israel Standard Time at UTC+02:00 and India Standard Time at UTC+05:30 are all abbreviated identically and all in common use. PST covers both Pacific Standard Time at UTC−08:00 and Philippine Standard Time at UTC+08:00, sixteen hours apart. CDT is the fourth, splitting between the United States and Cuba.
The other forty-four point at exactly one offset each. So the honest version of the warning is not that abbreviations are unreliable in general — it is that four specific ones are, and those four happen to include the two most commonly used in international scheduling. If someone sends you a time in CST or IST, the abbreviation genuinely does not tell you when they meant.
Note what ambiguity is being measured here. Plenty of abbreviations are shared by many zones — EST covers more than thirty — but those zones all keep the same offset, so the label still fixes a time. Sharing a label with another zone is harmless; sharing it with another offset is the problem.
Your browser will not tell you most of these
This is the part that surprised us most, and it is why this page exists as something other than a table. Ask a browser for a zone's short name and it does not consult the IANA database — it consults CLDR, Unicode's locale data, which is a different source with different opinions.
Measured against the runtime's own list of zones: 249 of them have an alphabetic abbreviation in the IANA database, and a browser asked for the short name of those same 249 agrees with the database on 115. That is 46.2 percent. For the remaining 134 it returns a bare GMT offset instead. So a browser will tell you Africa/Cairo is GMT+2, and will never tell you it is EET; the same goes for most of Africa, much of Asia, and every zone whose abbreviation is not familiar to an English-speaking audience.
That has a practical consequence for anyone building software. If you display a zone's short name using the platform's own formatter, more than half your users in abbreviation-using regions will see a numeric offset where they expected letters — and if you go looking for the abbreviation in your runtime because a table like this one says it exists, you will not find it. The abbreviation is real, and it is in a database your language probably does not expose.
It also means the two sources disagree about what is even worth naming. CLDR's short names are locale-dependent by design: what a zone is called depends on who is asking. The IANA abbreviation does not vary that way. Neither is wrong; they answer different questions, and most tools quietly pick one without saying which.
Honest limits
This table is a snapshot, and it says so on the page along with the release it came from and the date it was generated. IANA publishes several times a year and abbreviations do change — the database has been steadily removing invented ones for years. A table without a date on it is making a claim it cannot support, which is why this one carries both and why the generator sits in the repository next to the data so it can be re-run and diffed.
The list is deliberately shorter than most. Zones whose abbreviation is a numeric offset — the database emits things like +05 and −03 for a large part of the world — are not included, because those are not abbreviations. This is the single biggest reason other published lists are longer: many of them include invented or obsolete labels that no current release of the database emits, alongside real ones, with nothing to distinguish the two.
Abbreviations are shown for the offsets in force during 2026, sampled across the year so that both standard and summer time appear everywhere including the southern hemisphere. A zone that changes its rules in a future year will change here when the database does.
Finally, this page tells you what an abbreviation denotes; it does not convert times. If you have a moment and want it in another zone, that is a different job and a different page on this site.
Why is it free?
Because there is nothing to charge for. The table ships with the page and the search runs in your browser, so nothing you type is uploaded, logged or stored anywhere.
No account, no sign-up, nothing held back behind one. The data comes from the IANA time zone database itself rather than from another website's table, the script that generates it is in the repository, and the checks that verify it re-read the database and diff the result rather than taking the committed file on trust.