Timezone Meeting Planner
Find an hour that works in every city.
- Nothing is sent to a server
- Instant results
- Free, no sign-up
Related tools
All date & timeQuestions
Why does the gap between two cities change during the year?
Because North America and Europe change their clocks on different dates. Toronto is five hours behind London for most of the year and four hours behind for a few weeks each spring and autumn. Anyone with a recurring transatlantic call has noticed it silently moving twice a year. The grid takes a date precisely so those weeks are shown correctly.
Why does the weekday matter as much as the hour?
Because a 21:00 Toronto meeting is 10:30 the next day in Mumbai. Booking it for 'Tuesday' without checking which Tuesday is a reliable way to have someone join a day late. Every cell shows the local weekday alongside the time for exactly this reason.
Which places break the usual assumptions?
India is UTC+5:30 and Nepal is UTC+5:45 — half-hour offsets that surprise scheduling software regularly. Newfoundland is UTC−3:30, the only half-hour zone in North America. The southern hemisphere has daylight saving inverted, so the gap to Sydney swings by two hours across the year rather than one. Saskatchewan, Arizona and most of Asia and Africa do not observe it at all.
How are the colours decided?
Green is 09:00 to 17:00, amber is 08:00 to 20:00 — early or late but workable — and red is outside those. Scan down the grid for a row that is green everywhere, or settle for amber. On a wide spread of timezones there is often no green row at all, which is itself the useful answer.
What is the most reliable way to schedule across zones?
Send a calendar invitation rather than a time in an email. An invitation carries an instant and every recipient's software renders it in their own zone, which removes the entire class of error. If you must write a time in prose, include the zone and the date: 'Tuesday 12 May, 14:00 Toronto (EDT)'.
About timezone planner
Reading the grid
Each row is one hour of real time, shown as the local clock in every city you have selected. Green is 09:00–17:00, amber is early or late but workable, red is a time nobody wants a meeting. Scan down for a row that is green — or at least amber — everywhere.
The weekday next to each time matters as much as the hour. A 21:00 Toronto meeting is 10:30 the next dayin Mumbai, and booking it for “Tuesday” without checking which Tuesday is a classic way to have someone join a day late.
Why offsets are not fixed
Toronto is five hours behind London for most of the year and four hours behind for a few weeks in spring and autumn, because North America and Europe change their clocks on different dates. Anyone with a recurring Monday call between the two will have noticed it silently moving twice a year.
This is why the grid takes a date. Offsets come from your browser’s IANA timezone database and are calculated for the day you pick, so the awkward weeks are shown correctly rather than approximated.
Places that break the assumptions
- India is UTC+5:30 — a half-hour offset, which surprises scheduling software regularly. Nepal is UTC+5:45.
- Newfoundland is UTC−3:30, the only half-hour zone in North America.
- Most of the southern hemisphere has daylight saving inverted, so the gap to Sydney swings by two hours across the year, not one.
- Saskatchewan, Arizona and most of Asia and Africa do not observe daylight saving at all, so their offset to you changes when you change.
Practical advice
Send calendar invitations rather than times in an email. A calendar invitation carries an instant and every recipient’s software renders it locally, which removes the whole class of error. If you must write a time in prose, include the zone and the date: “Tuesday 12 May, 14:00 Toronto (EDT)”.
Related
Count down to the moment with the countdown timer, or work out spans with days between dates.