How the converter works
Choose a date, a time and two places. The converter works out the exact moment you mean in the first place, then shows the clock time in the second place at that same moment. It uses the rules for the date you choose, not today's, so a call booked for after a clock change is converted correctly.
For dates from 2025 to 2028, the rules come from the IANA time zone database (release 2026c), built into this page. That includes 2026 changes such as British Columbia's move to permanent UTC−7, Alberta's move to permanent UTC−6 and Morocco's return to UTC+0. Older phones and browsers do not always have these changes yet. For dates outside that range, the converter falls back on your browser's own time zone data and tells you when it does.
Times that happen twice, and times that never happen
On the night the clocks go forward, an hour is skipped. In London, 01:30 on Sunday 29 March 2026 never happened: the clocks jumped from 01:00 straight to 02:00. On the night the clocks go back, an hour happens twice. In New York, 01:30 on Sunday 1 November 2026 happens once on EDT (UTC−4) and again an hour later on EST (UTC−5). If you enter a time like this, the converter says so: for a skipped time it suggests the nearest valid one, and for a repeated time it shows both possible results.
Worked examples
- 15:00 in London on Friday 23 October 2026 is 10:00 in New York (5 hours behind).
- 15:00 in London on Monday 26 October 2026 is 11:00 in New York (4 hours behind). The UK has changed its clocks, but the US does not change until 1 November.
- 09:00 in Los Angeles on Monday 16 November 2026 is 10:00 in Vancouver, because British Columbia no longer puts its clocks back.
- 09:00 in Sydney on Monday 11 January 2027 is 22:00 on Sunday 10 January in London (11 hours behind).
Need a time that suits several places? Use the meeting planner. For regular city pairs, our time difference pages list every date on which the gap changes.