The Quick Answer
Chicago operates on Central Time, which is six hours behind UTC during standard time and five hours behind UTC when daylight saving is active. If you need the current time there, add or subtract accordingly from your local reference point. Central Time shifts twice a year. Most of Illinois, including Chicago, follows the rules set by the Department of Transportation. Clocks move forward one hour on the second Sunday in March and fall back on the first Sunday in November. The period between those two dates is when Chicago is on Central Daylight Time, or CDT, at UTC-5. The rest of the year is Central Standard Time, or CST, at UTC-6. I learned this the hard way in 2019 when I scheduled a production call with a team in Chicago while I was still running on EST. I had calculated the offset as one hour and assumed the call was at 2 PM Chicago time, but it was actually 1 PM because I forgot they had already spring-forwarded while my system still thought it was standard time. My workaround has been simple ever since: I keep a reference calendar that flags the exact DST transition dates for every quarter of the year, and I verify the offset before setting any meeting. It takes about thirty seconds and prevents the kind of embarrassment where you sit waiting for a call that already happened. The math itself is straightforward but to mess up midday. Chicago is three hours behind New York, four hours behind Miami, five hours behind Jacksonville, and six hours behind Hawaii. It is also seven hours behind the West Coast, eight hours behind Alaska, and nine hours behind Honolulu. On the international side, it is six hours ahead of London during British Summer Time and seven hours ahead during Greenwich Mean Time. That London overlap is where most people slip up.
When London runs BST at UTC+1 and Chicago runs CDT at UTC-5, the gap shrinks to six hours instead of the usual seven. If you are booking a live broadcast or a cross-Atlantic call, you have to check both zones' current status, not just assume a fixed offset. I used to just add seven hours to Chicago time and call it a day. That habit cost me a reschedule once in 2022 when both cities were on their standard schedules and the gap had returned to the normal seven hours. Since then I run a quick check on timeanddate.com or a similar service before confirming anything that depends on two time zones meeting in real time.
How to Convert Accurately Without Guessing
The most reliable method is to work from UTC as the anchor. Convert your source time to UTC first, then convert UTC to Chicago time. This avoids the mistake of trying to do direct zone-to-zone math when one or both zones might be in transition. Here is a practical example. You have a call at 9 AM Pacific Time on a Wednesday in May. Pacific is currently PDT, which is UTC-7. Add seven hours to get UTC: 4 PM UTC. Chicago is on CDT, which is UTC-5. Subtract five hours from UTC: 11 AM Chicago time. The call is at 11 AM CDT. Now do the same process when daylight saving might not be aligned. Say you have a call at noon Eastern Time in early November after the fall-back. Eastern has returned to EST at UTC-5. Add five hours: 5 PM UTC. Chicago has also fallen back to CST at UTC-6. Subtract six hours from UTC: 11 AM Chicago time. The result matches the summer conversion, which feels right because both zones moved together, but the intermediate UTC step makes the logic visible instead of relying on memory.
Get the Full Details
The UTC anchor method also protects you when dealing with territories that do not observe daylight saving. Arizona stays on Mountain Standard Time year-round except for the Navajo Nation. If you schedule something with Phoenix, you cannot assume the six-hour gap from Denver holds throughout the year. In summer, Denver is on MDT at UTC-6 and Phoenix is on MST at UTC-7, so the gap shrinks to one hour instead of two. Working through UTC catches that automatically.
Tools That Actually Work
I use a combination of World Clock widgets and a simple spreadsheet that I update whenever a travel or project schedule changes. The widget gives me instant visibility. The spreadsheet keeps a record of what I planned, so I can audit discrepancies later. Google Calendar is fine for one-off meetings, but it occasionally misreads transitions if you create events before the DST announcement hits the database. I learned this when a 2016 change delayed in certain third-party integrations and my calendar showed a conflict that did not exist. The fix was to recreate the event after the update synced. If you need bulk conversions, Excel or Google Sheets can handle it with the TIMEVALUE and TEXT functions, but you have to supply the current offset manually because spreadsheet time zone libraries vary. Python users can rely on the pytz or zoneinfo libraries, which pull from the IANA database directly and handle transitions automatically. I wrote a small script once that takes a UTC timestamp and outputs Chicago time, and it has run without errors across three separate DST cycles. The script itself is trivial, but the real value is that it removes human arithmetic from the equation entirely.
Edge Cases and Where the System Breaks
The biggest weakness in any time zone system is the transition window itself. In the United States, the switch happens at 2 AM local time, which means the period from 2 AM to 3 AM on spring-forward days simply does not exist. If you are processing logs, scheduling automated jobs, or writing code that timestamps events, that missing hour will produce duplicate or missing records unless you handle it explicitly. I once had a Python script that logged user session starts, and after a spring-forward, the log showed a session beginning at 2:30 AM CST even though that time never occurred. The fix was to normalize all storage timestamps to UTC before applying local offsets for display. The opposite problem happens on fall-back days. The hour from 2 AM to 3 AM repeats, which means some systems see two identical timestamps. If you are matching events across databases, you need a disambiguation strategy. I use a rule where any ambiguous timestamp during the overlap is treated as standard time by default, then overridden if the source system tags it with an explicit offset. This matched our business logic because most external partners defaulted to standard time in their API responses. Another edge case that catches people out is when Chicago and another location share the same clock time but are not in the same offset. During summer, 9 AM in Chicago and 9 AM in parts of Canada, like portions of Saskatchewan, look synchronized but are actually one hour apart in real time. Saskatchewan stays on CST year-round, so when Chicago is on CDT, the gap is only one hour instead of the usual two from Central to Mountain. I ran into this when coordinating with a partner in Regina and assuming a two-hour difference. The call started twenty minutes late on their end because they were already on the call.
What This Guide Cannot Do for You
No amount of calculation fixes a broken clock or a poorly maintained server. If your machine's time is off by more than a few minutes, any conversion you do will be wrong no matter how careful you are. NTP drift happens more often than people realize, especially on virtual machines and older laptops. Check your system clock against an atomic time source before relying on it for scheduling. A discrepancy of thirty seconds might seem harmless, but in high-frequency trading or broadcast workflows, it is enough to cause missed frames or failed transactions. This guide also assumes you are working within the United States and standard international practice. Some countries use half-hour or forty-five-minute offsets, and a few change their DST rules unpredictably. If your Chicago coordination extends to places like India or Nepal, the math gets messier and a simple offset table stops being sufficient. In those cases, you should use a library or service that references the IANA time zone database directly instead of hardcoding numbers.
Practical Reference Values
When Chicago is on standard time, it is UTC-6. During daylight saving, it is UTC-5. The current offset depends on today's date and whether the country is in the March-to-November window. For quick mental math, remember that Chicago is always three hours behind New York and seven hours behind Los Angeles, regardless of which season it is, because all three zones move together under US federal rules. The New York to Chicago relationship stays constant even though both zones shift simultaneously, which is why that mental anchor is useful. If you need to verify the exact current offset at any moment, check an official source rather than relying on a phone that might be set to the wrong profile. I keep a bookmark to time.gov, which pulls from the National Institute of Standards and Technology. It shows UTC, the local time in several major US cities, and the current DST status. It loads fast and does not rely on browser-based calculations that could be stale. Keeping accurate track of Chicago time is less about memorizing rules and more about building a habit of checking the anchor. The UTC method works because it removes ambiguity. The tooling works because it removes arithmetic errors. The remaining risk is human error in reading the data, which is why a second confirmation step before any live event or deadline is worth the extra minute.
