Pacific Time looks simple until you have to convert it. A webinar from California, a meeting with a team in Seattle, a product launch from Los Angeles, or a deadline written as “9 AM PST” can mean different things depending on the date.
The reason is that Pacific Time is not always the same UTC offset. During standard time, it uses PST, which is UTC-8. During daylight saving time, it uses PDT, which is UTC-7. Pacific Time, or PT, is the general label for the region.
That one-hour shift is not just a technical detail. It affects calendar invites, remote meetings, livestreams, flight planning, stock market timing, server logs, and any situation where Pacific Time has to be compared with another time zone.
The Short Answer
Pacific Time is the time zone used on the west coast of the United States and in parts of Canada and Mexico. PST and PDT are the two seasonal forms of that time zone.
| Term | Meaning | UTC offset | When to use it |
|---|---|---|---|
| PT | Pacific Time | UTC-8 or UTC-7 | General schedules, events, business hours |
| PST | Pacific Standard Time | UTC-8 | When Pacific Time is on standard time |
| PDT | Pacific Daylight Time | UTC-7 | When daylight saving time is active |
For most public communication, PT is the safest label. It tells the reader “Pacific local time” without forcing the wrong seasonal abbreviation. PST and PDT are useful when the exact UTC offset matters.
Why PST and PDT Are Not Interchangeable
PST means Pacific Standard Time. It is used during the standard-time part of the year, mostly in late fall and winter. Its offset is UTC-8. So when it is 12:00 UTC, it is 4:00 AM PST.
PDT means Pacific Daylight Time. It is used during daylight saving time, mostly from spring to early fall. Its offset is UTC-7. So when it is 12:00 UTC, it is 5:00 AM PDT.
The city does not change. Los Angeles, San Francisco, Seattle, Portland, Vancouver, and Tijuana all remain in the Pacific Time region. What changes is the legal clock rule for the date.
PDT = UTC – 7
This is why writing “PST” all year is risky. If someone in California schedules an event for July and writes “10 AM PST,” they probably mean 10 AM local Pacific Time. But in July, the local abbreviation is usually PDT. A person converting from PST literally may be off by one hour.
To check the live standard-time reference, use the current PST time page. To check the daylight-time reference, use the current PDT time page.
What Actually Changes During the Year
The important change is the offset from UTC. UTC is the global reference used for time conversion, computer systems, aviation, finance, and international scheduling. Local time zones apply regional rules on top of that reference.
Pacific Time is UTC-8 during standard time. When daylight saving time begins, clocks move forward by one hour, so Pacific Time becomes UTC-7. That is why the same local time can map to a different UTC time depending on the date.
| Example | Active Pacific Time | UTC offset | 12:00 UTC equals |
|---|---|---|---|
| Los Angeles in winter | PST | UTC-8 | 4:00 AM |
| Los Angeles in summer | PDT | UTC-7 | 5:00 AM |
The one-hour change becomes visible when Pacific Time is compared with another region. A 10:00 AM meeting in Los Angeles may convert differently for someone in London, Berlin, Tokyo, or Sydney because those places may follow different daylight saving rules, or none at all.
For the wider logic behind offsets and global time comparison, read what UTC is and why it matters. For the seasonal clock change itself, see why daylight saving time exists.
Pacific Time vs Eastern Time
Pacific Time is usually three hours behind Eastern Time. If it is 9:00 AM in Los Angeles, it is usually 12:00 PM in New York.
The word “usually” matters. PT to ET is normally a three-hour difference because both regions generally follow the same daylight saving schedule in the United States. But if people mix the abbreviations, the difference can change.
| Comparison | Difference | Why it matters |
|---|---|---|
| PT to ET | Usually +3 hours | Best for general West Coast to East Coast scheduling |
| PST to EST | +3 hours | Both are standard-time offsets |
| PDT to EDT | +3 hours | Both are daylight-time offsets |
| PST to EDT | +4 hours | One side is standard time, the other is daylight time |
This is the practical reason PT and ET are often better than PST and EST on public schedules. They describe the local time zones without forcing the reader into a seasonal offset. For the same issue on the East Coast, read EST, EDT, and Eastern Time.
When PT Is the Better Choice
Use PT when your reader needs the local Pacific time, not the technical offset. This is the right choice for most event pages, webinars, support hours, product launches, livestreams, class schedules, and recurring meetings.
- “The event starts at 10:00 AM PT.”
- “Support is available from 8:00 AM to 5:00 PM Pacific Time.”
- “The livestream begins at 6:00 PM PT.”
These examples are clear because the date decides whether the local time is PST or PDT. The reader does not have to know which abbreviation is active.
Use PST or PDT when the exact offset matters. That is more common in technical documentation, logs, APIs, market data, international operations, and manual UTC conversion.
Where Pacific Time Causes Real Mistakes
The most common mistake is using PST as a casual synonym for Pacific Time. It may feel harmless, but it can create real confusion when the audience is outside the Pacific region.
For example, “10 AM Pacific Time in Los Angeles” and “10 AM PST” are not always the same thing. The first follows the city’s time rules. The second fixes the time at UTC-8. If the event happens during daylight saving time, those two labels point to different UTC times.
The second mistake is assuming all countries change clocks together. The United States, the United Kingdom, and European countries do not always start or end daylight saving time on the same weekend. During transition periods, familiar time differences can temporarily shift.
The third mistake appears in software. A future event tied to Los Angeles should not be stored simply as PST. If the date falls during daylight saving time, the event needs to follow the local rule. That requires a location-based time zone, not only an abbreviation.
Why America/Los_Angeles Matters More Than PST
Abbreviations are useful for people, but they are weak for software. PST and PDT describe offsets. They do not describe the full rule set for a location.
An IANA time zone such as America/Los_Angeles stores the location rule. It tells a calendar or database when standard time applies, when daylight saving time applies, and how past or future legal changes should be handled.
This is why calendar systems, operating systems, databases, and programming languages rely on IANA identifiers instead of simple abbreviations. For a deeper explanation, see why an IANA time zone name matters more than the UTC offset alone.
The Practical Rule
Use PT for public schedules and general communication. It is clear, familiar, and avoids most seasonal mistakes.
Use PST only when Pacific Time is on standard time and the correct offset is UTC-8. Use PDT only when daylight saving time is active and the correct offset is UTC-7.
For technical systems, store timestamps in UTC and use a location-based IANA time zone for future events tied to a real place. That keeps the local time correct even when daylight saving rules apply.
Sources and references
