US Time Zones by State and ZIP Code: Why the Lookup Table Is Wrong
Published November 15, 2026 by the USA Address Generator editorial team · Data Quality · 8 min read
More than a dozen states are split between time zones, Arizona mostly skips daylight saving, and the territories never change their clocks. How to store and derive a time zone for an address correctly.
"Which time zone is this customer in?" sounds like a lookup on the state field. For about three quarters of the states it is. For the rest, a state-level table sends appointment reminders an hour early, schedules deliveries for the wrong window and stamps reports with the wrong date. This guide covers where the simple table fails and what to store instead.
The zones
The United States and its territories use nine standard time zones. From east to west: Atlantic, Eastern, Central, Mountain, Pacific, Alaska, Hawaii-Aleutian, Samoa, and, on the far side of the date line, Chamorro.
| Zone | Typical IANA identifier | Where |
|---|---|---|
| Atlantic | America/Puerto_Rico | Puerto Rico, US Virgin Islands |
| Eastern | America/New_York | East coast, most of the eastern Midwest |
| Central | America/Chicago | Mississippi valley, Gulf coast, Great Plains |
| Mountain | America/Denver | Rocky Mountain states |
| Mountain, no daylight saving | America/Phoenix | Most of Arizona |
| Pacific | America/Los_Angeles | West coast, Nevada |
| Alaska | America/Anchorage | Most of Alaska |
| Hawaii-Aleutian | Pacific/Honolulu, America/Adak | Hawaii; the western Aleutian Islands |
| Samoa | Pacific/Pago_Pago | American Samoa |
| Chamorro | Pacific/Guam | Guam, Northern Mariana Islands |
States with more than one time zone
These states are divided between two zones. The descriptions are approximate; the legal boundaries follow county lines and, in places, run through counties.
| State | Split |
|---|---|
| Florida | Mostly Eastern. The western Panhandle, including Pensacola, is Central. |
| Tennessee | East Tennessee, including Knoxville and Chattanooga, is Eastern. Nashville and Memphis are Central. |
| Kentucky | The eastern half, including Louisville and Lexington, is Eastern. The western half is Central. |
| Indiana | Mostly Eastern. Counties in the northwest near Chicago and in the southwest near Evansville are Central. |
| Michigan | Eastern, except four Upper Peninsula counties on the Wisconsin border, which are Central. |
| Texas | Central, except the far west around El Paso, which is Mountain. |
| Kansas | Central, except a few counties on the Colorado border, which are Mountain. |
| Nebraska | The eastern two thirds are Central; the west is Mountain. |
| South Dakota | Roughly divided by the Missouri River: Central to the east, Mountain to the west. |
| North Dakota | Mostly Central; the southwest is Mountain. |
| Idaho | The south, including Boise, is Mountain. The northern Panhandle is Pacific. |
| Oregon | Pacific, except most of Malheur County on the Idaho border, which is Mountain. |
| Nevada | Pacific, except West Wendover on the Utah border, which is Mountain. |
| Alaska | Alaska time, except the Aleutian Islands west of 169 degrees 30 minutes west, which use Hawaii-Aleutian time. |
Several of the affected places are not small. Pensacola, El Paso, Chattanooga and Knoxville are all on the "other" side of their state's line from the state's largest cities. A state-level table that says Texas is Central and Tennessee is Central is wrong for hundreds of thousands of people in each.
Daylight saving time
Most of the country moves clocks forward in March and back in November. The exceptions:
- Hawaii does not observe daylight saving time.
- Arizona does not observe it, with one exception: the Navajo Nation, which extends into Arizona, New Mexico and Utah, does. The Hopi Reservation, which is surrounded by the Navajo Nation, follows the rest of Arizona and does not.
- Puerto Rico, the US Virgin Islands, Guam, the Northern Mariana Islands and American Samoa do not observe it.
The Arizona case is why a fixed offset is the wrong thing to store. Phoenix and Denver share an offset in winter and differ by an hour in summer. Storing "UTC minus 7" for an Arizona customer is right all year; storing it for a Colorado customer is wrong for most of the year.
What to store
Store an IANA time zone identifier, such as America/Chicago, not an abbreviation and not an offset.
- Abbreviations are ambiguous.
CSTis used for Central Standard Time and for China Standard Time, and it says nothing about whether daylight saving applies. - Offsets change twice a year for most places and are a property of a moment, not of a location.
- An IANA identifier carries the rules. Every mainstream language and database can convert a timestamp using one, including the daylight saving transitions and their history.
ALTER TABLE customers ADD COLUMN time_zone TEXT; -- e.g. 'America/Denver'
SELECT appointment_at AT TIME ZONE c.time_zone AS local_time
FROM appointments a
JOIN customers c ON c.id = a.customer_id;
new Intl.DateTimeFormat('en-US', {
timeZone: 'America/Phoenix',
dateStyle: 'medium',
timeStyle: 'short',
}).format(new Date('2026-07-01T18:00:00Z'));
// "Jul 1, 2026, 11:00 AM"
Timestamps themselves should be stored in UTC. The time zone is stored separately, as an attribute of the person or place, and applied when the time is shown.
How to derive the zone for an address
In rough order of reliability:
- Ask the user, or read it from their device. For anything that affects a person, such as reminders or meeting times, the device's zone is usually what they want, and it is available in the browser through
Intl.DateTimeFormat().resolvedOptions().timeZone. An address tells you where a parcel is going, not where its recipient is at the moment. - Geocode the address and look up the coordinates in a time zone boundary dataset. This is the only method that is right for split states and for the Navajo Nation, and it is what you need for delivery windows and opening hours at a physical location.
- Use a ZIP-to-time-zone table. Much better than a state table, and right for the great majority of ZIP codes. It is imperfect because ZIP codes are delivery routes, not areas, and a few of them cross a zone boundary.
- Use a state table. Acceptable only as a default that can be corrected, and only if the fourteen states above are treated as "unknown".
A reasonable compromise for many applications is a state table for the single-zone states, a county or ZIP table for the split ones, and a user-editable field on top.
Bugs to test for
- The date changes, not just the hour. An order placed at 9 pm Pacific on the last day of the month is already in the next month in UTC and in New York. Reports grouped by date need to say whose date.
- The missing and repeated hours. On the spring transition, 2:30 am does not exist; in autumn, 1:30 am happens twice. Recurring schedules stored as local times must decide what to do on those two nights.
- Guam is a day ahead. For most of the day, it is already tomorrow in Guam relative to the mainland. "Deliver by Friday" needs a zone.
- Arizona in summer. A test that passes in January can fail in July.
- A customer on the minority side of a split state. El Paso and Pensacola are good fixtures.
For test data, generated addresses from the address generator carry the IANA zone of their city, so a batch filtered to Arizona, Florida or Texas gives you records on both sides of the interesting lines. The city generator shows the zone alongside each city. As with ZIP codes, the tests that find these bugs are the ones that deliberately include the awkward places; a fixture set drawn entirely from one coast finds nothing. For why a ZIP code is an unreliable stand-in for a location, see the guide to ZIP code architecture.