Timezone Meeting Planner
Pick the cities on your call, set what counts as a workday, and see every hour of the day rendered in each local time — with the slots that fall inside working hours for everyone highlighted, and one suggested time ready to paste into an invite.
Cities and working hours
Compare 2–5 cities. Your own timezone is added automatically.
Overlap for that date
Pick a date and working hours to see the overlap.
Announce the meeting with Moda
Turn the agreed time into a designed invite, agenda slide, or team announcement on a real canvas.
Try Moda free →How the overlap grid works
The grid shows one full day anchored to midnight in the first city on your list — usually 24 hourly columns, but 23 or 25 on that city’s daylight-saving switch dates, because those days really are shorter or longer. Each row renders the same instants in another city’s local time, so a single column is always one real moment — 9 AM in New York, 2 PM in London, 7:30 PM in Mumbai. A column turns green when it lands inside the working hours you set for every city at once, and the suggested time is the green slot closest to mid-morning for the first city, because 10 AM survives calendars better than 8 AM or 4 PM.
Daylight saving time is why you should trust a tool, not your memory
The gap between two cities is not a constant. New York and London are usually 5 hours apart, but for a few weeks each spring and autumn they are 4, because the US and the EU change their clocks on different dates — and India, China, and Japan never change at all. A recurring call that worked all winter can silently land outside someone’s workday in March. This planner reads the offset for the specific date you pick from the browser’s own timezone database, so a slot that is green for March 20 has already accounted for whichever cities have switched.
Half-hour and quarter-hour timezones
Not every timezone sits on a whole hour. India runs at UTC+5:30, Iran at UTC+3:30, and Nepal at UTC+5:45 — so a 9 AM start in London is 2:30 PM in Mumbai, never 2 PM or 3 PM. The grid keeps the minutes visible instead of rounding, which matters when a 30-minute call is meant to end exactly at someone’s 6 PM.
When there is no overlap
San Francisco, Berlin, and Sydney share no common 9-to-5 hour on any date — the planet does not bend that far. When no column turns green, the honest options are to widen the workday bounds (many distributed teams treat 8 AM–6 PM as meetable), rotate who takes the bad slot from meeting to meeting, or split into two sessions and record one. The grid makes the least-bad slot easy to spot: look for the column where the out-of-hours city is closest to its morning or evening edge rather than the middle of its night.
Frequently asked questions
Which timezones can I add?
Any IANA timezone your browser knows — roughly 400 of them, covering every city-level zone like America/New_York or Asia/Kolkata. The list comes from the browser’s own Intl API, so it stays current with timezone-rule changes without this page shipping its own database.
Does the planner account for daylight saving time?
Yes. Local times are computed for the exact date you pick using the browser’s timezone rules, so DST transitions — including the weeks where the US has switched but Europe has not — are reflected automatically. Re-check recurring meetings around March/April and October/November, when offsets between cities shift.
How is the suggested meeting time chosen?
From the hours that fall inside working hours for every city, the planner picks the one closest to 10 AM in the first city on your list. If a different slot suits you better, every green column is equally valid — the suggestion is a starting point, not a rule.
Why does a time slot show tomorrow’s date for some cities?
A late-afternoon slot in the Americas is already the next calendar day in Asia and Australia. Hover any cell to see its local date; when you send the invite, calendar apps handle the day rollover automatically as long as everyone’s calendar knows their timezone.
Can I plan a meeting for more than five cities?
The grid caps at five because past that point a full overlap almost never exists and the grid stops being readable. For larger groups, plan around the three or four anchor regions and let outliers join the nearest edge — or alternate the time between two picks so the burden rotates.