Las Vegas Runs on Pacific Time, And It Actually Matters
What Time Zone Is Us Las Vegas Pacific Time Rules The Silver State
Las Vegas is in the Pacific Time Zone. That's the short answer. Nevada as a whole operates under PT, which means UTC-8 during standard time and UTC-7 when Daylight Saving Time kicks in. The state officially adopted this after the federal government standardized time zones back in 1918 with the Standard Time Act. Before that, every railroad and town kept its own local solar time, which was a mess for scheduling. I've dealt with this on the logistics side more than once. The problem isn't knowing that Las Vegas is Pacific time. The problem is when the rest of the country doesn't follow the same rules or when you're coordinating across multiple zones and someone ignores DST transitions. I had a freight dispatch running cargo from Vegas to Phoenix last spring where the trucking company scheduled departures based on Mountain Time without accounting for Arizona not observing DST. We lost nearly three hours on a tight delivery window because the driver's base operations center sent out manifests at the wrong offset. We ended up rebooking through a local Las Vegas yard that understood the correct timezone math, which added cost but saved the shipment. Here's what most people miss: Nevada technically spans two time zones. The majority of the state, including Clark County where Las Vegas sits, follows Pacific Time. But places like West Wendover on the Utah border are actually on Mountain Time. If you're doing anything that involves cross-state coordination — logistics, legal deadlines, broadcasting, or even just setting up conference calls with clients in different parts of Nevada — assuming the whole state is on one clock will trip you up. West Wendover is a real edge case. It's about four hours from Las Vegas geographically, but it's an hour ahead time-zone-wise.
The practical setup for handling Las Vegas time correctly involves understanding the federal rules that govern it. The Uniform Time Act of 1966 is what sets the current DST framework. States can opt out, and Arizona did, but Nevada didn't. So Nevada observes DST the same way California and Oregon do. Clocks spring forward on the second Sunday in March and fall back on the first Sunday in November. That's been consistent since 1987, when Congress standardized those dates to reduce the confusion that existed under the previous patchwork of local DST rules. If you need to work with this programmatically or manage schedules across zones, the IANA timezone database entry for Las Vegas is America/Los_Angeles. That's the identifier you use in most timezone-aware systems. Not America/Vegas. Not Nevada. America/Los_Angeles. It covers the entire Pacific zone including Las Vegas, and it handles DST transitions automatically if your software respects the database rather than hardcoding offsets. I learned that the hard way when a client had their scheduling tool hardcoded to UTC-8 year-round and everything broke during DST switches for about six weeks every year. One counter-intuitive thing about Pacific Time in Nevada that comes up rarely but matters when it does: some federal facilities and military operations in the area technically operate on a different baseline depending on their mission requirements. The Nellis Air Force Base area adjacent to Las Vegas has had occasions where operational scheduling uses a stabilized reference that doesn't flip with civilian DST. This doesn't affect the general public, but if you're contracting for defense work or scheduling around military exercises near the base, that's something to verify directly rather than assume civilian time applies.
For most people dealing with Las Vegas time, the main pitfalls are assuming all of Nevada is Pacific time, forgetting about DST transitions when booking or scheduling, and using the wrong IANA identifier in any software or API work. Watch the DST dates each year and confirm with your counterparts if they're based outside the Pacific zone. That usually prevents the vast majority of issues.
Get the Full Details
