Phoenix is 7 hours behind UTC in winter and 7 hours behind UTC in summer — 7 hours behind UTC in winter. Its standard offset is UTC−07:00, and it does not observe daylight saving, so the difference never changes. This page explains the difference, shows it month by month, and gives the conversion tables in both directions.
Try the tool: UTC Converter — convert any time between UTC and Phoenix, with the offset for the date you pick.
How far is Phoenix from UTC?
The difference between Phoenix and UTC is the offset: UTC−07:00 in standard time. When it is noon in Phoenix, it is already afternoon or evening in London — the day at Greenwich is 7 hours ahead the day in Phoenix. The sign matters: a positive offset means ahead of UTC (east of Greenwich), a negative offset means behind it (west of Greenwich).
In practical terms, the difference means that the working day in Phoenix (09:00–17:00 local) is 16:00–00:00 UTC in January and 16:00–00:00 UTC in July. A team that schedules in UTC needs to know both numbers, because a meeting set for 15:00 UTC is 08:00 in Phoenix in January and 08:00 in July — and one of those may be outside the working day even when the other is inside it.
Phoenix vs UTC through the year
The offset on the 15th of each month in 2026. If the table shows one value all year, Phoenix does not observe daylight saving. If it shows two values, the change between them is the clock change.
| Month | Offset from UTC |
|---|---|
| January | UTC−07:00 |
| February | UTC−07:00 |
| March | UTC−07:00 |
| April | UTC−07:00 |
| May | UTC−07:00 |
| June | UTC−07:00 |
| July | UTC−07:00 |
| August | UTC−07:00 |
| September | UTC−07:00 |
| October | UTC−07:00 |
| November | UTC−07:00 |
| December | UTC−07:00 |
The clock changes are: in 2026, none; in 2027, none. For the full story, see the Phoenix DST 2026 page and the daylight saving checker.
Conversion tables
UTC to Phoenix, for eight hours of the day:
| UTC | Phoenix (January) | Phoenix (July) |
|---|---|---|
| 00:00 | 17:00 | 17:00 |
| 03:00 | 20:00 | 20:00 |
| 06:00 | 23:00 | 23:00 |
| 09:00 | 02:00 | 02:00 |
| 12:00 | 05:00 | 05:00 |
| 15:00 | 08:00 | 08:00 |
| 18:00 | 11:00 | 11:00 |
| 21:00 | 14:00 | 14:00 |
Phoenix to UTC, for the same eight hours:
| Phoenix local | UTC (January) | UTC (July) |
|---|---|---|
| 00:00 | 07:00 | 07:00 |
| 03:00 | 10:00 | 10:00 |
| 06:00 | 13:00 | 13:00 |
| 09:00 | 16:00 | 16:00 |
| 12:00 | 19:00 | 19:00 |
| 15:00 | 22:00 | 22:00 |
| 18:00 | 01:00 | 01:00 |
| 21:00 | 04:00 | 04:00 |
Two things to watch in these tables. First, the date: a UTC time in the evening is the next day in Phoenix when the offset is positive — 21:00 UTC is 14:00 the next day in Phoenix in January — and a Phoenix time early in the morning is the previous day in UTC when the offset is positive. Second, the season: the January and July columns are identical, because the offset never changes. The UTC to Phoenix page has the full 24-hour table.
Daylight saving and the difference
Phoenix does not observe daylight saving, so the difference from UTC is constant: UTC−07:00 on every day of the year. Arizona opted out of daylight saving in 1968, under the federal law that lets states exempt themselves. The reason is the desert heat: an extra hour of evening sun would mean an extra hour of air conditioning, not an extra hour outdoors. The Navajo Nation inside Arizona does observe it. That constancy is an advantage for scheduling — the difference never moves — but it also means the difference between Phoenix and any place that does observe daylight saving moves twice a year, when the other place changes its clocks. The difference between Phoenix and New York, for example, is 2 hours behind in January and 3 hours behind in July.
What the difference means for scheduling
For a team that works in UTC — software, aviation, science — the difference is the number you add to every UTC time to get Phoenix time, and the number you subtract from every Phoenix time to get UTC. The mistake is to use one number all year when there are two. The safe habit is to put the UTC time in every invitation as well as the local time, and to let the calendar do the conversion: a calendar event set in UTC moves correctly when daylight saving changes, and an event set in local time does not always.
For comparison, two other major cities: London is the same time UTC in January and 1 hour ahead UTC in July, and Tokyo is 9 hours ahead UTC all year. Phoenix's difference of 7 hours behind (January) sits between them in the sense that matters for scheduling: a meeting at 14:00 UTC is 07:00 in Phoenix, 14:00 in London and 23:00 in Tokyo in January. The time in Phoenix page has the working-hours tables, and the meeting planner finds the overlap for any pair of cities.
Phoenix vs UTC: the numbers at a glance
| Fact | Value |
|---|---|
| Standard offset | UTC−07:00 |
| Daylight saving offset | — does not observe daylight saving |
| Offset in January 2026 | UTC−07:00 |
| Offset in July 2026 | UTC−07:00 |
| Difference from UTC in January | 7 hours behind |
| Difference from UTC in July | 7 hours behind |
| IANA time zone | America/Phoenix |
| Country | United States |
Adjusting to the difference — travel and jet lag
Travelling to Phoenix from London means setting your watch back by 7 hours in January — you gain time going west, and the first day feels long. Travelling the other way, from Phoenix to London, you lose the hours. The rule of thumb for jet lag is that it takes about a day to adjust for each hour of difference when travelling east, and a little less when travelling west — so the return trip from Phoenix to London takes most travellers about 7 days to fully adjust to, while the outward trip is usually easier. The practical advice is the same in both directions: get sunlight in the morning at your destination, avoid naps longer than 20 minutes, and do not schedule important meetings for the first morning after you arrive.
The same arithmetic applies to remote work. If you are in Phoenix and your team works in UTC, your working day of 09:00–17:00 local time is 16:00–00:00 UTC in January — so a stand-up at 09:00 UTC is 02:00 for you, and a stand-up at 16:00 UTC is 09:00. If those times are outside your working day, the meeting is in the wrong place in the day, and the fix is to move the UTC time, not to ask one person to work at midnight. The meeting time finder finds the hours that work for a whole team, and the time in Phoenix page has the working-hours tables.
Frequently asked questions
How many hours is Phoenix ahead of UTC?
Phoenix is 7 hours behind UTC in January and 7 hours behind UTC in July. The difference is the same all year.
Is Phoenix ahead of or behind UTC?
Phoenix is behind UTC — its offset is negative (UTC−07:00 in January), so local time is earlier than UTC.
Does the time difference between Phoenix and UTC change?
No. Phoenix does not observe daylight saving, so the difference of 7 hours behind never changes.
What is Phoenix's UTC offset?
Phoenix's standard offset is UTC−07:00, all year. Its IANA time zone is America/Phoenix.
When it is midnight UTC, what time is it in Phoenix?
It is 17:00 in January and 17:00 in July — the previous day, because the offset is negative.
Sources
- IANA Time Zone Database, via Node.js Intl (
Intl.DateTimeFormatwithtimeZone) — offsets, daylight saving dates and local times in this article were worked out from the IANA database, not typed from memory. - TimeFlow's own time-zone data (
data/cities.ts,data/dst.ts), computed from the IANA database. - TimeFlow's UTC converter and world clock — the live tools behind the numbers on this page.
- Time-zone and daylight saving rules are set by governments and can change. For flights, deadlines and meetings that cannot move, confirm the time with an official source.