Why the date matters
UK and US daylight-saving transitions do not always happen on the same dates.
Time difference
Compare London time with New York time using a date-aware calculator. This page is prefilled for London (Europe/London) and New York (America/New_York), but you can change the date, time, or cities anytime.
UK and US daylight-saving transitions do not always happen on the same dates.
London uses Europe/London in this calculator.
New York uses America/New_York in this calculator.
Start with the actual calendar date, then compare the local time in London with the matching local time in New York. This page uses Europe/London and America/New_York, so the calculator can apply the right local offset for that date when browser time zone data is available.
UK and US daylight-saving transitions do not always happen on the same dates. A route that is correct today may be different on a future date, so a date-aware comparison is safer than a memorized hour difference.
Before sending a calendar invite, announcement, or deadline, read the converted time back in both directions: London local time to New York local time, then New York local time back to London. This catches the most common route mistakes, including next-day arrivals, weekend dates, and daylight-saving weeks when the familiar offset is temporarily wrong.
Use the time zone converter when the same London event needs more than one destination city. Use working hours overlap when the question is not just the offset, but whether the converted time is reasonable for both teams.
The comparison uses browser time zone support with IANA-style identifiers such as Europe/London and America/New_York. Review the time zone data notes for calculation context, the editorial policy for review standards, or send feedback if a route note needs correction.
Recheck London to New York when either city is near a clock-change week, when the event is more than a few weeks away, or when the converted time lands close to midnight. A late London call can become a next-day New York event, and that date boundary is often where launch notes, support handoffs, and meeting invites go wrong.
Use this route as the first verification pass, then write the final time with both city names in the calendar description. For customer-facing announcements, include UTC plus both local times so readers can verify the same moment in their own calendar system.
For paid webinars, interviews, travel coordination, or support schedules, keep a screenshot or copied timestamp from the final conversion in the planning notes. That gives the team a simple audit trail if someone later asks why the London time and New York time were paired on that date.
Time-difference pages depend on date-aware browser time zone support, IANA-style identifiers, and periodic review when local rules change. These links keep the data method, editorial process, correction channel, and advertising privacy details close to the route content.
How offsets, IANA zones, DST changes, and corrections are handled.
Editorial policyHow route guidance is reviewed and separated from advertising.
FeedbackReport stale offsets, labels, route notes, or broken links.
Privacy policyReview cookies, analytics, ads, and local browser storage.
Compare local times and DST-aware offsets.
Los Angeles to TokyoCompare local times and DST-aware offsets.
London to SydneyCompare local times and DST-aware offsets.
San Francisco to LondonCompare local times and DST-aware offsets.
New York to TokyoCompare local times and DST-aware offsets.
London to SingaporeCompare local times and DST-aware offsets.