One meeting, three calendars
Monday in London. Tuesday in Singapore.
Imagine a call fixed at 16:00 in London on 15 January 2024. These cards show the same instant, using the same browser timezone system as the converter.
London
15 Jan, 16:00
Europe/London
New York
15 Jan, 11:00
America/New_York
Singapore
16 Jan, 00:00
Asia/Singapore
Put the date in the invitation
Singapore has crossed midnight, so copying only “16:00” or only “Monday” would leave out important information. Pin both the date and time in the reference zone, add the other cities, then read each card’s date as well as its clock.
The +1 day or −1 day badge compares that city’s calendar date with the reference city. It does not mean the meeting lasts a day longer or that the conversion is wrong. When sharing the plan, include the city or timezone and the full date.
Recurring meetings need a second look
A city name represents a set of timezone rules, while a UTC offset represents the difference at one instant. Two countries may change clocks on different weekends, so even a familiar weekly meeting can shift locally for part of the year. Check the actual occurrence rather than reusing an offset from an older invitation.
During a clock change, some local times happen twice or do not happen at all. If your pinned time is close to that transition, confirm the intended UTC instant with the organizer. This tool is a comparison view, not a recurring-event scheduler.
Live now returns to the current instant. Pinned times and added zones remain in this browser session; they are not uploaded or saved. Results depend on the timezone data shipped with your browser, so keep it updated when local clock rules change.