PST to GMT Converter

Scheduling between the US West Coast and the UK is a common transatlantic remote-work problem, and it’s also the one pair on this site where “GMT” in a search query and the technically correct term genuinely diverge. Someone searching “PST to GMT” almost always means “what time is it right now for my London colleague” — which, for about half the year, isn’t GMT at all, but British Summer Time (BST, UTC+1). This page is built around that real intent: it converts Pacific time against the UK’s actual civil timezone (Europe/London), which correctly shifts between GMT and BST on the UK’s own calendar, rather than pinning the result to a fixed GMT reference that would silently be an hour wrong every summer. (If you specifically want the fixed, never-shifting GMT standard rather than UK local time, the UTC to GMT page covers that distinction directly.)

The baseline gap is a steady 8 hours, in both winter (Pacific Standard Time, UTC-8, against GMT, UTC+0) and summer (Pacific Daylight Time, UTC-7, against BST, UTC+1) — the difference between the two zones doesn’t move even though each zone’s own offset does, since both sides shift forward by the same one hour at roughly the same time of year. What makes this pair genuinely more complicated than a same-country conversion is that the US and the UK don’t flip their clocks on the same dates: the US moves to daylight saving on the second Sunday of March and back on the first Sunday of November, while the UK/EU move on the last Sunday of March and last Sunday of October. For a window of roughly one to three weeks each spring and about a week each autumn, one side has already made its seasonal switch and the other hasn’t — briefly narrowing the usual 8-hour gap to 7 hours instead, a wrinkle that doesn’t exist for any of this site’s US-only zone pairs (where both sides always change on the same date).

Working through a concrete case: 8:00 AM Pacific on July 30, 2026 — solidly summer for both sides, no transition-window wrinkle in play — converts to 4:00 PM in London (BST, UTC+1), the steady-state 8-hour gap, matching a summer Pacific morning landing on a UK late afternoon.

Converting Pacific time to UK time programmatically

JavaScript, via the round-trip technique, targeting the real UK zone rather than a fixed GMT offset:

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, 8, 0, "America/Los_Angeles");
console.log(new Intl.DateTimeFormat("en-US", {
  timeZone: "Europe/London", timeStyle: "short", timeZoneName: "short",
}).format(utcInstant));
// "4:00 PM GMT+1" — BST, correctly, since it's July

Python, via zoneinfo:

from datetime import datetime
from zoneinfo import ZoneInfo

pacific_time = datetime(2026, 7, 30, 8, 0, tzinfo=ZoneInfo("America/Los_Angeles"))
uk_time = pacific_time.astimezone(ZoneInfo("Europe/London"))
print(uk_time)
# 2026-07-30 16:00:00+01:00