Timezone Abbreviations and What EST, CET and IST Actually Mean

What are timezone abbreviations and why are they ambiguous?

A timezone abbreviation is a two to five letter label that a date formatter prints next to a time so a human can read it. It is output, never input. No standards body owns the list, the same letters are used by different countries, and the abbreviation changes twice a year in most of the world without the underlying zone changing at all.

The practical consequence is simple: if a log line, a form field or a JSON payload says 10:00 IST, you cannot convert it. India is UTC+5:30 and Ireland is UTC+1 in summer, so that string is ambiguous by four and a half hours. The same happens with CST, where the spread between Central Standard Time and China Standard Time is fourteen hours.

Timezone abbreviations list with standard UTC offsets

The offsets below are the standard time values. Where a region shifts its clocks, the daylight form and its offset are in the last column.

What does EST mean, and CST, MST and PST?

EST means Eastern Standard Time, the winter time of the US east coast and eastern Canada, at UTC-5. The other three North American zones step west one hour at a time.

Two well known exceptions inside this grid: most of Arizona stays on MST all year and never switches to MDT, and Saskatchewan stays on CST all year. A person in Phoenix and a person in Denver share an abbreviation in winter and not in summer.

European abbreviations: GMT, CET and EET offsets

Europe runs three bands one hour apart, and every one of them has a summer form. GMT is the odd one out because it is both a zone label and, in casual use, a synonym for UTC. The two are not the same thing, which we cover in UTC or GMT: same clock, different authority.

Ireland is worth a second look. Its legislation names the summer time Irish Standard Time and treats winter as the deviation, so the naming is inverted compared with its neighbours: Ireland is GMT in January and IST in July.

UTC offset list for Asia and Oceania abbreviations

Most of Asia does not shift its clocks, so these abbreviations hold all year. Australia and New Zealand do shift, and their summer falls in the northern winter.

Note the offsets that are not whole hours. India at UTC+5:30 and Nepal at UTC+5:45 break any code that stores an offset as an integer number of hours, and Newfoundland does the same in the other direction.

Which timezone abbreviations mean more than one zone?

These are the collisions that produce real bugs, because both readings are common and both look plausible in a support ticket.

A parser cannot resolve any of these from the letters alone. The only thing that disambiguates them is context you have to supply separately, such as the country of the user who typed the string, and that context is exactly what tends to be missing by the time the bug report arrives.

CST vs CDT and the other standard and daylight pairs

Most zones that shift their clocks have two abbreviations, one for standard time and one for daylight time. CST vs CDT is the usual example: Chicago is CST at UTC-6 in January and CDT at UTC-5 in July. The city, the country and the IANA zone name never changed, only the label and the offset.

Two traps follow from this. The first is that people write PST or EST all year round, including in July when the west coast is actually on PDT, so a label you receive may be wrong by an hour even when the region is unambiguous. The second is that the changeover dates differ by country: the US switches on the second Sunday in March and the first Sunday in November, while the EU switches on the last Sunday in March and the last Sunday in October, which leaves a few weeks each year when the usual gap between New York and Paris is not the usual gap. The DST change dates by country cover that calendar in full.

Notice also that CDT at UTC-5 has the same offset as EST at UTC-5. An offset on its own does not identify a zone either, which is why the pair of a UTC instant and a zone name is the only combination that survives.

Which IANA timezone database name should I store?

The IANA timezone database, also called tzdata or the Olson database, gives every zone a unique name in Region/City form: America/New_York, Europe/Berlin, Asia/Kolkata, Australia/Sydney. Those names are unambiguous, they are the identifiers most operating systems and standard libraries already use, and they carry the full history of offset and daylight rules for that place, so the same name resolves correctly for a date in 1995 and a date next July.

Governments change their rules, and the IANA database is updated when they do, which is another reason to keep the name and resolve the offset at read time rather than freezing a number.

from datetime import datetime
from zoneinfo import ZoneInfo

# The zone name is the input. The abbreviation is only ever output.
meeting = datetime(2026, 7, 14, 9, 0, tzinfo=ZoneInfo("America/New_York"))
print(meeting.strftime("%Y-%m-%d %H:%M %Z"))
# 2026-07-14 09:00 EDT

// Same rule in the browser: pass the IANA name, read the label back.
new Intl.DateTimeFormat("en-US", {
  timeZone: "Asia/Kolkata",
  timeZoneName: "short",
}).format(new Date());
// Zones with no short English label print an offset such as GMT+5:30

That last comment matters. Not every zone has an abbreviation at all, and engines print a numeric offset when none exists, so any code that expects three letters back from a formatter will meet a string it did not plan for.

How can I check what an abbreviation means for a date?

Because an abbreviation depends on the date, the only reliable check is to pick the actual moment and convert it. The timezone converter takes a date and a time, a source zone and a target zone chosen from the full list of IANA names your browser supports, and returns the converted moment as a full date and time, a date only value, a time only value, a Unix timestamp in seconds and an ISO 8601 string, each with a copy button. There is a button to fill in the current time and one to swap the two zones.

When you need several places at once rather than one moment, the world clock ticks live for sixteen major cities and shows each one with its current UTC offset rather than an abbreviation, which sidesteps the ambiguity completely. You can add any other IANA zone from a searchable list, and the additions stay in your browser for next time. Both tools run entirely in the browser, on the zone data your browser already ships, documented in the Intl.DateTimeFormat reference.

Timezone converterConvert one moment between two IANA zones and copy the result World clockLive time and current UTC offset for sixteen cities at once

Frequently asked questions