What UTC Offset Is CST? UTC-6 and UTC-5 Explained

Central Standard Time is UTC-6. The Central zone shifts to UTC-5 during summer daylight saving time. The offset you need depends entirely on the date.

CST Is UTC-6: What That Number Means

Someone in Chicago says "meet at 2:00 p.m. Central." Your calendar is in UTC. What do you type?

8:00 p.m. UTC. Central Standard Time sits at UTC-6. Six hours behind the global reference clock.

The number is not arbitrary. UTC-6 means the zone is geographically centered on the 90th meridian west of Greenwich, England. That line runs roughly through the middle of the Mississippi Valley. "Central Standard Time" and "UTC-6" describe exactly the same clock; one is the name, the other is the coordinate.

Put it in practice: when UTC reads 18:00, Central reads 12:00 noon. Subtract six, and you have it. That is the entire conversion for winter dates.

CDT Is UTC-5: The Summer Offset

Now the complication. The offset is not fixed all year.

From the second Sunday in March to the first Sunday in November, the Central zone observes daylight saving time and shifts to Central Daylight Time, whose offset is UTC-5. Five hours behind UTC, not six. The clocks move forward one hour in spring, and they do not come back until autumn.

So the honest complete answer to "what UTC offset is CST" is this: CST itself is always UTC-6, but the Central zone as a whole alternates between UTC-6 in winter and UTC-5 in summer. If you are converting a date in July, you almost certainly want UTC-5, even if someone loosely wrote "CST."

A meeting in July at 2:00 p.m. Central is 7:00 p.m. UTC, not 8:00. Getting this wrong puts you an hour early. You miss the call entirely.

The 2026 Switch Dates

For 2026, the clocks change on these dates:

  • Spring forward: Sunday 8 March 2026 at 02:00 local. Clocks jump to 03:00. CST (UTC-6) becomes CDT (UTC-5).
  • Fall back: Sunday 1 November 2026 at 02:00 local. Clocks retreat to 01:00. CDT (UTC-5) becomes CST (UTC-6).

For 2027, the dates shift:

  • Spring forward: Sunday 14 March 2027 at 02:00 local.
  • Fall back: Sunday 7 November 2027 at 02:00 local.

Mexico City Stays Put

Mexico City sits in the same IANA zone family but does not follow the same clock. Mexico abolished nationwide DST in October 2022. The capital, on America/Mexico_City, stays fixed at UTC-6 all year.

The result: Chicago and Mexico City share the same clock from November through March. From March through November, Chicago springs forward to UTC-5 while Mexico City holds at UTC-6. A noon call between the two cities in July means noon in Mexico City and 1:00 p.m. in Chicago.

Northern border municipalities like Matamoros and Ojinaga are the exception. They continue to observe the US DST schedule for economic reasons, so they match their US neighbours year-round.

UTC vs GMT: The Reference Standard Explained

Why does everything route through UTC? Because UTC is the anchor of the entire time-zone system.

Every zone on Earth is defined as a number of hours ahead of or behind it. UTC itself never changes for daylight saving. That fixed reference is what makes conversions reliable: instead of comparing two moving local clocks, you translate each one to UTC and back.

GMT is effectively UTC+0, but technically it is a time zone. UTC is a time standard. They line up to the same minute in practice, but the distinction matters when you read an ISO 8601 timestamp or parse a log file. GMT is a place on the map; UTC is the clock everything else is measured against.

How Offsets Work: Negative Numbers Mean Behind UTC

A negative offset means the zone is behind UTC. When UTC says noon, a zone at UTC-6 says 6:00 a.m. The sun rises later there because the Earth rotates west to east, and the zone sits west of Greenwich.

This is why the sign matters. UTC+6 (like Bangladesh) is ahead of UTC. UTC-6 (like Central) is behind. The convention is universal, and it is the first thing to check when you see an offset written as "+05:30" or "-08:00."

CST in ISO 8601 Format: -06:00 and -05:00

If you work with APIs, databases, or scheduling software, you will see the offset written in ISO 8601 format. It looks like this:

  • Winter (CST): 2026-01-15T10:00:00-06:00
  • Summer (CDT): 2026-07-15T10:00:00-05:00

The time portion is the local clock. The offset at the end tells you how far that local time is from UTC. To convert to UTC, add the offset back. Ten in the morning minus six hours is 16:00 UTC in winter. Ten in the morning minus five hours is 15:00 UTC in summer.

The format is unambiguous, which is exactly why it exists. No need to guess whether "10:00" means Central or something else.

Real Offsets on Real Dates

On 15 January 2026, when the zone is on CST (UTC-6), here is how other cities line up against Chicago:

  • New York: 1 hour ahead
  • Los Angeles: 2 hours behind
  • London: 6 hours ahead
  • Paris: 7 hours ahead
  • Dubai: 10 hours ahead
  • Mumbai: 11.5 hours ahead
  • Singapore: 14 hours ahead
  • Tokyo: 15 hours ahead
  • Sydney: 17 hours ahead
  • Johannesburg: 8 hours ahead
  • São Paulo: 3 hours ahead

On 15 July 2026, when the zone is on CDT (UTC-5), the gaps shift:

  • New York: 1 hour ahead
  • Los Angeles: 2 hours behind
  • London: 6 hours ahead
  • Paris: 7 hours ahead
  • Dubai: 9 hours ahead
  • Mumbai: 10.5 hours ahead
  • Singapore: 13 hours ahead
  • Tokyo: 14 hours ahead
  • Sydney: 15 hours ahead
  • Johannesburg: 7 hours ahead
  • São Paulo: 2 hours ahead

Dubai, Mumbai, Singapore, Tokyo, Sydney, Johannesburg, and São Paulo all shift by one hour relative to Central. They do not observe DST, or they observe it on different dates. London and Paris stay at the same gap because their DST periods roughly align.

What Is the UTC Offset for CST in Code and Scheduling?

For developers, the offset is the only thing that matters. Unix timestamps are always UTC-based. They count seconds from January 1, 1970, at UTC, with no time zone attached. When you display a timestamp to a user in Chicago, you apply the offset at display time, not at storage time.

That is why your server logs are in UTC, why your database stores UTC, and why your frontend converts to local time. The offset is the translation layer. Get it wrong, and you schedule a meeting at the wrong hour, send a notification at 3:00 a.m., or log a timestamp that is off by six hours.

The CST Ambiguity Trap

"CST" is not unique. It also stands for China Standard Time (UTC+8) and Cuba Standard Time (UTC-5). In international contexts, "CST" without a qualifier is ambiguous. Use "America/Chicago" or "UTC-6" for clarity.

"Central Time" (CT) is the safe umbrella term covering both CST and CDT. Many people say "CST" year-round out of habit. A "6 p.m. CST" meeting invitation in July is technically wrong. It should say CDT. Most people understand what was meant, but the offset removes all ambiguity.

Professions That Depend on the Offset

  • Remote team managers and HR: scheduling across zones
  • TV and radio producers: broadcast schedules, "8/7c" notation
  • Airline and travel agents: flight times, connections
  • Software developers: timestamp handling, UTC conversions, logging
  • Financial traders: market open/close across global exchanges
  • Customer support teams: SLAs, coverage hours
  • Event planners and webinar hosts: registration deadlines, live stream times
  • Military and government contractors: Zulu time coordination
  • Trucking and logistics: delivery windows, driver hours of service
  • Telemedicine providers: appointment scheduling across state lines

What UTC Offset Does CST Use in Winter vs Summer?

Central Standard Time is UTC-6. Central Daylight Time is UTC-5. The zone switches between them twice a year, and the switch dates follow the second Sunday in March and the first Sunday in November.

If you schedule across zones, work with APIs, or just want to stop being confused by meeting invitations, learn the offset. It is the single most useful fact about this time zone.

And if you are the one sending the invitation, write the offset explicitly. Do not make your colleagues in London or Tokyo guess whether you meant winter or summer time.