California Runs on Pacific Time and That Is Less Simple Than You Think
California is in the Pacific Time Zone. In the IANA timezone database, the identifier is America/Los_Angeles. The abbreviation is PT, which covers both PST (Pacific Standard Time, UTC-8) and PDT (Pacific Daylight Time, UTC-7). When people talk about California time, they are usually referring to the broader Pacific Time design, not just the winter offset. The legal definition comes from the Uniform Time Act of 1966 and subsequent amendments. California observes daylight saving time. The current rule, established by the Energy Policy Act of 2005, starts at 2:00 AM local time on the second Sunday in March and ends at 2:00 AM local time on the first Sunday in November. Before 2007, the transition dates were different: first Sunday in April through last Sunday in October. This matters when you are processing historical data or building anything that needs to handle dates across that 2007 boundary. On the technical side, the IANA database handles all of this. The tzdata package for your operating system contains the rule changes going back decades. If you are running a Linux server and your tzdata is stale, your timestamps will be wrong for transitions that happened after your last system update. I learned this the hard way when a payroll system I supported was processing biweekly runs and kept getting a 23-hour day during the spring transition because the container image had an outdated tzdata package from 2019. The fix was straightforward but easy to miss: mount the host's /usr/share/zoneinfo into the container and set TZ=America/Los_Angeles explicitly instead of relying on the default system timezone baked into the image.
In code, you should never store or transmit California time as a simple UTC offset like -8 or -7. Store everything as UTC. When you need to display it in Pacific time, convert at the presentation layer using the proper timezone identifier. This avoids the classic bug where someone stores a datetime in UTC but formats it without specifying the timezone, and the display defaults to the server's local time, which might be EST or something else entirely. One counter-intuitive thing about Pacific Time is how it interacts with international scheduling. California is not simply three hours behind New York during standard time and three hours during daylight time in a way that stays clean. The reason is that the DST transition dates, while currently aligned between Eastern and Pacific, are not guaranteed to stay aligned. States can opt out of DST, and there have been legislative attempts in California itself to stay on permanent PDT. If that happens, the offset relationship with Eastern Time shifts permanently. Any system that hardcodes assumptions about the ET-PT offset being exactly three hours is taking a risk. Another nuance people miss: Pacific Time does not apply to the entire state in the same way for all purposes. Some remote eastern areas of California technically fall within the Mountain Time Zone geographically, but no populated area in California observes MT. The state is uniformly PT. However, if you are working with census data, survey response times, or anything that uses timezone for geographic inference, assuming "California equals PT" will work for nearly all practical purposes but could introduce errors in edge datasets.
For developers, here is what I actually use. In Python, I use the zoneinfo module from the standard library, which pulls from the system's tzdata. In Node.js, I use the IANA timezone name directly with date-fns-tz or Luxon rather than relying on moment-timezone, which has had maintenance concerns. In JavaScript environments where you control the runtime, explicitly setting the timezone via process.env.TZ=America/Los_Angeles at process startup is the single most effective way to avoid silent timezone drift in server-side code. If you need to download updated timezone data, the source is the IANA tzdata project at ical.org/timezone-data. For Debian and Ubuntu systems, running sudo apt-get install --reinstall tzdata and then dpkg-reconfigure tzdata is the standard path. On macOS, timezone data ships with the OS and updates through normal software updates. Windows uses its own registry-based timezone database, which diverges from IANA occasionally, so cross-platform consistency requires explicit handling. The main failure mode I see repeatedly is treating timezone as a static offset. It is not. It is a set of rules that change over time, and those rule changes are not uniform globally. California's rules have changed multiple times in the last 60 years. If your system only handles the current rule set, it will produce incorrect results for any historical data before the rule changed. I have seen data pipelines that worked fine for current operations but silently corrupted backfills going beyond a few years into the past because nobody checked whether the tzdata version matched the date range of the data being processed.
Get the Full Details
For end users just trying to figure out what time it is in California right now, the practical answer is to check if it is currently between the second Sunday in March and the first Sunday in November. If yes, it is PDT, which is UTC-7. If no, it is PST, which is UTC-8. There is no exception to this within California proper. The state does not span multiple time zones like some western states do.
