---
title: "PST vs PDT: what's the difference?"
url: https://meet.barq.dev/glossary/pst-vs-pdt
updated: 2026-11-17
author: "Hammad Ali"
---

# PST vs PDT: what's the difference?

> **Short answer:** PST, Pacific Standard Time, is UTC-08:00; PDT, Pacific Daylight Time, is UTC-07:00. They differ by one hour. For Los Angeles, 14:00 on 15 January 2026 is 22:00 UTC, while 14:00 on 15 July is 21:00 UTC. Use the location and date when you mean its local clock.


## What does PST vs PDT mean for a Los Angeles appointment?

PST and PDT apply different offsets to the same written clock hour. In the dated Los Angeles examples, January uses minus eight hours and July uses minus seven, so calling both appointments "14:00 PST" would describe the wrong instant for the July local-hour intention.


The letter matters here.


| Detail | PST | PDT |
| --- | --- | --- |
| Expanded name | Pacific Standard Time | Pacific Daylight Time |
| UTC offset | UTC-08:00 | UTC-07:00 |
| Los Angeles example | 15 January 2026 | 15 July 2026 |
| 14:00 local in UTC | 22:00 | 21:00 |

Method: computed with Luxon and America/Los_Angeles for the stated dates. [IANA's time zone data](https://www.iana.org/time-zones) and [release notes](https://data.iana.org/time-zones/tzdb/NEWS) cover the location's rule framework, as of 17 November 2026.


Our [EST and EDT comparison](https://meet.barq.dev/glossary/est-vs-edt) explains the corresponding naming distinction for the New York examples. Don't transfer one city's rules to every place using a similar abbreviation.


## How much can a PST label change a July invitation?

A literal PST instruction is one hour later than the same clock hour in Los Angeles during the July example. If you intend 10:00 Los Angeles time on 15 July 2026, the appointment is at 17:00 UTC; 10:00 at fixed UTC-08:00 is 18:00 UTC.


That's an hour late. The guest applying the written minus-eight offset has followed the instruction you gave, even though you meant the city's minus-seven summer clock.


These conversions use Luxon with America/Los_Angeles and the explicit fixed offset. Write "15 July 2026, 10:00 Los Angeles time" if the city's clock is the agreement.


The [abbreviation reference for meeting times](https://meet.barq.dev/glossary/time-zone-abbreviations) explains why naming the location is clearer than assuming every reader interprets "Pacific" as the same rule set.


## When does Los Angeles change between PST and PDT?

The checked US transition table places the 2026 spring change on 8 March and the autumn change on 1 November. The 2027 dates are 14 March and 7 November; use those dates with the location's rules, instead of assuming a permanent calendar day each year.


Check the year as well. Sources: timeanddate's [2026 spring](https://www.timeanddate.com/time/dst/2026a.html), [2026 autumn](https://www.timeanddate.com/time/dst/2026b.html), [2027 spring](https://www.timeanddate.com/time/dst/2027a.html) and [2027 autumn](https://www.timeanddate.com/time/dst/2027b.html) tables, as of 17 November 2026.


The [glossary's time-related definitions](https://meet.barq.dev/glossary/scheduling-glossary) cover named zones and offsets. Future government decisions can change the rules, so keep a dated source attached to future transition claims.


## What should a Los Angeles host set in Barq Meet?

A Los Angeles host whose appointments should follow the city's local clock should use America/Los_Angeles for the availability schedule. We interpret working hours in that named zone, while the guest chooses how to display those appointment starts locally.


We keep calendar conflict checks tied to the submitted appointment. We send booking confirmations with calendar invitations, giving both participants a way to inspect the chosen instant after selecting a time. Check [AEST versus AEDT](https://meet.barq.dev/glossary/aest-vs-aedt) before converting a Sydney appointment as though every Australian participant follows the same seasonal clock.


Test dates in both seasons. If the result is wrong, check the schedule's zone before rewriting the email label; a suffix change alone doesn't move an existing booking.


Recurring series need another process because Barq Meet books individual appointments. Review [the included availability controls](https://meet.barq.dev/pricing), then [make a booking page that follows Los Angeles time](https://meet.barq.dev/app/sign-in) for guests in other zones.

## Frequently asked questions

### Is Pacific time a fixed eight-hour subtraction?

No. For the Los Angeles dates shown, January uses UTC-08:00 and July uses UTC-07:00. Use the named zone and meeting date when converting, instead of applying the winter difference to every appointment. Use America/Los_Angeles and the actual date for a city-based appointment, instead of applying the winter subtraction to a summer conversation.

### Can I use PST in the title of every event?

Avoid a permanent PST suffix if the offer follows Los Angeles local time across seasons. Name the city in the description and let the dated calendar invitation identify the appointment, so a summer booking isn't labeled with the winter offset.

### Does PDT tell me whether a guest can attend?

No. PDT identifies an offset label, not a person's working hours or calendar conflicts. Convert the dated appointment, then ask for availability or offer a booking choice that passes the host's scheduling rules. Ask the guest about their working hours independently of the conversion, because sharing a valid offset doesn't establish whether the proposed time is convenient.

## Related pages

- [EST vs EDT: what's the difference?](https://meet.barq.dev/glossary/est-vs-edt)
- [Time zone abbreviations list for scheduling](https://meet.barq.dev/glossary/time-zone-abbreviations)
- [Scheduling glossary: booking and calendar terms explained](https://meet.barq.dev/glossary/scheduling-glossary)
- [AEST vs AEDT: what's the difference?](https://meet.barq.dev/glossary/aest-vs-aedt)

[Create your free booking link](https://meet.barq.dev/app/sign-in)
