City time difference
Los Angeles to London: current time and meeting overlap.
Quick answer: London is 8 hours ahead of Los Angeles. No overlap between Los Angeles and London for the selected working hours.
Los Angeles UTC-7 · PDT
10:20 AM London UTC+1 · GMT+1
6:20 PM
overlap
No standard overlap
none Suggested meeting window
No standard 60-minute window fits both workdays.
Planning guide Best times and checks before sending. Show Hide
What to do with this city time difference.
Use this page when you need both the current time difference and a working-hour overlap check between Los Angeles and London.
1
Start with the overlap card: it shows the strongest standard workday window for Los Angeles and London.
2
If the overlap is tight, choose the earliest slot that still lands inside both teams' working hours.
3
For recurring meetings, rotate the burden instead of forcing the same side into early mornings or late evenings every week.
When this page is useful
Real situations for Los Angeles to London.
These notes focus on the scheduling or conversion mistakes people actually make before sending a time.
West Coast to UK overlap
Use Los Angeles to London when a West Coast team needs to understand how narrow the UK overlap is before sending an invite.
Avoid late-London defaults
This page is most useful for avoiding late-London meetings; if the only slot is painful, shorten the agenda or move updates async.
West Coast launch coordination
Use Los Angeles to London before setting release calls because West Coast morning often collides with London end-of-day.
Scheduling workflow Show Hide
Include the date and both local times.
Suggested meeting window: use the overlap shown above for Los Angeles and London. Include both local times in the calendar note before sending.
Confirm the date
Pick the actual date first so Los Angeles to London reflects daylight-saving rules for that day.
Check the overlap
Use the overlap status before choosing a time. Good overlap fits the selected hours; tight or none means another slot or async update may be better.
Share both sides
Send the Los Angeles time and the London time together so nobody has to recalculate.
Reference table Hourly conversion table Show Hide
| Los Angeles | 24h | London | 24h | Date |
|---|---|---|---|---|
| 12:00 AM | 00:00 | 8:00 AM | 08:00 | same day |
| 1:00 AM | 01:00 | 9:00 AM | 09:00 | same day |
| 2:00 AM | 02:00 | 10:00 AM | 10:00 | same day |
| 3:00 AM | 03:00 | 11:00 AM | 11:00 | same day |
| 4:00 AM | 04:00 | 12:00 PM | 12:00 | same day |
| 5:00 AM | 05:00 | 1:00 PM | 13:00 | same day |
| 6:00 AM | 06:00 | 2:00 PM | 14:00 | same day |
| 7:00 AM | 07:00 | 3:00 PM | 15:00 | same day |
| 8:00 AM | 08:00 | 4:00 PM | 16:00 | same day |
| 9:00 AM | 09:00 | 5:00 PM | 17:00 | same day |
| 10:00 AM | 10:00 | 6:00 PM | 18:00 | same day |
| 11:00 AM | 11:00 | 7:00 PM | 19:00 | same day |
Related timezone pages
Keep comparing without starting over.
Timezone questions answered
What is the time difference between Los Angeles and London?
This page compares Los Angeles and London using IANA timezone identifiers, current UTC offsets, and a working-hours overlap check.
How accurate is this timezone page?
useChrono uses IANA timezone identifiers through the browser and platform Intl API, so daylight-saving changes are reflected when the runtime timezone data is current.
Should I use the converter or the meeting planner?
Use the converter for one exact time. Use the meeting planner when the time needs to be fair for people in both locations.
Why should I include both local times in an invite?
Calendar apps can display times in the viewer timezone. Including both local times reduces mistakes for remote teams and cross-region handoffs.
Data note: useChrono uses IANA timezone identifiers and the platform Intl API. Daylight-saving rules can change, so confirm mission-critical times in your calendar system.