Time difference between Chicago and Catalina Foothills

Catalina Foothills is 2 hours behind Chicago.

America/Chicago America/Phoenix same day

Local time in both cities

Chicago · United States
08:23
Monday, 21 September 2026
America/Chicago · UTC-05:00
Catalina Foothills · United States
06:23
Monday, 21 September 2026
America/Phoenix · UTC-07:00

Catalina Foothills is 2 hours behind Chicago.

same day

Time zones

ChicagoAmerica/Chicago · UTC-05:00
Catalina FoothillsAmerica/Phoenix · UTC-07:00

Chicago is currently on daylight saving time (UTC-05:00). Next change: 2026-11-01 01:00.

Catalina Foothills does not observe daylight saving and stays on UTC-07:00 all year.

Hour-by-hour conversion

Calculated for 2026-09-21 local time in Chicago. The two places start and end daylight saving on different dates, so another day can give a different result.

Chicago (source) Catalina Foothills (target)
00:00 22:00 prev day
01:00 23:00 prev day
02:00 00:00
03:00 01:00
04:00 02:00
05:00 03:00
06:00 04:00
07:00 05:00
08:00 06:00
09:00 07:00
10:00 08:00
11:00 09:00
12:00 10:00
13:00 11:00
14:00 12:00
15:00 13:00
16:00 14:00
17:00 15:00
18:00 16:00
19:00 17:00
20:00 18:00
21:00 19:00
22:00 20:00
23:00 21:00

FAQ

How many hours apart are Chicago and Catalina Foothills right now?
The answer at the top of the page is calculated for the current moment and states which side is ahead. The gap changes during the year, because the two places usually start and end daylight saving on different dates.
Is this difference the same all year?
Not necessarily. Chicago uses America/Chicago and Catalina Foothills uses America/Phoenix; if either observes daylight saving, the gap shifts during the year. Use “Convert a specific date and time” below to calculate it for a given day.
How do I read the conversion table?
The left column lists each whole hour in Chicago; the right column is the local time in Catalina Foothills at that same instant, with date rollovers marked. On the day clocks jump forward, some hours do not exist locally — the table says so instead of showing a plausible but wrong value.

Both cities