Tukuk-OS🕒 Los Angeles to Chicago time
| Los Angeles on 2026-11-06 | 12:00 (GMT−8) |
| Chicago at that instant | 14:00 the same day (GMT−6) |
| Difference on this date | 2 hours (2026-01-01 to 2026-12-31) |
| 2026-01-01 to 2026-12-31 | 2 hours |
| Next clock change, Los Angeles | Sunday 14 March 2027 at 10:00 UTC |
| Next clock change, Chicago | Sunday 14 March 2027 at 08:00 UTC |
| 09:00 in Los Angeles is | 11:00 in Chicago |
| 12:00 in Los Angeles is | 14:00 in Chicago |
| 18:00 in Los Angeles is | 20:00 in Chicago |
| Shared 09:00–17:00 working window | 09:00–15:00 in Los Angeles, 11:00–17:00 in Chicago |
ℹ️ What this tool does & how it works
On 2026-11-06 the two clocks are apart by 2 hours, with Chicago ahead. Los Angeles runs on GMT−8 and Chicago on GMT−6. Across 2026 the difference runs: 2026-01-01 → 2026-12-31: 2 hours. Pick any date and time below and the page reworks the whole table from your own device.
Why Los Angeles and Chicago keep a fixed gap all year
Both places do change their clocks, and the gap still never moves, because the two moves are the same size on the same instant — Los Angeles and Chicago sit under rules that step together, which is what keeps them 2 hours apart through 2026. It is the most common arrangement inside a single bloc: the whole of the European Union, for example, turns its clocks at the same UTC moment, so no pair inside it ever has a moving difference despite both sides observing daylight saving.
The clock changes, and who decides them
Los Angeles uses the zone America/Los_Angeles, and its next change after 2026-11-06 is Sunday 14 March 2027 at 10:00 UTC. Chicago uses the zone America/Chicago, and its next change after 2026-11-06 is Sunday 14 March 2027 at 08:00 UTC. Neither figure is a physical fact: an offset is legislation, and the same fifteen degrees of longitude can sit under three zones because a border runs through it. That is why this page reads its offsets out of the time-zone database built into your own browser instead of hardcoding a table of abbreviations — it is the database your operating system already keeps current, and it is what puts Los Angeles and Chicago in the right relation even when a government moves a date at short notice. A device whose database predates the last change gets the old answer, which is the one caveat worth knowing.
What it is actually like to work across the two
Both places are inside their own 09:00–17:00 on 6 hours of the day: 09:00–15:00 in Los Angeles, 11:00–17:00 in Chicago — outside those hours somebody is starting early, finishing late or taking the call at midnight. The two clock rules here are not unique to these two places: 10 other cities in our dataset keep the same clock as one of them, including San Francisco, Seattle, Las Vegas, Vancouver, Portland, so looking any of those up against the city on the other side of the pair gives this page’s answers. The arithmetic is the three lines the page runs in front of you: read each zone’s offset for the date you picked, subtract, and let the modulo handle the dateline.