Time Zone Meeting Planner
Find the hours that fall within everyone's working day across multiple time zones, with each participant's local time. Uses live DST-aware offsets. Runs in your browser.
These zones have no hour where everyone is within 9:00–17:00 local. Widen the work-hours window or accept an early/late call for one region.
Shows every UTC hour at which all participants are inside their local work-hours window, with the local time for each. Uses your browser’s IANA time-zone data, so current daylight-saving offsets are applied automatically. Offsets are for today; a future meeting date could differ if a DST change falls in between. Everything runs in your browser.
About this tool
Scheduling a meeting across time zones is a recurring headache for distributed teams: a time that's mid-morning in New York is late evening in Tokyo, and finding a slot that's reasonable for everyone means juggling offsets in your head. This planner does that work. You add each participant's time zone and set a shared working-hours window (9:00 to 17:00 by default), and it scans all 24 hours of the day to find every hour at which every participant is inside their own working hours — then displays those overlapping slots with the corresponding local time for each person, so you can pick a slot that's fair to all. The offsets are computed from your browser's built-in IANA time-zone database, which means daylight-saving time is handled automatically and correctly for each region's current rules, rather than relying on fixed offsets that break twice a year. When no common working hour exists — a frequent reality for teams spanning, say, California and India — the tool says so plainly, and the fix is to widen the working-hours window or accept that one region takes an early or late call. A couple of practical notes: the offsets shown are for today's date, so for a meeting weeks away that straddles a DST transition (different countries change on different dates, and some don't observe DST at all) the local times could shift by an hour; and the tool works in whole hours, which is enough for planning but a few zones use 30- or 45-minute offsets that it rounds in the display. Use it to propose a slot, then confirm the exact local times with attendees. Everything runs in your browser; nothing is uploaded.
How to use it
- Add each participant and select their time zone.
- Set the shared working-hours window (e.g. 9 to 17).
- Read the list of UTC hours where everyone is within working hours, with each person's local time.
- If there's no overlap, widen the window or choose an early/late slot for one region.
Frequently asked questions
- How does the meeting planner find overlapping times?
- It checks each of the 24 UTC hours and keeps the ones where every participant's local time falls inside the shared working-hours window. Those hours are shown with each person's local time.
- Does it handle daylight saving time?
- Yes. It uses your browser's IANA time-zone data, so each region's current DST offset is applied automatically — no manual adjustment for summer/winter time.
- What if there are no common working hours?
- For widely separated zones (e.g. US West Coast and South Asia) there may be no overlap within standard hours. The tool tells you, and you can widen the window or accept an early/late call for one side.
- Are the times accurate for a future date?
- Offsets shown are for today. Because countries change DST on different dates (and some not at all), a meeting weeks out that crosses a transition could shift by an hour — confirm close to the date.
- Why are the times shown in whole hours?
- The planner scans hour by hour for simplicity. A few time zones use 30- or 45-minute offsets (e.g. India, Nepal); their local times are rounded in the grid, so verify the exact minute for those participants.
- Is anything uploaded?
- No. All calculations run entirely in your browser using its built-in time-zone data.