Why Time Zone Abbreviations Like CST and IST Are Genuinely Dangerous
There is no official global registry of time zone abbreviations. They are conventions, several of them collide, and calendar software will not warn you.
By Nishanth Narayanan · 2026-08-06 · 6 min read
The collisions
CST is the worst. It means Central Standard Time in North America, UTC-6. It also means China Standard Time, UTC+8. And Cuba Standard Time, UTC-5. Someone in Chicago and someone in Shanghai can both write "10:00 CST" and be fourteen hours apart.
IST means India Standard Time at UTC+5:30, Irish Standard Time at UTC+1, and Israel Standard Time at UTC+2 or UTC+3. Given how much software development is split between India and Ireland, this one causes real problems.
BST is British Summer Time at UTC+1, and also Bangladesh Standard Time at UTC+6.
AMT, ECT, WST and several others have similar clashes. There is no authority that resolves them, because abbreviations are a naming habit rather than a standard.
The season problem
Even without collisions, the abbreviations usually encode whether daylight saving is in force, and people write them out of season constantly.
The American east coast is EST in winter and EDT in summer. Writing "3pm EST" in July is wrong: in July that region is on EDT. Whether the reader interprets it as the literal UTC-5 you wrote, or charitably assumes you meant local New York time, changes the answer by an hour.
The same applies to PST and PDT, CET and CEST, GMT and BST. In practice, PST is used year round as a loose synonym for California time, which is convenient and technically incorrect half the year.
India avoids this entirely, because it does not observe daylight saving, so IST is always IST. That is one of the few things it makes simpler.
What to write instead
Use the city. "15:00 in New York" cannot be misread by anybody and needs no knowledge of whether daylight saving is active. This is the single most useful habit.
Use UTC for anything technical. "2026-08-06T14:30:00Z" is unambiguous, machine readable, and does not move.
Use the IANA identifier in software. America/New_York, Asia/Kolkata, Europe/Dublin. These are stable, unique, and carry the full history of that location's rules, including past changes. Never store an abbreviation or a raw offset.
If you must use an abbreviation, add the offset. "10:00 CST (UTC-6)" removes the ambiguity in five characters.
Why our pages still show abbreviations
People search for them. Someone typing "IST to PST" into a search box wants an answer, not a lecture, and refusing to use the common shorthand would simply mean not being found.
What we do instead is name the region alongside the abbreviation everywhere it appears, so a page about IST to PST says India Standard Time and US Pacific Time in the title and heading, and the live clocks show the current offset in force. The abbreviation gets you to the page; the page tells you what it actually means.
If you want to check a specific pair for a specific date, including whether daylight saving is active on that date, the converter works from city names and shows the real offset rather than the label.
Frequently asked questions
Does CST mean Central or China Standard Time?
Both, and they are fourteen hours apart. CST is Central Standard Time at UTC-6 in North America and China Standard Time at UTC+8. There is no registry that resolves the clash, so the abbreviation alone is not enough.
Is it wrong to write EST in summer?
Technically yes. The American east coast is on EDT, UTC-4, from March to November. Writing EST in July either means the literal UTC-5 or is a loose way of saying New York time, and the two differ by an hour.
What should I use instead of an abbreviation?
Name the city for human readers, use UTC with a Z suffix for technical records, and use IANA identifiers such as America/New_York in software.
About the author
Nishanth Narayanan builds and maintains GlobalTimeTools from Coimbatore, India. He works with distributed teams across Indian, European and US time zones, which is where most of these questions came from.