Find the hours that fall inside the working day for everyone, across up to 8 time zones.
Uses your browser’s time-zone data, so daylight saving is handled correctly.
How do you find a meeting time across time zones?
Convert each participant’s working hours into UTC and look for the overlap. Use IANA zone names like Europe/London rather than abbreviations such as EST, and calculate for the specific date — daylight saving starts on different days in different countries, which is what makes recurring meetings drift.
Understanding your result
Manual time-zone arithmetic goes wrong for one reason above all others: daylight saving. Offsets are not fixed, the northern and southern hemispheres shift in opposite directions, the changeover dates differ between countries, and places such as India, Japan and most of Africa never change at all. That means the gap between London and New York is five hours for most of the year but four for a few weeks in spring and autumn — which is exactly when recurring meetings quietly break. Reading offsets from a real time-zone database for the specific date removes the guesswork. When no slot works for everyone, rotating which region takes the awkward hour is fairer than permanently burdening one team.
Formula and method
For each of the 24 UTC hours, the local time in every zone is computed from that zone’s offset on the chosen date. An hour is marked as working when every participant falls inside the working day, and as workable when everyone is within two hours of it.
Assumptions and limitations
This compares whole hours only and assumes the same working day everywhere, so it will not know about local lunch conventions, part-time schedules, prayer times or public holidays. Zones must be entered as IANA names such as Europe/London rather than abbreviations like EST, which are ambiguous. For dates far in the future, results depend on currently published daylight-saving rules, and governments do occasionally change them.
Worked example
London, New York and Kolkata share only a narrow window: mid-afternoon in London is late morning in New York and evening in Kolkata, so the workable slots cluster tightly rather than spreading through the day.
How to use this tool
- Enter each participant’s time zone, one per line.
- Set the date if you are booking more than a few weeks ahead.
- Adjust the working day if your team starts earlier or later.
- Pick an hour marked as working for everyone.
Common mistakes to avoid
- Using ambiguous abbreviations like EST or CST instead of IANA names.
- Assuming the offset between two cities is fixed all year.
- Forgetting that a recurring meeting shifts when only one side changes clocks.
- Always giving the same team the unsociable hour.
About the Time Zone Meeting Planner
The Time Zone Meeting Planner compares up to eight time zones and shows which hours fall inside the working day for everyone. Offsets are read from your browser’s own IANA time-zone database for the date you are planning, so daylight saving is applied correctly rather than assumed.
Who should use this tool
Distributed teams, freelancers with international clients and anyone scheduling across continents.
Benefits
- Handles daylight saving for the specific date you are booking.
- Compares up to eight zones at once, not just two.
- Shows near-misses when no hour works perfectly.
- Adjustable working day, since not everyone works 9 to 5.
Practical use cases
- Scheduling a recurring standup across three continents.
- Finding a call time with a client in another country.
- Planning a webinar that suits several regions.
- Checking whether a proposed time is unreasonable for someone.
Explore all Date and Time tools
Frequently asked questions
What time zone names should I use?
IANA names such as Europe/London, America/New_York or Asia/Kolkata. Abbreviations like EST or IST are ambiguous — IST alone can mean Indian, Irish or Israeli time.
Does this handle daylight saving?
Yes. Offsets come from your browser’s time-zone database for the date you choose, so a meeting planned across a clock change is calculated correctly.
Why does my recurring meeting drift?
Because regions change clocks on different dates, and some never do. For a few weeks each year the gap between two cities differs from its usual value, which shifts one side of the meeting.
What if no time works for everyone?
The planner shows hours that are within two hours of the working day. Consider rotating the awkward slot between regions, or recording the session for anyone who cannot attend live.
How many zones can I compare?
Up to eight at once, which covers most distributed teams. Beyond that, the overlap is usually empty and asynchronous working is the better answer.