Timezone Meeting Planner
Plan meetings across time zones. Add cities and see a 24-hour overlap grid that highlights everyone's working hours, flags day changes, and finds the best slots when all participants are awake.
Add a member
Loading planner…
How the planner works
Add the people you meet with as members. Each row is one member; each column is one hour of the reference timezone (auto-detected from your browser, or set manually). For every hour the planner converts that instant into each member's local time and colors the cell against that member's own working hours:
- Green: inside the member's working hours — good to meet.
- Amber: within 2 hours of their start/end — workable for a short call.
- Grey: outside their hours — avoid.
The tool automatically pre-selects the best slot — the hour where everyone is within working hours, or, if none exists, the hour with the most overlap — so you see a workable answer before touching anything. A +1d / −1d badge flags when the meeting lands on a different calendar day for that member.
Per-member working hours
A global "9–5" doesn't exist. An engineer in Berlin may work 10:00–18:00 while a partner in Mumbai works 11:00–19:00. Set each member's real start and end hours and the overlap math uses their schedule, not a generic assumption — so the suggested slot is one everyone can actually attend.
Members, their timezones, and working hours are saved on this device, so your team is still set up the next time you open the planner. Nothing is sent to a server.
Time zones, UTC offsets & DST
You can pick from the full IANA database (400+ zones), search by country, city, or flag, or choose a fixed UTC±offset (no daylight saving) when a person isn't tied to a specific city. The current offset is shown next to every option.
Offsets are political, not purely geographic: they span UTC−12 to UTC+14, some regions use 30- or 45-minute offsets (India UTC+5:30, Nepal UTC+5:45), and daylight saving shifts on different dates in each hemisphere. Conversion uses the browser's Intl engine, so DST is applied correctly for the date you choose.
| Hub | Standard offset | Note |
|---|---|---|
| Los Angeles | UTC−8 | DST −7 |
| New York | UTC−5 | DST −4 |
| London | UTC±0 | DST +1 |
| Berlin | UTC+1 | DST +2 |
| Mumbai | UTC+5:30 | No DST |
| Singapore | UTC+8 | No DST |
| Tokyo / Seoul | UTC+9 | No DST |
| Sydney | UTC+10 | DST +11 |
Tips for scheduling across time zones
Rotate the pain
Alternate recurring times so the same region isn't always on a late-night call.
Record by default
With 3+ time zones a perfect slot rarely exists — record and share notes.
Anchor to UTC
Put UTC in the invite; calendar apps localize it correctly for every attendee.
Protect deep work
Cluster syncs into one overlap window instead of scattering them through the day.
Private by design
Every calculation — timezone conversion, DST, overlap scoring — runs entirely in your browser. Your member list never leaves your device, so the planner works offline and shares nothing with any server. The widest practical overlap for US–Europe–Asia teams is typically the 07:00–09:00 US Eastern window.