PST to EST: Dates, Daylight Saving and Meeting Times

Choose fixed standard time or date-aware local time

A conversion starts with the meaning of the supplied time. PST means Pacific Standard Time, with a fixed offset of UTC−08:00. EST means Eastern Standard Time, with a fixed offset of UTC−05:00. Eastern Standard Time is therefore three hours ahead of Pacific Standard Time. These literal offsets stay fixed even when the date falls in summer.

A meeting described as Pacific time usually means the local clock in a Pacific location. Los Angeles uses daylight time during part of the year. New York does the same for Eastern time. The PST to EST converter offers both interpretations. Choose fixed mode for an explicitly supplied standard offset. Choose date-aware mode for a Los Angeles or New York event.

The location matters. This tool uses America/Los_Angeles and America/New_York as its local-zone definitions. It does not treat every place with a similar abbreviation as having identical rules. For a destination elsewhere, use the UTC to time-zone converter and select its actual IANA location.

Understand the four familiar abbreviations

When both locations observe standard time, their difference is three hours. When both observe daylight time, it is also three hours. Combining a fixed standard abbreviation with a daylight abbreviation changes that arithmetic. For example, 9:00 AM literal PST is 1:00 PM EDT, while 9:00 AM PDT is noon EDT.

A date-aware result includes the abbreviations and the numeric offsets actually applied. Keep those fields with a copied result. They explain why a particular answer differs from a remembered three-hour shortcut. The world clock is useful for the current instant; it does not replace a conversion for a future appointment.

Work through forward and reverse examples

In fixed mode, January 10, 2027 at 11:00 PM PST becomes January 11 at 2:00 AM EST. Adding three hours passes midnight, so the destination date advances. The same instant is January 11 at 07:00 UTC. A result containing only 2:00 AM would omit the part most likely to cause a scheduling mistake.

In the reverse direction, January 11, 2027 at 1:00 AM EST becomes January 10 at 10:00 PM PST. Subtracting three hours moves to the previous date. Enter this example in the EST to PST converter and compare the destination date with the source date.

For a summer meeting, July 10, 2027 at 9:00 AM in Los Angeles becomes noon in New York under the currently available local rules. The local labels are PDT and EDT. The exact instant is 16:00 UTC. Changing that same input to fixed PST/EST mode instead produces 17:00 UTC. The wall-clock difference still looks like three hours, but the selected instant differs by an hour.

Check the hours around a daylight-saving transition

Under current US rules, participating locations advance their clocks on the second Sunday in March and turn them back on the first Sunday in November. Each change occurs at 2:00 AM local time. These are local transitions, so New York and Los Angeles do not change at the same UTC instant.

The converter resolves one actual instant before formatting the other location. This matters in the short period between the two transitions. On March 14, 2027, 12:30 AM in Los Angeles corresponds to 4:30 AM in New York. The difference is temporarily four hours. On November 7, 2027, 12:30 AM in Los Angeles corresponds to 2:30 AM in New York. The difference is temporarily two hours.

The hourly chart is calculated for the source date you select. It is not a permanent copied table that assumes every hour has the same difference. Change the date, direction or convention and the chart recalculates alongside the main answer. Its destination-date column also shows which rows cross midnight.

Resolve skipped and repeated source times

A clock advance leaves a gap in local wall times. For example, March 14, 2027 at 2:30 AM in Los Angeles does not occur under the current rules. Date-aware mode rejects that input. Choose a valid event time rather than allowing an invisible correction to a different hour.

A clock rollback creates two occurrences of some wall times. November 7, 2027 at 1:30 AM in Los Angeles can identify two instants. The earlier occurrence is 08:30 UTC and becomes 3:30 AM EST in New York. The later occurrence is 09:30 UTC and becomes 4:30 AM EST. Choosing earlier or later therefore changes the answer.

The default repeated-time rule asks for a choice. Select an occurrence only when it matches the actual event. If the original invitation contains a UTC instant or a numeric offset, use that information to identify it. Fixed standard-offset mode has neither a skipped hour nor a repeated hour because its offset never changes.

Share a meeting with its date and zone

1. Enter the calendar date as it is written in the source location.
2. Enter the source clock time, checking AM and PM.
3. Choose local date-aware time or explicit fixed standard offsets.
4. Resolve an occurrence if the source hour repeats.
5. Read the destination date, time, abbreviation and UTC offset.
6. Copy the result with the exact UTC instant for a useful cross-check.

The swap button reverses the conversion while preserving the converted instant when the current input is valid. Use it to check that the destination can be converted back to the original date and time. The 12-hour and 24-hour display choices change presentation rather than the instant.

For an event duration, use the time between times calculator with its stated browser-local convention. A clock conversion alone does not measure a meeting length or create a calendar invitation. Read the time-zone meeting guide for a wider scheduling workflow.

Use future years without replacing a static table

The converter accepts a source date and calculates its result from that date. It has no 2027 end date. The site’s current date, calendar headings and yearly pages also follow the date when the page is requested. Leap years and calendar arithmetic are calculated rather than copied from an old year.

Local-zone offsets come from the time-zone data available to the visitor’s browser. IANA publishes revisions when governments change boundaries, offsets or daylight-saving rules. Browser and operating-system updates are therefore part of maintaining accurate local conversions. A result for a distant year reflects the available rules, which can later change.

Fixed PST/EST mode keeps its explicit offsets regardless of those policy changes. Editorial guides still need a factual review when a rule changes. Their worked examples remain labeled examples; the site does not give them a false new review date whenever January arrives. Keep browser software current and confirm a distant appointment again as its date approaches.

Read the conversion receipt before using the answer

The result separates the source time and date from the destination time and date. It lists both UTC offsets, the day change and the exact UTC instant. These fields make the calculation reproducible. If two people get different results, compare the mode, date and offsets before comparing only the clock time.

The live Pacific and Eastern clocks show the current instant from the device. They continue ticking even while a historical or future date is selected in the converter. The chart belongs to the selected date; the live clocks belong to now. This distinction lets you check the present time without losing the appointment you are converting.

Try a normal daytime conversion, a late-night conversion and a transition-date example before sharing a complex schedule. For calendar-only intervals, move to the days between dates calculator. It counts Gregorian dates rather than treating a clock change as an extra or missing calendar day.

Frequently asked questions