Time Zone Meeting Planner

1. 1Add each city or time zone — the first one is the reference.
2. 2Choose the meeting date and the working hours to aim for.
3. 3Look for the hours marked ✓, which fall within working hours everywhere.
4. 4Select an hour to see it in every city, then copy the times into your invite.

Each column is one hour in the reference city. For every city the tool works out the local time at that moment from your browser's built-in time-zone database — the same IANA rules operating systems use — so daylight saving, half-hour offsets such as India's and 45-minute offsets such as Nepal's are all correct for the date you choose.

An hour counts as good for a city when the whole hour falls inside the working hours you set, on a weekday. Early mornings and evenings are marked separately from night and weekends, so when there is no perfect overlap you can see the least disruptive compromise.

Daylight saving starts and ends on different dates in different countries — the United States changes its clocks weeks before Europe does — so the overlap between two cities can shift by an hour for part of the year. Choosing the actual meeting date, not just today, avoids that trap.

• Plan with the actual meeting date, not today. Countries change their clocks on different dates, so an overlap can move by an hour for a few weeks a year.
• When there is no hour that suits everyone, rotate the early or late slot between teams rather than always giving it to the same people.
• Write the time zone or city next to every time in the invite, such as 14:00 London / 09:00 New York, so nobody has to convert.
• For a recurring meeting, check the overlap again around March and October–November, when clocks change.

• Unix timestamps explained: seconds, milliseconds and time zones
• How to schedule a meeting across time zones without mistakes
• EST vs EDT, GMT vs UTC: time zone abbreviations explained
• ISO 8601 date format explained (YYYY-MM-DD and beyond)