About this tool
Find realistic meeting times across time zones by comparing each participant's working hours, local schedule, and meeting duration.
Meeting Overlap Finder is not just a timezone converter. It is meant for distributed teams that need realistic meeting windows across multiple local schedules and working-hour constraints.
- Supports multiple participants with different IANA time zones and local working hours.
- Uses participant 1's local date while resolving every other participant's adjacent local date automatically.
- Suggests scored meeting slots, shows every local time, and exports the selection to Google Calendar or RFC 5545 ICS.
How to use Meeting Overlap Finder
Set the date in participant 1's time zone, add each participant with IANA time zones and work hours, then compare the highest-scoring windows in every local time. Select one result to copy a share link, open Google Calendar, or download a UTC-based ICS file.
When this tool is useful
- Find realistic meeting slots across distributed teams in different IANA time zones.
- Compare working hours before scheduling interviews, standups, or recurring project calls.
- Share overlap windows with teammates before sending calendar invites.
Practical tips
- Treat participant 1 as the date reference; teammates may see the selected instant on an adjacent local date.
- Set each participant's local work hours before judging whether a slot is truly reasonable.
- Use shorter durations first when overlap is tight, then widen only if needed.
- Recheck far-future plans because browser time-zone data can change when governments update daylight-saving rules.
Examples you can test
Load an example, compare the result with the expected output, then replace it with your own input.
US and Europe planning call
Example input
San Francisco 9:00-17:00, New York 9:00-18:00, London 9:00-17:00, duration 30 minutes
Expected output
A narrow late-morning US / late-afternoon London overlap, scored higher when it avoids the edge of each workday.
This scenario is common for product, sales, and support teams that need a slot acceptable on both sides of the Atlantic.
APAC and US handoff
Example input
Seoul 9:00-18:00, Singapore 9:00-18:00, San Francisco 8:00-16:00, duration 45 minutes
Expected output
Either an early US slot or a late APAC slot, depending on the selected date and daylight saving offset.
When overlap is thin, reducing meeting duration often produces more humane options than forcing a one-hour call.
Validation checklist
- Use IANA time zones such as America/New_York or Asia/Seoul instead of fixed UTC offsets for future dates.
- Confirm the selected date because daylight saving time can shift overlap windows.
- Check whether a mathematically valid slot is still acceptable for every participant's local workday.