World Time Zone & Meeting Planner
Find a time that works across time zones
Choose each person’s city and work hours. The planner checks the full call, finds shared windows and shows local times when no perfect overlap exists.
Meeting details
Date is based on the first locationOptional: meeting title for calendar export
Participants and working hours
Enable JavaScript to calculate meeting times.
Default workdays are Monday–Friday. Use “Workdays and name” inside a participant card for custom days, overnight shifts or an optional name. 24-hour shifts are not supported.
Meeting options for your team
Recommended meeting starts
Selected meeting in each location
Continuous shared work windows
Only windows where the whole meeting fits everyone’s working hours. Start-time ranges account for the full call duration.
Example: four cities with no shared working hour
On Monday, 9 November 2026, imagine a 60-minute call between New York, London, Dubai and Tokyo. Everyone works 09:00–17:00 local time. There is no time when all four are on shift; at most 2 of 4 can attend entirely within their working hours.
10:00 in London
It is 14:00 in Dubai, 05:00 in New York and 19:00 in Tokyo. The full hour fits London and Dubai, but not the other two.
15:00 in London
It is 10:00 in New York, 19:00 in Dubai and 00:00 Tuesday in Tokyo. This time fits New York and London instead.
Shortening the call will not create a four-way overlap if the workdays never intersect. Teams can rotate which region takes an inconvenient hour, agree to a one-off schedule change or hold two regional conversations. The examples above are specific to 9 November 2026; changing the date or work schedules can change the result.
Daily working-hours overlap
Each cell represents an hourly start time on the selected day in the first location. Its count shows how many participants can attend the entire meeting within their working hours. Select a cell to inspect everyone's local time.
Clock changes can shorten or lengthen a local day; some regions shift by 30 minutes rather than one hour. UTC offsets distinguish repeated times when clocks move back. The planner checks possible starts every 15 minutes, while this timeline shows hourly starts.
How the meeting time calculator works
Exact time-zone conversion
Each possible start is represented as one UTC instant, then converted into every participant's IANA time zone for that date. This accounts for differing daylight saving change dates and fractional-hour offsets.
Whole-meeting availability
The planner checks the full duration in 15-minute segments against each participant's local shift and selected workdays. It does not count a time as a full match if the meeting extends past someone's hours.
Why one option appears first
The planner first prefers times that keep the most people within their working hours for the entire call. If there is a tie, it considers how much of the meeting fits everyone’s schedules, then uses a fixed inconvenience score to break the tie. This is a planning aid, not a measure of anyone’s personal preferences.
See the scoring rules
Options are ordered by: (1) number of participants fully within working hours; (2) total 15-minute participant-segments within hours; (3) lowest highest individual penalty; (4) lowest sum of individual penalties; (5) earliest UTC start.
For each participant and 15-minute segment, the penalty equals the shortest clock-hour distance from the center of their shift, plus 20 if that segment is outside their working hours, 12 if its local midpoint falls between 22:00 and 06:00, and 14 if that midpoint falls on Saturday or Sunday. The participant’s score is the average across the meeting. Night and weekend warnings are shown even when a scheduled shift covers those hours.
What the planner cannot know
Calculations run in your browser; this tool does not send your entries to a scheduling server. It cannot see calendar bookings, lunch breaks, holidays or leave, and each participant has one continuous shift per workday. Future changes to official time-zone rules depend on the browser’s updates. Always confirm the chosen time with the people attending.
Time zone meeting planner FAQ
Why is there no meeting time that works for everyone?
A full match requires every participant to be on shift for the entire meeting. On 9 November 2026, New York, London, Dubai and Tokyo have no four-way overlap when all four use 09:00–17:00 local hours. The planner therefore shows options that keep as many people as possible within their schedules.
Would a shorter meeting help?
It can help if everyone has some time in common, but that period is shorter than your meeting. If their working hours never intersect at all, reducing a 60-minute call to 15 minutes will not create an overlap.
Why can the same local hour appear twice?
When clocks move back for daylight saving changes, a local time such as 01:00 can occur twice with different UTC offsets. The timeline labels each occurrence by offset. Clock changes are not always a full hour.
What if someone works nights or weekends?
Select that participant’s working days and enter the shift start and end. For example, a Friday 22:00–Saturday 06:00 shift belongs to Friday’s schedule. The planner still flags night and weekend times so everyone knows when the meeting falls.
Can I exclude lunch breaks or existing appointments?
Not automatically. Each participant has one continuous work shift per scheduled day. The tool does not read calendars, holidays, leave or breaks. Adjust the hours manually or confirm availability with the team.
Does the calendar download send invitations?
No. Downloading a .ics file creates an event you can import into a calendar, with times stored in UTC. It does not book attendees, check their diaries or send an invitation.
Will the time-zone conversion stay correct next year?
The calculation uses the date-specific time-zone rules installed in your browser, including fractional-hour offsets. Governments can change those rules, so recheck important meetings if a region announces a new clock policy.
Technical references
Reference for time-zone identifiers and changes to local UTC offsets and daylight saving rules; the planner uses the visitor's browser implementation rather than downloading live IANA data.
https://www.iana.org/time-zonesJavaScript API used for date-specific conversion and local time components.
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/DateTimeFormatAPI used to list browser-supported IANA time zones, with a fallback list for older browsers.
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/supportedValuesOf