Why Las Vegas Time Zone Confusion Is So Common
Las Vegas is in the Pacific Time Zone, same as Los Angeles and Seattle. Standard time is UTC-8, daylight saving time is UTC-7. That part is straightforward. The confusion comes from everything else surrounding it. Nevada sits right on the edge of the Mountain Time Zone, and there are small pockets in the state that actually observe MT instead of PT. Places like West Wendover, close to the Utah border, run on Mountain Time. A business owner setting up a vendor meeting between Wendover and Las Vegas can easily book both sides at the same local clock time and end up a full hour apart in reality. This is a real problem I ran into when coordinating a construction schedule between a supplier outside Elko and the main crew in Vegas. Took me three weekends to untangle it. The state does observe daylight saving time, which means the offset shifts twice a year. Nevada moved to DST on the second Sunday in March and backs off on the first Sunday in November. Most of the country follows this pattern now, but not all of it. Arizona, for instance, stays on Mountain Standard Time year-round except for the Navajo Nation. If you're booking a call with a Phoenix contractor at 9 AM Pacific during summer, that's 11 AM in Phoenix, not 10. I've seen that mistake cost a project manager a full morning of delays.
Another thing people miss: Vegas stays on Pacific time even though it's geographically closer to the center of Mountain Time than the standard Pacific boundary would suggest. The time zone line runs through eastern Nevada, well east of the state capital, Carson City. So the entire populated portion of Nevada, including Reno and Las Vegas, falls in the Pacific division. There's no split within the city limits itself. Here's the practical side that most guides skip. When scheduling across zones, always confirm whether the other party is observing DST at that moment. The two-week windows around the spring and fall transitions are where things break. In late March, for example, Las Vegas has already shifted to PDT while somewhere like Chicago might still be on CST for a few more days depending on their local rules. The offset between Vegas and Chicago is usually two hours during standard time and one hour during daylight time, but during those transition weeks it can be neither. For travelers, the main thing to keep in mind is that flight schedules are listed in local departure and arrival times, not UTC. If you're flying from New York to Las Vegas on a Monday morning at 7 AM Eastern, you land around 9:30 AM Pacific. The three-hour difference sounds simple until you've been up since 4 AM and your internal clock decides it's still Eastern time. I always set my phone to the destination time zone the night before a trip and leave it there. It's a small fix that prevents about half the scheduling mistakes I see people make.
Businesses running multi-location teams should just keep everything in UTC internally and convert at the point of communication. It sounds like extra work, but it eliminates the DST overlap problem entirely. You stop asking "are we on standard or daylight right now?" and just read one number. I switched my team's scheduling system to this approach and cut the conflict rate down to nearly zero over a twelve-month period. If you need to look up the current offset quickly, the IANA time zone identifier for Las Vegas is America/Los_Angeles. It's the same database that most calendar applications use under the hood. You won't find an entry labeled "America/Las_Vegas" because the tz database doesn't maintain separate entries for cities within the same zone. That's normal and it doesn't mean anything is wrong with your system.
Get the Full Details
