Plan meetings around daylight-saving changes

Use the meeting date and a named zone to avoid seasonal offset mistakes.

“New York is five hours behind London” is not a safe year-round scheduling rule. Regions can change clocks on different dates, temporarily changing the difference between them. Plan with the date of the meeting and a named zone.

A date-specific example

On March 19, 2026, 12:00 in New York is 16:00 in London. On September 19, 2026, the same New York wall time is 17:00 in London. Copying a remembered offset from one date to another can shift an invitation by an hour.

Build the conversion

1. Open the converter.
2. Choose the organizer's city as the source zone and enter the meeting's date and time there.
3. Select the attendee's zone and read the full result, including its date.
4. For another attendee, change the destination only. For a recurring series, check representative dates before and after clock changes.

Times that do not have one answer

In New York on March 8, 2026, clocks skip 02:30. Entering that time produces a warning because no instant has that local reading. On November 1, 2026, 01:30 occurs twice. The first occurrence corresponds to 05:30 UTC, and the second to 06:30 UTC. Choose the occurrence before communicating the result.

Share the appointment clearly

Include a date and named zone in written messages, and attach a zone to calendar invitations. Abbreviations can be ambiguous: CST may mean different things in different regions. Named zones preserve regional rules rather than assuming one fixed offset.

This site's results use the browser's time-zone database. Governments can change future rules, and older browsers may have older data. For events affected by a recent rule change, verify the relevant local announcement and update the browser. The IANA time-zone database is the underlying reference used by many systems.

Updated September 19, 2026 · ClockWithSeconds / Cool My World · Report a correction