Meeting Planner
This free time zone meeting planner helps you find a meeting time that works across multiple locations. Add the cities you need (your own is detected automatically) and it shows each location's working hours side by side, correctly handling daylight saving time for every zone, and highlights the best overlapping window.
How to Use It
- Your own time zone is detected automatically and added as the first location.
- Search for and add more cities (2 or more) using the search box.
- Adjust each location's working hours if they differ from the default 9:00 to 17:00.
- The grid and best-overlap summary update instantly as you add locations or change hours.
How It Works
Every location's current offset from UTC is calculated live using its actual time zone rules, not a fixed number, so daylight saving transitions are always reflected correctly, including Southern Hemisphere zones where daylight saving runs on the opposite schedule from the Northern Hemisphere.
Each location's working hours (9:00 to 17:00 local time by default, adjustable per location) are converted to a common UTC timeline, then compared minute-by-minute across every added location to find the longest stretch where everyone is available. That window is highlighted at the bottom of the grid and summarized above it.
A simplified worked example: a location at UTC−5 working 9:00 to 17:00 local is available from 14:00 to 22:00 UTC. A second location at UTC+1 working the same local 9:00 to 17:00 is available from 08:00 to 16:00 UTC. The overlap between those two UTC ranges is 14:00 to 16:00 UTC, which is 9:00 to 11:00 local time for the first location, and 15:00 to 17:00 local time for the second. That's the two-hour window the planner would highlight, computed the same way regardless of how many additional locations are added, just intersected across all of them at once instead of just two.
Everything runs client-side in your browser using your device's own time zone database. No location data is sent anywhere.
Frequently Asked Questions
How does this planner handle daylight saving time mismatches?
Each location's current UTC offset is recalculated live from its actual time zone rules (not a fixed number), so daylight saving transitions are handled automatically. This includes Southern Hemisphere zones like Sydney or Auckland, where daylight saving runs on the opposite half of the year from the Northern Hemisphere. If two locations are mid-transition on different dates, the overlap shown always reflects today's actual offsets.
What's the difference between a time zone and a UTC offset?
A UTC offset (like "UTC+2") is just a fixed number of hours from Coordinated Universal Time at a single moment. A time zone (like "Europe/Paris") is a set of rules for a region, including when and how its offset changes for daylight saving. Two places can share the same UTC offset for part of the year and differ for the rest, which is why this tool works with named time zones instead of raw offsets.
Why is there no overlap shown for some location combinations?
If the selected locations' working hours don't intersect at all (for example, two places on nearly opposite sides of the globe both working a standard 9-to-5), there may be no shared working-hour window on that day. Try adjusting the working hours for one or more locations to find any workable overlap, such as an early start or a later finish.
How many locations can I add?
There's no hard cap built into the tool. Add as many as your meeting actually needs. The grid and overlap calculation scale to however many locations are added, though in practice, finding a shared working-hour window gets harder the more locations (and time zones) are involved.
Does this account for weekends or different work-week schedules across countries?
No, this planner works from each location's daily working hours only (like 9:00 to 17:00), not a weekly schedule, so it doesn't know that some countries observe a Friday-Saturday weekend instead of Saturday-Sunday. If you're planning across regions with different work weeks, double-check the actual day of the week against each location's local calendar before finalizing a time.
If it's already tomorrow in one location, does the planner show that?
The grid itself is built on a shared UTC timeline underneath each location's local hours, so a location where it's already the next calendar day is handled correctly in the underlying math, even though the display focuses on local working hours rather than explicitly calling out the date difference. If a meeting time crosses midnight for a location, double-check that location's actual calendar date before sending an invite.
What if two different time windows both work equally well?
The tool highlights the single longest contiguous overlap window it finds. If your locations genuinely have more than one separate workable window (for example, an early-morning overlap and a separate late-afternoon overlap), only the longest of those is highlighted by default. It's worth checking the full grid rather than only the summary if timing flexibility matters to your group.