CST vs CDT: Central Time's Two Abbreviations (And Three Zones Named CST)

CST is Central Standard Time, UTC−6, the winter clock. CDT is Central Daylight Time, UTC−5, the summer clock. CT means "Central Time, whichever one is running today." That is the entire answer for anyone booking a call with Chicago, Dallas, Houston, or Winnipeg. Everything difficult about Central Time comes after that sentence: most of Mexico is on Central Time and stopped changing its clocks in 2022, the Canadian province of Saskatchewan sits on CST all year and never moves, and the letters CST are also the standard abbreviation for two other zones — one of them fourteen hours away. This article covers the rule, the exact transition dates, the scheduling mistakes that follow from them, and the ambiguity that quietly corrupts international calendars. If you only want the arithmetic, the timezone converter does it for you.

The rule in one sentence

Central Standard Time (CST) is UTC−6 and is in force from the first Sunday in November to the second Sunday in March. Central Daylight Time (CDT) is UTC−5 and is in force from the second Sunday in March to the first Sunday in November. CT is the generic label for the zone and commits to neither — it is what American broadcasters, sports schedules, and airline timetables use so they never have to name the season.

The IANA time zone database represents the U.S. Central region with the identifier America/Chicago, which carries the full history of every transition the zone has ever recorded, including the 2007 change that lengthened U.S. daylight time by about four weeks. Operating systems, databases, and programming languages all read those rules from tzdata, which is why an invite created in Outlook on a laptop in Nashville resolves to the correct local hour when it is opened in Berlin.

What the abbreviations actually mean

The three-letter framework is consistent across the North American zones. The first letter is the region (Pacific, Mountain, Central, Eastern, Atlantic, Hawaiian). The second letter is either Standard or Daylight. The third letter is always Time. So:

• CST— Central Standard Time, UTC−6. The "winter" clock setting in the Central Time Zone, roughly four months of the year.
• CDT— Central Daylight Time, UTC−5. The "summer" clock setting, roughly eight months of the year.
• CT— Central Time, generic. A line like "kickoff at 7:20 p.m. CT" means whichever Central clock is ticking on game day. Because the NFL, MLB, and most U.S. television networks schedule in Central Time, this is one of the most-printed time abbreviations in the country.

The same pattern produces PST/PDT/PT, MST/MDT/MT, and EST/EDT/ET. Hawaii uses HST (UTC−10) and does not observe daylight saving time; Alaska uses AKST and AKDT. Note the offsets collide across zones: CDT (UTC−5) is the same offset as EST, and CST (UTC−6) is the same offset as MDT. Two clocks can read the same hour and still carry different letters.

When does each one apply

The U.S. Department of Transportation holds jurisdiction over the nation's time zones and daylight saving time — authority it inherited from the Interstate Commerce Commission under the Uniform Time Act of 1966, which is also the law that forced every state observing daylight time to observe it on the same dates. The current schedule was set by the Energy Policy Act of 2005, which took effect in 2007 and added about four weeks to the daylight window. Under those rules:

• Spring forward: the second Sunday in March, at 2:00 a.m. local time, clocks jump from 2:00 to 3:00. CST ends; CDT begins.
• Fall back: the first Sunday in November, at 2:00 a.m. local time, clocks fall from 2:00 back to 1:00. CDT ends; CST begins.

For the current cycle that puts the next switch on Sunday, November 1, 2026 (CDT ends, CST begins), followed by Sunday, March 14, 2027 (CST ends, CDT begins) and Sunday, November 7, 2027, all at 2:00 a.m. local time. Canada's Central provinces move on the same dates. So do the Mexican border municipalities described below — but not the rest of Mexico.

One asymmetry catches people out: because daylight time now runs from March to November, CDT is in force for roughly eight months and CST for roughly four. If you mentally split the year in halves, you will guess wrong more often than not. The CST to CDT conversion is a flat one-hour shift, but the date decides which side of it you are on.

The Uniform Time Act lets a state opt out of daylight saving time and stay on standard time permanently. It does not let a state adopt permanent daylight time; that requires an act of Congress. Several Central Time states have passed conditional bills that would switch them to year-round daylight time the moment federal law permits it, and the U.S. Senate passed such a bill by unanimous consent in 2022, but as of this article's publication no such measure has become law.

Where Central Time actually applies

Central Time covers all or part of twenty U.S. states and roughly a third of the U.S. population, making it the second most populous zone in the country after Eastern. Ten states sit wholly inside it — Alabama, Arkansas, Illinois, Iowa, Louisiana, Minnesota, Mississippi, Missouri, Oklahoma, and Wisconsin. The rest are split:

• Split with Mountain Time (west edge): Texas (El Paso and Hudspeth County are Mountain; the other 252 counties are Central), Kansas, Nebraska, North Dakota, and South Dakota.
• Split with Eastern Time (east edge): Florida (the panhandle west of the Apalachicola River is Central), Michigan (four counties in the Upper Peninsula), Indiana (about a dozen counties, split between the Chicago suburbs and the Evansville area), Kentucky, and Tennessee.
• Canada: Manitoba — Winnipeg is the anchor city — plus western Ontario and parts of Nunavut, all on CST/CDT. All of Saskatchewan is on CST year-round.
• Mexico and Central America:most of Mexico, including Mexico City, Guadalajara, and Monterrey, sits at UTC−6. So do Guatemala, Belize, El Salvador, Honduras, Nicaragua, and Costa Rica, none of which observe daylight saving time.

That geography is why the Central zone is the one where boundary arguments happen. Indiana spent decades as the standing joke of American timekeeping: most of the state refused to observe daylight saving time at all until 2006, and the counties nearest Chicago and Evansville still sit on the Central side of a line that runs through the middle of the state.

Saskatchewan, Mexico, and the places that never switch

The Pacific zone has Arizona as its famous non-switching neighbor. Central has two exceptions, and both are larger.

• Saskatchewan. The province observes CST (UTC−6) year-roundand has not changed its clocks since the 1960s. Most of Saskatchewan lies geographically in the Mountain zone, so the effect is that the province keeps Mountain Time on a permanent one-hour advance. In winter Regina and Saskatoon match Winnipeg; in summer they match Calgary instead, because Manitoba has moved to CDT and Alberta has moved to MDT (UTC−6, the same offset Saskatchewan never left). The tz identifier is America/Regina.
• Mexico. Mexico abolished nationwide daylight saving time with the Ley de los Husos Horarios en los Estados Unidos Mexicanos, in force from 30 October 2022. Most of the country, including Mexico City, now stays on UTC−6 permanently — so "CST" in Mexico no longer shifts the way U.S. CST does. Two carve-outs remain: the whole state of Baja California, and a short list of border municipalities in Chihuahua, Coahuila, Nuevo León, and Tamaulipas, all of which still follow the U.S. schedule so that cross-border commerce and shift work stay aligned.

The Mexican change has a concrete consequence that many recurring calendar invites are still getting wrong. Before 2022, Chicago and Mexico City both shifted, so they usually shared a wall clock. Since 2022 they share a wall clock only during the U.S. standard-time window: from November to March both are UTC−6, and from March to November Chicago moves to UTC−5 while Mexico City does not. A weekly 10:00 a.m. Chicago call is 10:00 in Mexico City for four months of the year and 9:00 for the other eight.

The trap: "CST" means three different things

This is the section worth reading twice. The abbreviation CST is not unique, and the collisions are not obscure — they involve two of the largest economies a North American company is likely to deal with.

• CST = Central Standard Time, UTC−6. North America. tz identifier America/Chicago (and America/Winnipeg, America/Regina, America/Mexico_City).
• CST = China Standard Time, UTC+8.The single civil time of the entire People's Republic of China, with no daylight saving time. tz identifier Asia/Shanghai. The gap between the two readings of "CST" is fourteen hours in the northern winter and thirteen in summer — big enough that a misinterpreted invite lands on a different calendar day.
• CST = Cuba Standard Time, UTC−5. tz identifier America/Havana. Cuba does observe daylight saving time, switching to Cuba Daylight Time (CDT), UTC−4, on the same second-Sunday-of-March and first-Sunday-of-November calendar the United States uses, though the transition happens at midnight local time rather than 2:00 a.m. So Cuba collides with the U.S. Central zone on both abbreviations: a Havana timestamp marked CST is one hour ahead of a Chicago timestamp marked CST, and a Havana timestamp marked CDT is one hour ahead of a Chicago one marked CDT.

The failure mode is not theoretical. A supplier in Shenzhen writes "the call is at 9:00 CST." A procurement system in Dallas parses CST as UTC−6 and books 15:00 UTC. The supplier meant 9:00 at UTC+8, which is 01:00 UTC. Nobody joins, and both sides believe the other missed the meeting. The same shape of error appears in log aggregation: ingest a Shanghai application log whose formatter printed the short zone name CST, parse it with a North American default, and every event in that file is now stamped fourteen hours late.

Java is the classic offender here because its legacy three-letter table resolves the identifier "CST" to America/Chicago, while a date formatted from Asia/Shanghai will happily print the short name CST. Format and re-parse the same instant and it moves half a day. Internet mail has the same legacy: RFC 5322 still lists the alphabetic zone forms and reads CST as the North American UTC−6, which is why every modern mail client writes a numeric offset like -0600 in the Date header instead.

The rule that avoids all of it: never let a three-letter abbreviation cross a system boundary. Use a numeric offset for display and an IANA identifier for storage.

Quick reference: Central Time across major hubs

The table below shows what 9:00 a.m. on a Tuesday in Chicago looks like in the cities most likely to be on the other end of the call, during the CST (winter) window and the CDT (summer) window. The receiving city's offset depends on its own daylight saving status, which is why several rows are not consistent between the two columns.

Worked examples

Example 1 — CST to UTC.A standup at 9:00 a.m. on Tuesday, January 13 in Chicago. Central is on CST that morning, so the offset is UTC−6. Add six hours: the meeting is 15:00 UTC on Tuesday, January 13 — a single unambiguous instant to store in a database. Check it against the UTC to CST conversion.

Example 2 — CDT to Central European Summer Time.A demo at 8:00 a.m. on Tuesday, July 14 in Dallas. Central is on CDT, UTC−5. Frankfurt is on CEST, UTC+2. Total shift: seven hours forward, so the demo is 15:00 in Frankfurt — comfortably inside the European working day, which is why 8:00 a.m. Central is the classic U.S.-to-Europe slot.

Example 3 — the Mexico drift.A weekly production sync at 10:00 a.m. Chicago time with a plant outside Guadalajara. From November to March, Chicago is UTC−6 and Mexico is UTC−6, so the plant sees 10:00. From March to November, Chicago is UTC−5 and Mexico has not moved, so the plant sees 9:00. The invite never changed; the U.S. side did. This has only been true since the 2022 Mexican law, so many long-running recurring meetings still carry an agenda written for the old behavior.

Example 4 — the CST collision.A supplier in Shanghai proposes "Thursday 09:00 CST." Read as China Standard Time (UTC+8) that is 01:00 UTC Thursday, which is 19:00 Wednesday in Chicago during CST season. Read as U.S. Central Standard Time it is 15:00 UTC Thursday, a full fourteen hours later and on a different day for one of the parties. When an abbreviation can move a meeting across a date boundary, insist on a city name or a numeric offset in the confirmation email.

Example 5 — the spring-forward gap. A nightly batch job scheduled for 2:30 a.m. local time in Chicago will never run on the second Sunday of March, because 2:00 a.m. skips straight to 3:00 a.m. and 2:30 does not exist that day. Conversely, on the first Sunday of November 1:30 a.m. happens twice, and a scheduler that fires on wall-clock pattern may run the job twice. Schedule in UTC where you can, or pick a time of day the transition cannot touch.

How modern software handles this

A calendar, database, or scheduler should never store "CST" or "CDT" as a time zone. Both are surface labels whose meaning depends on the date of the event and, as the section above shows, on the country of the person who wrote them. Store the IANA identifier and let the runtime compute the offset: America/Chicago for the U.S. Central zone, America/Winnipeg for Manitoba, America/Regina for Saskatchewan, America/Mexico_City for central Mexico, America/Havana for Cuba, and Asia/Shanghai for China.

Avoid the legacy POSIX-style zone CST6CDTthat still ships in tzdata. It hard-codes the U.S. rules under a name that looks like a generic description of the offset, so it will silently misrepresent Saskatchewan, Mexico City, and Havana — all of which are or were UTC−6 or UTC−5 at some point in the year but do not follow the U.S. schedule.

Storing IANA names solves three problems at once: the zone picks up future legislation automatically when tzdata is updated (the Mexican repeal shipped as a tzdata release within weeks), historical timestamps keep their meaning across past rule changes, and the abbreviation ambiguity never reaches your data at all because abbreviations are only ever generated for display.

Common mistakes

• Writing "CST" in July.Between March and November the U.S. Central zone is on CDT. The wall-clock hour is the same either way, but the offset differs (UTC−5 vs UTC−6), and a system that honors the literal abbreviation will resolve the event an hour off.
• Assuming Mexico still tracks Chicago.It did until 2022. It now stays on UTC−6 year-round outside Baja California and the border municipalities, so the Chicago-to-Mexico gap is zero hours in winter and one hour in summer.
• Treating Saskatchewan as a DST province. Regina never moves. A recurring Winnipeg-Regina call is the same hour from November to March and one hour apart from March to November.
• Forgetting that CDT and EST share an offset.Both are UTC−5. In summer, 14:00 CDT in Chicago is the same instant as 15:00 EDT in New York, not the same as anything labeled EST. The matching offsets make it easy to convince yourself the conversion is a no-op — see the CST to EST conversion for the winter case, where the gap really is one hour.
• Forgetting that CST and MDT share an offset. Likewise UTC−6. The CST to MST conversion is the standard-time comparison; in summer, Denver on MDT and Regina on CST read the same clock while carrying different letters.
• Hard-coding a fixed offset. Pinning UTC−6as "Central" is wrong for eight months of every year. Use America/Chicago and let a time-zone library resolve it.
• Accepting a bare abbreviation from a counterparty abroad.If the sender is in China or Cuba, "CST" does not mean what your calendar thinks it means. Ask for a city or a numeric offset.

Bottom line

Central Time has two abbreviations because the Uniform Time Act of 1966, as amended by the Energy Policy Act of 2005, splits the U.S. year into a four-month standard window and an eight-month daylight window: CST at UTC−6 from November to March, CDT at UTC−5 from March to November, with CT as the label that refuses to pick. The edges are where the money is lost — Saskatchewan sits on CST forever, most of Mexico has been frozen at UTC−6 since October 2022, and the letters CST simultaneously denote a zone in China fourteen hours away and a zone in Cuba one hour away. Store America/Chicago rather than a label, publish numeric offsets when you write to anyone outside North America, and treat any incoming three-letter abbreviation as a question rather than an answer.