Meeting Planner Across Time Zones
Choose a dated time in an explicit source zone and compare local dates and times before making a calendar file.
Choose a date and source zone, then compare local times before exporting a calendar file.
Before you share
- Choose a dated time and explicit source zone.
- Select two to four locations.
- Review local dates, offsets and end times.
- Copy the summary or download a UTC calendar file.
Uses this browser’s IANA time-zone rules, which may be outdated. Dates 1990-2100; 2-4 locations; 15-480 minutes. Ambiguous or nonexistent local times are rejected. Does not check availability or send invites.
Your time comparison
Select a source time and locations, then compare.
The example shows date rollover from Toronto to Sydney.Time-zone data and planning limits
Rules come from your browser’s time-zone database and may change. Keep your browser updated and confirm important meeting times with participants. This planner supports seven named locations, dates from 1990 to 2100, and 15-480 minutes. Source times in daylight-saving gaps or repeated hours are rejected rather than guessed. Calendar files use UTC; your calendar app displays its selected local zone. Reloading clears the workspace.
Instructions and examples
From input to output
- Enter Meeting date and time and choose its Source time zone explicitly.
- Set Duration and choose two to four Compare locations. Add a Calendar title if useful.
- Select Compare times, inspect start/end dates and offsets, then copy the summary or download ICS.
Settings and result behavior
- The input belongs to the source location, not your device zone. Include the source among comparison locations if you want its row.
- Duration is elapsed minutes. Clock changes can affect local end time. Blank title becomes “Planned meeting”.
- ICS stores UTC; your calendar application displays it in its chosen zone.
A worked example
- Input
9 October 2026, 09:00 in America/Toronto.
- Settings
- 60 minutes; Toronto, London and Sydney selected.
- Expected result
Toronto 09:00-10:00; London 14:00-15:00; Sydney 00:00-01:00 on 10 October, using those dates’ zone rules.
Supported input and limits
Dates 1990-2100, seven supported named locations, 2-4 comparison rows and 15-480 whole minutes. ICS export does not send invitations or check availability.
Uses this browser’s IANA time-zone rules, which may be outdated. Dates 1990-2100; 2-4 locations; 15-480 minutes. Ambiguous or nonexistent local times are rejected. Does not check availability or send invites.
If the result is unexpected
- A daylight-saving gap or repeated source hour is rejected. Choose an unambiguous time and confirm it with participants.
- If a local date rolls forward or backward, check the date as carefully as the hour. Browser zone rules may be outdated.
Check before using the result
Confirm important times with participants and inspect the imported calendar event. A displayed proposal does not mean anyone is free.
Report a problem with this tool. Include a nonsensitive example and your browser details.
Questions about this tool
Does the meeting planner check availability or send invites?
No. It compares a dated time across 2-4 locations using browser time-zone rules and can create an ICS file. Ambiguous or nonexistent local times are rejected. Verify the date and import the file yourself.