MST vs MDT: Why Mountain Time Has Two Abbreviations (And Arizona Only One)

Mountain Time has two abbreviations because it has two clocks. MST — Mountain Standard Time — is UTC−7 and runs through the winter. MDT — Mountain Daylight Time — is UTC−6 and runs through the summer. MTis the generic label meaning "whichever one is in effect right now." For Denver, Salt Lake City, and Albuquerque that is the entire rule. Then there is Arizona, which never moves its clocks — except for the Navajo Nation, which does, except for the Hopi Reservation sitting inside the Navajo Nation, which does not. If you only need the arithmetic, the timezone converter handles it.

That nesting is not trivia. It is the reason Mountain Time is the hardest of the four continental U.S. zones to get right in software, and the reason the IANA time zone database needs two separate identifiers — America/Denver and America/Phoenix— for a region that shares a single UTC offset for four months of the year. This article covers the rule, the transition dates, the Arizona exception in detail, the 2026 changes redrawing the zone's northern edge, and the scheduling mistakes that follow from all of it.

The rule in one sentence

Mountain Standard Time (MST) is UTC−7 and is in force from the first Sunday in November to the second Sunday in March. Mountain Daylight Time (MDT) is UTC−6 and is in force from the second Sunday in March to the first Sunday in November. MTmeans "Mountain Time, whichever is currently in effect," and it is what broadcasters, airlines, and most publishers use to sidestep the question entirely.

Two offsets are worth memorizing alongside those. MDT (UTC−6) is the same offset as Central Standard Time, and MST (UTC−7) is the same offset as Pacific Daylight Time. That means Mountain Time is never more than one hour from either neighbor, but which neighbor it matches flips twice a year — and the flip is what breaks recurring calendar entries.

What the abbreviations actually mean

The three-letter framework is consistent across the U.S. zones. The first letter is the region (Pacific, Mountain, Central, Eastern, Atlantic, Hawaiian). The second letter is either Standard or Daylight. The third is always Time. So:

• MST— Mountain Standard Time, UTC−7. The winter clock setting across the Mountain Time Zone, and the year-round setting in most of Arizona.
• MDT— Mountain Daylight Time, UTC−6. The summer clock setting, observed from March to November everywhere in the zone except the Arizona exceptions below.
• MT— Mountain Time, generic. A schedule that says "7:00 p.m. MT" means whichever Mountain clock is running on the day of the event. It is deliberately non-committal, and for published schedules that is usually the right call.

The same pattern produces PST/PDT/PT, CST/CDT/CT, and EST/EDT/ET. Hawaii uses HST (UTC−10) with no daylight saving at all; Alaska uses AKST and AKDT. The pattern is so regular that people assume the underlying behavior is regular too, which is exactly where Mountain Time catches them out.

When does each one apply

The U.S. Department of Transportation holds jurisdiction over the country's time zones and the dates of daylight saving transitions, under authority established by the Uniform Time Act of 1966. The current schedule comes from the Energy Policy Act of 2005, which took effect in 2007 and lengthened U.S. daylight saving time by roughly four weeks. Under those rules:

• Spring forward: the second Sunday in March, at 2:00 a.m. local time, clocks jump from 2:00 to 3:00. MST ends; MDT begins.
• Fall back: the first Sunday in November, at 2:00 a.m. local time, clocks fall from 2:00 back to 1:00. MDT ends; MST begins.

That puts the 2026 transitions on Sunday, March 8 (MST ends, MDT begins) and Sunday, November 1 (MDT ends, MST begins). In 2027 they fall on Sunday, March 14 and Sunday, November 7. Both switches happen at 2:00 a.m. local time, which means they do not happen simultaneously across the country — the Eastern zone switches an hour before Central, which switches an hour before Mountain.

Note the asymmetry: MDT covers roughly eight months of the year and MST roughly four. People who mentally split the year in half consistently overestimate how often MST applies. If you are writing a date in April, May, June, July, August, September, or October, the correct abbreviation is MDT. If you write "MST" for a summer meeting and a system takes you literally, you have just moved the meeting an hour. Use the MST to MDT conversion when you need to see that one-hour step in isolation.

Where Mountain Time actually applies

The zone runs down the spine of the continent and is the least populated of the four contiguous U.S. zones. It covers:

• Entirely: Colorado, Utah, Wyoming, New Mexico, Montana, and Arizona.
• Partly:southern Idaho (Boise, Idaho Falls — the northern panhandle is Pacific), western Kansas, western Nebraska, western North and South Dakota, western Texas (El Paso), and a western sliver of Oregon's Malheur County.
• In Canada: Alberta (Calgary, Edmonton) and the eastern edge of British Columbia — though both are changing in 2026, covered below.
• In Mexico: the state of Sonora, which sits on MST year-round like neighboring Arizona, and the border municipios of Chihuahua around Ciudad Juárez, which follow the U.S. MST/MDT schedule to stay aligned with El Paso.

Denver is the zone's largest metro and its default reference point; Phoenix is larger still but, as the next section explains, is not on the same clock for most of the year.

Arizona: the state that opted out

Arizona is in the Mountain Time Zone and does not observe daylight saving time. This is not an informal practice — it is statute. Arizona Revised Statutes § 1-242 sets the state's standard time as the solar time of the 105th meridian west, "commonly known as standard mountain time," and then states that notwithstanding any federal provision on the adoption of daylight saving time, Arizona "elects to reject such time." The state observed DST in 1967, disliked it, and repealed it by Arizona Laws 1968, chapter 183, effective 21 March 1968. The tz database records that date as the last transition America/Phoenix will ever have.

The Uniform Time Act permits exactly this. A state may opt out of daylight saving entirely; what it may not do is observe DST on its own idiosyncratic dates. Arizona and Hawaii are the two states that took the opt-out.

The practical consequence is that Arizona swaps neighbors twice a year. Phoenix stays at UTC−7 permanently:

• March to November: Phoenix matches Pacifictime. Los Angeles is on PDT (UTC−7), so Phoenix and Los Angeles share a wall clock, and Phoenix is one hour behindDenver, which is on MDT (UTC−6).
• November to March: Phoenix matches Mountaintime. Denver is on MST (UTC−7), so Phoenix and Denver share a wall clock, and Phoenix is one hour ahead of Los Angeles, which is on PST (UTC−8). The MST to PST conversion covers that winter gap.

This is the single most common Mountain Time mistake in business software: a recurring Phoenix–Denver call booked in December looks stable for three months and then silently slides by an hour in March, because Denver moved and Phoenix did not.

The reservations inside the exception

Arizona's opt-out is not statewide, and the geography of the carve-outs is genuinely unusual.

• The Navajo Nation observes DST.The Navajo Nation spans northeastern Arizona, northwestern New Mexico, and southeastern Utah. Because two of those three states observe daylight saving, the Nation follows the standard U.S. schedule so that its own territory keeps one consistent time across state lines. Tribal nations are not bound to the time practices of the jurisdictions around them, and the Navajo Nation is the most visible exercise of that. So from March to November, Window Rock is on MDT while Phoenix, four hours' drive south, is still on MST.
• The Hopi Reservation does not. The Hopi Reservation — about 2,530 square miles across Navajo and Coconino counties — is surrounded entirely by the Navajo Nation. It is not part of it, and it does not observe daylight saving. It stays on MST year-round, like the rest of Arizona.

Stack those and you get a DST-observing territory enclosing a non-observing one, both inside a state that does not observe DST, in a country that mostly does. During the summer months, driving east on Arizona State Route 264 from Tuba City crosses in and out of Hopi and Navajo land repeatedly — six changes of clock in under 100 miles. Both Moenkopi villages, near Tuba City, are Hopi and stay on MST; the land around them is Navajo and is on MDT.

This is the mirror image of the pre-1966 chaos the Uniform Time Act was written to end, except that here it is entirely lawful and entirely intentional on all sides. For anyone dispatching field crews, scheduling deliveries, or running clinic appointments across northeastern Arizona in summer, the practical rule is to name the community, not the state.

2026: the zone's northern edge is moving

Two Canadian jurisdictions changed their time observance in 2026, and both affect what "Mountain Time" means north of the border.

• Alberta has left the MST/MDT cycle.Bill 31, the Red Tape Reduction Statutes Amendment Act, 2026, repealed Alberta's Daylight Saving Time Act and replaced it with the Official Time Act, which fixes the province's standard time at UTC−6. The bill received Royal Assent on 14 May 2026 and the relevant section was proclaimed in force on 18 June 2026 by Order in Council 204/2026; a companion order prescribes the official term "Alberta Time." Because Alberta was already at UTC−6 on MDT when the act came into force, nothing visibly changed at the time. The visible change comes on 1 November 2026, when Calgary and Edmonton simply will not fall back. From that date Alberta sits one hour ahead of Denver every winter, on the same clock as Winnipeg and Chicago.
• British Columbia has gone the other way.B.C. adopted permanent year-round daylight saving; its final clock change was the spring-forward on 8 March 2026, and it will not turn clocks back on 1 November 2026 either. The province's new year-round zone is legally called "Pacific time" and sits at UTC−7— the same offset as MST. Vancouver therefore matches Denver's winter clock and trails it by an hour in summer, a reversal of the old relationship.

There is a wrinkle worth knowing if you read raw time zone data. The tz database labels British Columbia's new permanent UTC−7 with the abbreviation MST, not because B.C. joined Mountain Time but because tzdata and POSIX require zone abbreviations of three to six alphanumeric characters, and "PT" is one character too short. If you see a Vancouver timestamp tagged MST in 2027, that is the reason.

The Regional District of East Kootenay in southeastern B.C., which has historically kept step with Alberta on MST/MDT, has been debating a move to year-round MST; as of this writing the decision has been reopened and no change is in the tz database.

Quick reference: Mountain Time across major hubs

The table shows what 9:00 a.m. on a Tuesday in Denver looks like elsewhere, in the MST (winter) and MDT (summer) windows. Denver at 9:00 MST is 16:00 UTC; Denver at 9:00 MDT is 15:00 UTC. The Canadian rows reflect the post-1 November 2026 arrangement.

Worked examples

Example 1 — MST to UTC.A standup at 9:00 a.m. on Tuesday, 13 January 2026 in Denver. Mountain is on MST that morning, so the offset is UTC−7. Add seven hours: 16:00 UTC. Stored that way, it is a single unambiguous instant regardless of who opens the calendar. Check it against the UTC to MST conversion.

Example 2 — MDT to CEST.A demo at 10:00 a.m. on Wednesday, 8 July 2026 in Salt Lake City. Mountain is on MDT, UTC−6. Berlin is on CEST, UTC+2. Total shift: eight hours forward, so the demo lands at 18:00 in Berlin. Run the same meeting in January and Salt Lake City is on MST (UTC−7) while Berlin is on CET (UTC+1) — still eight hours, because both ends moved together. That coincidence is why European–Mountain scheduling feels stable and why the two weeks in March when it is not stable catch people out.

Example 3 — the Phoenix drift.A weekly 8:00 a.m. Denver call with a Phoenix supplier, set up in December. From December to early March, both sides see 8:00 a.m.: Denver is on MST and Phoenix is on MST. On 8 March, Denver springs forward and Phoenix does not, so the supplier now joins at 7:00 a.m. their time. Nobody changed the invite. The fix is to agree on the Phoenix hour and let Denver's calendar float, or to pin the series to a America/Phoenix host calendar.

Example 4 — the spring-forward gap. A nightly batch job scheduled for 2:30 a.m. local time in Denver will never run on the second Sunday of March, because 2:00 a.m. skips straight to 3:00 a.m. and 2:30 does not exist that day. On the first Sunday of November the reverse happens: 1:30 a.m. occurs twice, and a wall-clock trigger may fire twice. The same job pointed at America/Phoenix runs cleanly every night of the year, because Phoenix has no transitions at all. Schedule in UTC where you can.

How software handles this

A calendar app, a database, or a scheduling service should never store "MST" or "MDT" as a time zone. Both are surface labels whose meaning depends on the date of the event, and in Arizona the label MST does not even imply the same rules it implies in Colorado. Store the IANA identifier and let the runtime compute the offset:

• America/Denver — Colorado, Wyoming, most of Montana and New Mexico, and the Navajo Nation. Observes DST. The tz database also ships America/Shiprock and Navajo as links to this zone precisely so that Navajo Nation records can be tagged distinctly while resolving to the same rules.
• America/Phoenix — Arizona outside the Navajo Nation, including the Hopi Reservation. No DST, ever, since March 1968. Creston and Dawson Creek in British Columbia link to it as well.
• America/Boise — southern Idaho, which observes MST/MDT on the U.S. schedule but has a different historical record from Denver.
• America/Edmonton— Alberta, now on a fixed UTC−6.
• America/Hermosillo — Sonora, Mexico, MST year-round.
• America/Ciudad_Juarez — the Chihuahua border municipios, which follow the U.S. MST/MDT schedule while the rest of Chihuahua (America/Chihuahua) moved to a fixed UTC−6 in 2022.

The fact that Arizona needs its own identifier rather than an offset flag is the clearest argument for zone names over offsets in general.UTC−7 tells you what Phoenix and Denver have in common in January and nothing about what they will do in March. Zone identifiers pick up future legislation automatically when tzdata is updated — release 2026c already carries the Alberta and British Columbia changes described above — and they preserve the meaning of historical timestamps across every past rule change.

Common mistakes

• Writing MST for a summer date. Between March and November the correct abbreviation is MDT. The wall-clock hour is the same either way, but the UTC offset differs by an hour, and any system that parses the abbreviation literally will resolve the event to the wrong instant.
• Assuming Arizona is on Pacific time. It is on Mountain time and simply does not change. It looks like Pacific for eight months a year, which is why the assumption survives until November.
• Assuming all of Arizona is on the same clock. From March to November the Navajo Nation is an hour ahead of the rest of the state, and the Hopi Reservation inside it is back on the state clock. Name the community.
• Treating MDT and CST as different zones in summer. They share UTC−6, so 10:00 MDT in Denver is 10:00 CST in Regina, even though the abbreviations differ. See the MST to CST conversion for the winter case, where they differ by an hour.
• Hard-coding UTC−7 for "Mountain." It is wrong for eight months of every year in Denver and right all year in Phoenix. Use America/Denver or America/Phoenix and let the library decide.
• Assuming Calgary still tracks Denver. That was true until 1 November 2026 and is not true after it. Recurring Denver–Calgary meetings created before that date will shift by an hour each winter unless the invite is anchored to a zone identifier.
• Scheduling anything at 2:30 a.m. local time. See the spring-forward gap. Either schedule in UTC or pick an hour the transition does not touch.

Bottom line

Mountain Time has two abbreviations because the Uniform Time Act of 1966, as amended by the Energy Policy Act of 2005, splits the year into a four-month standard window (MST, UTC−7) and an eight-month daylight window (MDT, UTC−6), with the switches on the second Sunday in March and the first Sunday in November at 2:00 a.m. local. MT is the way to avoid picking. What makes this zone harder than its neighbors is that the rule has holes in it: Arizona rejected daylight saving by statute in 1968, the Navajo Nation observes it anyway, and the Hopi Reservation inside the Navajo Nation does not — a three-layer exception you can drive through in an afternoon. Alberta left the cycle for a fixed UTC−6 in 2026 and British Columbia settled on a fixed UTC−7, so the zone's northern boundary now means something different than it did last year. For scheduling, name the city. For software, store America/Denver or America/Phoenix, keep tzdata current, and never let an offset stand in for a zone.