GMT to PST Converter

Which GMT and which PST?

Zone abbreviations are ambiguous, so this page starts by pinning both down. GMT here is Greenwich Mean Time: the IANA zone Europe/London, anchored on London. Note that GMT is also UTC±0 kept year-round, which London does not do; this page means only the London sense. PST here is Pacific Standard Time (North America): America/Los_Angeles, anchored on Los Angeles. Note that PST is also Philippine Standard Time (usually written PHT); this page means only the Los Angeles sense.

GMT in the everyday sense means London time, whichever of GMT or BST (British Summer Time) is in force. London is not on GMT all year: its offset is UTC±0 while standard time applies (its January offset) and UTC+1 while daylight saving is active (its July offset). As of September 2026 it is on BST (UTC+1). Wherever this page writes GMT, read it as "London time on the date in question".

PST in the everyday sense means Los Angeles time, whichever of PST or PDT (Pacific Daylight Time) is in force. Los Angeles is not on PST all year: its offset is UTC−8 while standard time applies (its January offset) and UTC−7 while daylight saving is active (its July offset). As of September 2026 it is on PDT (UTC−7). Wherever this page writes PST, read it as "Los Angeles time on the date in question".

The difference as of September 2026

As of September 2026, Los Angeles is 8 hours behind London. London is on UTC+1 (BST, daylight saving in effect) and Los Angeles is on UTC−7 (PDT, daylight saving in effect). Subtract one offset from the other and you have the gap. As wall clocks: 9:00 AM in London is 1:00 AM in Los Angeles, 5:00 PM in London is 9:00 AM in Los Angeles, and 9:00 AM in Los Angeles is 5:00 PM in London.

The calendar date is part of the conversion on this pair. A 9:00 AM to 5:00 PM day in London reads 1:00 AM to 9:00 AM in Los Angeles, and a 9:00 AM to 5:00 PM day in Los Angeles reads 5:00 PM to 1:00 AM the next day in London, so a time on one side can belong to a different date on the other. The converter above flags each reading that lands on the previous or next day; the date you enter is the date on the From side's clock.

Next scheduled clock changes: clocks in London go back 1 hour on Sunday, October 25, 2026 (local date), moving the offset from UTC+1 to UTC±0; clocks in Los Angeles go back 1 hour on Sunday, November 1, 2026 (local date), moving the offset from UTC−7 to UTC−8. Every one of those changes moves the gap, because the other side does not change with it.

How the gap changes through the year

Both sides of this pair observe daylight saving — London moves between UTC±0 and UTC+1, Los Angeles between UTC−8 and UTC−7 — but they do not switch on the same dates. London changes its clocks on its own calendar and Los Angeles on its own, and in the weeks between one side's switch and the other's, exactly one of them has moved. During those weeks the gap holds a value it holds only in those windows.

Over the year scanned from Sep 7, 2026, the gap takes two distinct values and changes four times. The full schedule, with dates on London's calendar and each run's length in days:

* Cut short by the edge of the scanned year: this run began before the scan started or continues past its end.

The usual state — 344 of the 365 days scanned — has Los Angeles 8 hours behind London. That is the value that holds for the largest part of the year. The briefest of the mismatch windows in the table is Oct 25, 2026 – Nov 1, 2026: 7 days at 7 hours behind, with GMT / PDT in force. Counted by who is on summer time, the scanned year splits into 211 days with both sides on summer time (8 hours behind), 21 days with only Los Angeles on summer time (7 hours behind), and 133 days with neither side on summer time (8 hours behind). Every value other than the usual 8 hours behind falls inside those 21 days with only Los Angeles on summer time.

The trap is the recurring meeting. Pin a weekly call at 9:00 AM on London's clock and, on Los Angeles's calendar, it sits at 1:00 AM for most of the year but at 2:00 AM while the gap is 7 hours behind (GMT / PDT). Pinned on Los Angeles's clock instead, the same call moves on London's calendar: 9:00 AM there is 5:00 PM in London for most of the year and 4:00 PM at 7 hours behind. Either way the meeting moves twice around each mismatch window — once when the first side switches and once when the second does — which is why the converter above evaluates the rules for the exact date rather than applying one remembered number.

Working hours that overlap

Assume a 9:00 AM to 5:00 PM day on both sides. Because the gap changes during the year, the overlap changes with it, so it is shown for each gap the pair takes:

• Los Angeles 8 hours behind London (BST / PDT or GMT / PST; 344 of the 365 days scanned): no overlap at all: when it is 9:00 AM in Los Angeles it is already 5:00 PM in London.
• Los Angeles 7 hours behind London (GMT / PDT; 21 of the 365 days scanned): 1 hour of shared working time: 4:00 PM to 5:00 PM in London, which is 9:00 AM to 10:00 AM in Los Angeles.

The 9-to-5 window is a convention, not a fact about anyone's real hours. The Meeting Planner lets you set each side's actual working hours and shows the overlap for the exact date you are planning.

Converting PST to GMT

This page serves both directions, because the reverse conversion is the same gap with the sign flipped. As of September 2026, London is 8 hours ahead of Los Angeles, so:

• 9:00 AM GMT (London) = 1:00 AM PST (Los Angeles)
• 9:00 AM PST (Los Angeles) = 5:00 PM GMT (London)
• 5:00 PM PST (Los Angeles) = 1:00 AM the next day GMT (London)

To run PST to GMT in the converter above, swap the From and To menus; the result shows both offsets for the date you enter and flags a day change whenever the reading lands on the previous or next calendar day. The readings above hold only while the gap is 8 hours behind; on the dates listed in the section above they move, in both directions at once.

More on these zones

• Current time in London — live clock, offset and next clock change.
• Current time in Los Angeles — live clock, offset and next clock change.
• Time Zone Converter — any city to any city, DST-correct for the date.
• Meeting Planner — overlap for your real working hours.
• All zone-to-zone converters — the other corridors on this site.

GMT to PST — frequently asked questions

Conversions are computed locally in your browser from its IANA time zone data; nothing you enter is transmitted. The schedule and offsets on this page were derived from the same database at build time, as of September 2026. Jurisdictions occasionally change DST law with short notice, and the IANA database follows reality — for legally critical timing, confirm against an official source. See the methodology page.