Date & Time
Multi-Timezone Meeting Planner
Plan meetings across multiple timezones. Add cities, pick a date and time, and instantly see the local time for every participant. Highlights working-hours overlap. Download .ics file.
Cities (2/10)
24-hour overlap grid (reference: New York)
| City | 00 | 01 | 02 | 03 | 04 | 05 | 06 | 07 | 08 | 09 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| New York | 00 | 01 | 02 | 03 | 04 | 05 | 06 | 07 | 08 | 09 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 |
| London | 05 | 06 | 07 | 08 | 09 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | ↩0 | 01 | 02 | 03 | 04 |
| Overlap |
Working hours Partial No overlap Candidate time
Best windows (all cities working)
How to plan a meeting across timezones
Add the cities where your participants are located, then drag the candidate time slider to find a window that falls within everyone's working hours. The overlap bar at the bottom of the grid shows green for full overlap, yellow for partial, and gray for no overlap.
Best times for global team meetings
There is rarely a perfect time for a truly global team. Common strategies include rotating the inconvenient slot across team members, scheduling "async first" with a short synchronous check-in, or anchoring on a time that overlaps for the most people even if a minority must attend off-hours.
- Americas + Europe: Early morning Eastern (8–10am ET) overlaps with early afternoon in London and evening in Berlin.
- Europe + Asia: Late afternoon in London (4–5pm GMT) is early morning in Singapore or Tokyo the next day.
- Americas + Asia: Very difficult. 7am Pacific = 11pm Tokyo (next day). Video recordings plus async follow-up are often more humane.
Common timezone gotchas
- DST transitions: Clocks change on different dates in the US, EU, and Australia. A window that works in March may not work in April.
- Half-hour and 45-minute offsets: India (UTC+5:30), Nepal (UTC+5:45), and Iran (UTC+3:30) have non-standard offsets.
- Southern hemisphere DST: Australia and New Zealand observe DST in their summer (October–March), opposite to the northern hemisphere.
World clock reference
| City | UTC offset (standard) | UTC offset (DST) |
|---|---|---|
| Los Angeles (PT) | UTC−8 | UTC−7 |
| New York (ET) | UTC−5 | UTC−4 |
| São Paulo (BRT) | UTC−3 | UTC−2 |
| London (GMT) | UTC+0 | UTC+1 |
| Paris / Berlin (CET) | UTC+1 | UTC+2 |
| Dubai (GST) | UTC+4 | No DST |
| Mumbai (IST) | UTC+5:30 | No DST |
| Singapore (SGT) | UTC+8 | No DST |
| Tokyo (JST) | UTC+9 | No DST |
| Sydney (AEST) | UTC+10 | UTC+11 |
Meeting invitation best practices
- Always include the UTC time in the invitation body: "3pm ET / 8pm UTC" - attendees in unusual timezones can convert from UTC more reliably than from a regional zone that may or may not observe DST.
- Attach a .ics calendar file: modern calendar apps display the event in each recipient's local timezone automatically when opened from a proper .ics attachment.
- Specify whose timezone applies: "3pm New York time" is clearer than "3pm EST" because EST is sometimes misused to mean ET (which is EDT during summer).