PST to EST Converter


Interpreted in the "From" timezone

Time in America/New_York
UTC equivalent

Offsets
America/Los_Angeles UTC-07:00 → America/New_York UTC-04:00
Difference
3h ahead of the source zone
Calendar date
Same calendar date

Converting Pacific time to Eastern comes up constantly for anyone based on the US West Coast trying to fit into an East Coast-centric schedule — a 9 AM Pacific start feels early only until you realize it’s already noon on the East Coast, and a lot of West Coast professionals learn to think in both zones simultaneously specifically to avoid proposing meeting times that quietly don’t work for the other side. This is the mirror image of the Eastern-to-Pacific conversion, but the practical question is usually different: not “what does my time become for them,” but “how early do I need to start my day to catch them at all.”

The constraint worth internalizing, and it’s a subtler one than “West Coast people just lose 3 hours”: a standard 9-to-5 Pacific workday and a standard 9-to-5 Eastern workday actually overlap for a comfortable 5 hours — 9 AM to 2 PM Pacific lines up with noon to 5 PM Eastern — since the 3-hour figure most people remember is the zone gap, not the overlap, and the two aren’t the same number. What that 5-hour overlap misses specifically is the very start of the East Coast’s day: 9 AM to noon Eastern is only 6 AM to 9 AM Pacific, well before a standard Pacific workday begins. West Coast teams that specifically want to catch East Coast colleagues first thing, not just during the shared afternoon, deliberately start earlier than a standard 9-to-5 for exactly that reason — there’s no symmetric equivalent available going the other way, since the East Coast can’t shift later to meet the West Coast without cutting into their own evening.

Working through the concrete numbers: 9:00 AM Pacific on July 30, 2026 converts to 12:00 PM (noon) Eastern — already deep into a standard East Coast morning, which is exactly the “later than you’d expect” effect that catches people planning from the Pacific side. The 3-hour gap itself doesn’t shift with the seasons (both zones observe US daylight saving on the same calendar dates, so they move together), which at least makes the mental math consistent year-round even if it’s easy to misjudge on any single day.

Converting Pacific time to Eastern time programmatically

JavaScript, via the same round-trip technique needed any time the starting point is a wall-clock time in a specific zone rather than an already-known UTC instant:

function zonedTimeToUtc(year, month, day, hour, minute, timeZone) {
  const naiveUtc = Date.UTC(year, month - 1, day, hour, minute);
  const parts = new Intl.DateTimeFormat("en-US", {
    timeZone, year: "numeric", month: "2-digit", day: "2-digit",
    hour: "2-digit", minute: "2-digit", hour12: false,
  }).formatToParts(new Date(naiveUtc));
  const get = (t) => Number(parts.find((p) => p.type === t)?.value ?? 0);
  const readBack = Date.UTC(get("year"), get("month") - 1, get("day"), get("hour") % 24, get("minute"));
  return new Date(naiveUtc - (readBack - naiveUtc));
}

const utcInstant = zonedTimeToUtc(2026, 7, 30, 9, 0, "America/Los_Angeles");
console.log(new Intl.DateTimeFormat("en-US", {
  timeZone: "America/New_York", timeStyle: "short",
}).format(utcInstant));
// "12:00 PM"

Python, via zoneinfo:

from datetime import datetime
from zoneinfo import ZoneInfo

pacific_time = datetime(2026, 7, 30, 9, 0, tzinfo=ZoneInfo("America/Los_Angeles"))
eastern_time = pacific_time.astimezone(ZoneInfo("America/New_York"))
print(eastern_time)
# 2026-07-30 12:00:00-04:00

Frequently asked questions

If I'm on the West Coast, when should I schedule calls with East Coast colleagues?
Starting your workday call block around 8-11 AM Pacific gives you 11 AM-2 PM on the East Coast — solidly inside their business hours without asking them to join before or after their own workday. Anything before 8 AM Pacific pushes East Coast attendees past 11 AM comfortably, but anything after roughly 11 AM Pacific starts landing after 2 PM Eastern, eating into the tail end of their day.
Is 9 AM Pacific too early to expect an East Coast reply?
No — 9 AM Pacific is already noon Eastern, squarely in their midday. The riskier end is the opposite: an 8 AM Pacific message is only 11 AM Eastern (fine), but anything sent after about 2 PM Pacific lands at 5 PM Eastern or later, likely after most East Coast colleagues have logged off.
Does working from the West Coast mean losing hours of overlap with the East Coast?
Less than you'd guess from the 3-hour zone gap alone: a standard 9-to-5 Pacific day and a standard 9-to-5 Eastern day actually overlap for 5 hours — 9 AM to 2 PM Pacific lines up with noon to 5 PM Eastern. The gap between the zones and the size of the daily overlap are two different numbers; what the overlap misses specifically is the East Coast's own morning (9 AM-noon Eastern is only 6-9 AM Pacific), which is why West Coast teams that want to catch East Coast colleagues at the *start* of their day, not just the afternoon, deliberately start earlier than a standard Pacific 9-to-5.
Why does the West Coast fall behind by exactly 3 hours, not more or less?
Because America/Los_Angeles and America/New_York are both defined relative to UTC with a fixed 3-hour difference between their offsets (UTC-8 vs UTC-5 in winter, UTC-7 vs UTC-4 in summer) — the two zones' geographic distance corresponds to roughly 3 standard time zone widths, and since the US doesn't use half-hour-offset zones the way some countries do, that distance rounds to a clean 3-hour gap rather than something fractional.
Is the date/time I enter sent to a server?
No. The conversion runs entirely in your browser using the Intl API already built into it — nothing is uploaded, logged, or stored.

Related Timezone Converter pages

Looking for a different pair or algorithm? Here are the other specific versions, plus the general tool for everything else: