Find the best meeting time across timezones

How it works

1. Step 1

   Add people and their cities

   Add 2 to 8 participants and pick each person's city. Their IANA timezone is set automatically.

2. Step 2

   Set each person's working hours

   Choose when each person is reasonably available. Defaults to 9:00–17:00 local time.

3. Step 3

   See the best overlapping meeting times

   Pick a date and the tool ranks that day's slots by the fairest tradeoff across everyone's available hours.

Who this is for

Frequently asked questions

Does this handle daylight saving time?

Yes. Every city uses its IANA timezone, so daylight saving transitions are applied automatically for the dates you're scheduling.

Are times shown in each person's local timezone?

Yes. Every participant's timeline and suggested slot is rendered in their own local time, so you can see exactly what the meeting looks like for each person.

Do I need an account?

No. There's no sign up, no login, and no email required. Open the page and start planning.

Is any data saved?

Your participant setup is saved locally in your own browser so a refresh doesn't wipe it. It never leaves your device and is never sent to a server — clear it any time from your browser's site data.

Can I use this for remote teams?

Yes. Add up to 8 participants with custom names, cities, and working hours, and share the suggested slot with your team.

Ready-made city pairs

Pre-filled planners for the pairs people schedule most, each with the ranked slots already worked out.

• San Francisco ↔ London
• New York ↔ London
• London ↔ Mumbai
• New York ↔ Mumbai
• San Francisco ↔ Singapore
• London ↔ Singapore
• New York ↔ São Paulo
• London ↔ Tokyo
• San Francisco ↔ Sydney
• London ↔ Sydney
• New York ↔ Tokyo
• Mumbai ↔ Singapore

Browse all 48 cities and 253 pairs.

Scheduling guides

• How to run a fair rotating meeting across three or more timezones

  Once a team spans three or more zones, a single fixed time almost always taxes the same person forever. Rotation fixes that — if you do it deliberately.

• What to do when two timezones have no overlapping working hours

  Some pairs simply don't overlap under standard hours. The question stops being 'when' and becomes 'who moves, and how often'.

• Why recurring cross-timezone meetings break twice a year

  Not every country changes clocks, and those that do don't change on the same day. That gap is where recurring meetings quietly break.

• Setting working hours that actually survive a distributed team

  Most scheduling pain isn't arithmetic — it's that nobody has written down when they're actually available.