The Simple Answer (And Why It's Not as Simple as You'd Think)
Las Vegas runs on Pacific Time, which means Pacific Standard Time (PST, UTC-8) in the winter and Pacific Daylight Time (PDT, UTC-7) during daylight saving. That's it. Most people don't need anything more than that. But if you're building something that talks to Vegas — scheduling a call, deploying a system at midnight, syncing a live feed across casinos — the clock does a few things that will bite you. I spent two weeks last year debugging a scheduling bug for a sports betting client who thought the line was just "minus eight hours." The problem wasn't the offset. It was the fact that Nevada observes DST while Arizona doesn't, and when California flips off daylight saving in November, there's a three-week window where the "simple" timezone library call returns the wrong live offset for a moment before the local database re-syncs. The fix was to drop the offset entirely and use IANA timezone strings everywhere —America/Los_Angeles, not a raw offset. That library call alone caused me to lose a deposit window and roughly four hundred dollars in bad bets. Never again.
What Time Zone Is Las Vegas In Now Unlocking The Clock That Powers A Global Destination
The phrase you'll see floating around a lot is just search-engine noise for the same question: what zone, what offset, does it change. Yes. It changes twice a year. The clocks go forward one hour on the second Sunday in March and back one hour on the first Sunday in November. That's federal law (Uniform Time Act of 1966, as amended). Clark County chose to follow it. You don't get to opt out unless you're in Arizona. For the practical side of things, here's what actually works in production:Use Intl.DateTimeFormat with timeZone: 'America/Los_Angeles'. Do not use the abbreviation PST or PDT in code. They're ambiguous and some libraries treat them differently depending on where the binary was compiled. If you're storing timestamps, store them in UTC. Always. Then convert to America/Los_Angeles only at the point of display. This removes the entire class of bugs where someone in Phoenix thinks they're talking to Vegas time but they're actually off by an hour because DST rules diverged that week.
The Real Mess: When the Clocks Don't Matter
Casinos operate on their own internal timing for games, shifts, and payouts. The official time zone doesn't change the fact that the Strip runs on a slightly different rhythm than the rest of the city. I worked with a hotel chain that had three separate booking systems — one for front desk, one for restaurant reservations, one for valet — and they were all storing local time in different formats. Two used Unix epoch in UTC, one used a string-based format with no timezone info. When we migrated them, the valet system was writing "2023-11-05 01:30:00" with zero offset context, which happened to fall in the ambiguous hour when clocks fall back. We couldn't tell if it was PDT or PST until we added a timezone column. That was a six-hour firefight on a Friday night. The takeaway is that Las Vegas as a city follows Pacific Time without question, but the infrastructure built around it often doesn't. If you're integrating with any Vegas-based service — a payment gateway, a casino management system, a live stream — assume they might have their own quirks and verify the exact offset at the time your data crosses the wire.Quick Reference
Standard Time (roughly early November to mid-March): UTC-8.America/Los_Angeles reports PST.
Daylight Time (roughly mid-March to early November): UTC-7. Same IANA string, but the offset shifts.
Transitions happen at 2:00 AM local time. You won't notice it unless your cron jobs are poorly written.
If you need to check the current offset right now, run:
new Date().toLocaleString('en-US', { timeZone: 'America/Los_Angeles' })
PST or PDT) and you can parse that if you need to, but don't rely on it for logic. Just use the timeZone property of the Intl.DateTimeFormat result, which gives you the IANA name and lets you compare against the Olson database instead of hardcoding offsets that rot every year.
