Quick answer
San Francisco and London share approximately 1 hour of business hours overlap within standard working times: 8 AM PST / 4 PM GMT. This is the tightest major international overlap in regular business use. The gap does not improve in summer because both cities observe DST together. The entire SF–London scheduling strategy must be built around this single hour.
The 1-hour reality
| SF time | London time | Both within hours? | London follow-up time |
|---|---|---|---|
| 7 AM PST | 3 PM GMT | Yes (SF early start) | 2 hours |
| 8 AM PST | 4 PM GMT | Yes — the only standard slot | 1 hour |
| 9 AM PST | 5 PM GMT | London at close | 0 hours |
| 10 AM PST | 6 PM GMT | No — London past hours | — |
Why summer does not help
San Francisco observes Pacific Daylight Time (PDT, UTC‑7) in summer. London observes British Summer Time (BST, UTC+1) in summer. Both shift forward by one hour. The gap between them stays at 8 hours year-round for most of the calendar — 8 AM PDT = 4 PM BST, exactly the same relationship as 8 AM PST = 4 PM GMT.
The exception is the brief late-March window when the US has moved to PDT but the UK has not yet moved to BST. During those 1–2 weeks, the gap is temporarily 7 hours: 8 AM PDT = 3 PM GMT. London gets a 2-hour post-meeting window during this period. If you have a particularly important call requiring London same-day action, scheduling it in this late-March window is a genuine tactical option.
Building a workflow around 1 hour of overlap
Treat 8 AM Pacific as the single live anchor. One scheduled meeting per day or per week at 8 AM PST / 4 PM GMT handles all decisions requiring real-time input from both sides. Everything else is async.
Strict time discipline. A 60-minute meeting starting at 8 AM Pacific / 4 PM London ends at 9 AM Pacific / 5 PM London — exactly at London's standard close. Any overrun takes London past their working day. The standing rule for SF–London calls: hard stop at 45 minutes, leaving London 15 minutes of buffer. Overrun items move to the next day's meeting or to async.
Async-first for everything that does not need real-time input. Information sharing, status updates, document review, and non-urgent questions all move to shared documents, structured Slack or Teams channels, or recorded short videos. San Francisco creates async content during their afternoon (London is asleep). London reviews and responds during their morning (San Francisco is asleep). The live call handles only what async cannot.
Front-load the agenda. In a 45-minute SF–London call, London has no same-day buffer for any item discussed in the second half. Put items requiring London action — approvals, decisions, blockers — in the first 20 minutes. Informational items and open questions go last. Agenda structure is a scheduling tool on this route, not just a courtesy.
Who uses this route
SaaS and technology companies — San Francisco is the global centre of technology venture capital and many of the world's largest software companies. London is their primary European presence. SF–London teams are among the most common international configurations in the tech industry, and 8 AM Pacific / 4 PM London is the de facto standard for this configuration. See the 8 AM PST in London and 8 AM Pacific to UK pages for the specific time conversions.
Venture capital — San Francisco VC firms with London portfolio companies use the 8 AM Pacific slot for portfolio reviews and board prep calls. The London company arrives at 4 PM with a full day's context; the SF investor starts their day with London's output.
Media and entertainment — Streaming platforms and media companies with SF headquarters and London production or distribution use 8 AM Pacific for commissioning and distribution calls. London creative teams are available for one post-production hour before their day closes.
Frequently asked questions
What are the overlapping business hours between San Francisco and London?
Approximately 1 hour: 8 AM PST / PDT = 4 PM GMT / BST. This is London's final standard working hour. It does not expand in summer because both cities observe DST together, keeping the 8-hour gap constant.
Is there a better meeting time than 8 AM SF / 4 PM London?
Within standard hours: no. 7 AM Pacific / 3 PM London gives London 2 hours of follow-up but requires SF to start very early. 9 AM Pacific / 5 PM London is London's standard close with zero follow-up time. The 8 AM Pacific slot is the only window where both sides are simultaneously within standard working hours.
Why doesn't the SF–London overlap improve in summer?
Both cities observe DST and shift forward by one hour simultaneously. PDT (UTC‑7) and BST (UTC+1) maintain the same 8-hour gap as PST and GMT. The exception is the 1–2 weeks in late March when the US has moved to PDT but the UK has not yet moved to BST: 8 AM PDT = 3 PM GMT, a 2-hour London buffer.
How do SF–London teams manage with 1 hour of overlap?
One scheduled live meeting at 8 AM Pacific / 4 PM London serves as the decision anchor. It runs 45 minutes maximum. All other coordination is async: shared documents, recorded updates, structured messaging channels. SF creates async content in their afternoon; London reviews it in their morning. The live call handles only what requires real-time input from both sides.