CST Time Converter

The model, stated exactly

The US Central zone is America/Chicago in the IANA time-zone database. It observes Central Standard Time (CST, UTC−6) from the end of daylight saving until daylight saving resumes, and Central Daylight Time (CDT, UTC−5) the rest of the year. For the current cycle: daylight saving ran from March 8, 2026 to November 1, 2026, so CST runs from November 1, 2026 to March 14, 2027, and daylight saving then runs from March 14, 2027 to November 7, 2027. The converter never assumes the offset from the month: it tries each candidate offset (UTC−5, then UTC−6) for the entered wall time and keeps the one whose Chicago rendering reproduces the entered date and time exactly, reading the abbreviation from the database itself. Every output zone is then rendered from that UTC instant with Intl.DateTimeFormat. That is why the converter stays correct across the transitions, including the two awkward hours: 1 a.m. on a fall-back day occurs twice (the converter takes the first, daylight occurrence), and 2:30 a.m. on a spring-forward day does not exist at all (the converter reports it as an error instead of silently shifting it).

The worked example, line by line

Setup: Central date January 15, 2027, Central time 12:00.

Line 1 — the abbreviation. January is in the standard-time half, so the zone is CST (UTC−6).

Line 2 — the UTC instant. 12:00 plus 6 hours = 18:00 UTC on January 15, 2027.

Line 3 — New York. EST (UTC−5): 18:00 UTC = 13:00 EST on January 15.

Line 4 — Chicago. The entered time itself: 12:00 CST on January 15.

Line 5 — Denver. MST (UTC−7): 18:00 UTC = 11:00 MST on January 15.

Line 6 — Los Angeles. PST (UTC−8): 18:00 UTC = 10:00 PST on January 15.

Line 7 — Anchorage. AKST (UTC−9): 18:00 UTC = 09:00 AKST on January 15.

Line 8 — Honolulu. HST (UTC−10, no DST): 18:00 UTC = 08:00 HST on January 15.

Try these

October in the Central zone: noon on October 24, 2026. This is not CST — it is CDT (UTC−5), so the UTC instant is 17:00 UTC on October 24: 13:00 EDT in New York, 12:00 CDT in Chicago, 11:00 MDT in Denver, 10:00 PDT in Los Angeles, 09:00 AKDT in Anchorage, and 07:00 HST in Honolulu. Writing "CST" for this date would put every conversion an hour out.

Summer: noon on July 15, 2027. Again CDT (UTC−5) and again 17:00 UTC, with the same US times as the October example: 13:00 in New York, 12:00 in Chicago, 11:00 in Denver, 10:00 in Los Angeles, 09:00 in Anchorage, and 07:00 in Honolulu. Noon Central is 1 p.m. Eastern in both seasons — the UTC anchor is what moves, because both zones shift together.

The boundary days. Noon on November 1, 2026 is already CST (18:00 UTC), because daylight saving ended at 2 a.m. that morning; noon on March 13, 2027 is still CST, and noon on March 14, 2027 is CDT (17:00 UTC), because clocks sprang forward that morning.

Disambiguation: three different CSTs

The letters CST are reused around the world, and context is the only reliable guide. US Central Standard Time (this page) is UTC−6 in winter, with CDT (UTC−5) in summer — if the conversation is about Chicago, Houston, Dallas, or Minneapolis, this is the CST meant. China Standard Time is also abbreviated CST, but it is UTC+8 all year with no daylight saving — a full 14 hours ahead of US Central Standard Time; our China Time Converter covers it. Cuba Standard Time is also abbreviated CST (UTC−5 in winter, with its own daylight time, CDT) — if the conversation is about Havana, it is the Cuban clock, not Chicago's. When a message says only "CST" with no place attached, ask which country before converting: the same three letters can mean three clocks 14 hours apart.

Output · formula · meaning

Who uses this

• The scheduler writing "noon CST" in January: enters January 15, 2027 and confirms noon CST is 1 p.m. Eastern and 10 a.m. Pacific — and that the abbreviation is actually correct for that date.
• The manager who wrote "CST" for a July meeting: enters the July date, sees the converter label it CDT, and fixes the invitation before anyone joins an hour late.
• The traveler landing in Chicago in October: enters October 24, 2026 and learns noon local is CDT, 17:00 UTC — not the 18:00 UTC a winter CST conversion would give.
• The remote worker across three US zones: enters one Central time and reads off every US zone at once, including whether Honolulu (which never shifts) has drifted an hour relative to the mainland since the last meeting.

Accuracy & limitations

The conversion is exact for the IANA time-zone database in your browser, which is the same database operating systems and airlines use. Two caveats deserve daylight. First, the converter assumes the time you enter is a Central wall-clock time in America/Chicago — if a contact quotes you a time labeled only "CST" with no place, check the disambiguation section first, because China Standard Time (UTC+8) and Cuba Standard Time (UTC−5) share the abbreviation. Second, US daylight-saving rules have changed before (the current March-to-November pattern dates from 2007) and could change again by law; the converter follows whatever rules your browser's database currently carries, which is correct for scheduling today but may differ for far-future dates if the law changes. The fall-back hour (1 a.m. occurring twice) is resolved to its first, daylight occurrence, and the spring-forward gap hour is reported as an error rather than silently shifted. Error policy: empty, malformed, or impossible dates (such as February 30) and nonexistent Central times are reported as errors rather than calculated, so no result ever shows a rolled-over date.