Time Zone Meeting Planner

Time zone meeting planner: compare times across cities and find the best slot for every attendee. Free online calculator, runs in your browser, no signup.

Find a meeting time

Pick a date and up to 5 cities. The planner finds the longest window when all cities are inside their local working hours (9:00–17:00 by default).

Times use the IANA time-zone database and your browser's Intl implementation. "Best window" means the longest contiguous overlap of local working hours across the selected cities.

Updates automatically as you type.

Calculated in your browser; your inputs are not sent to us. Privacy

Results will appear here.
Calculation details
Every figure above is calculated locally in your browser from the assumptions shown. No inputs are sent anywhere. See the methodology section below for how this tool works.
Use this resultShare the current inputs, or ask ChatGPT to explain the calculation in context.
Ask an AI to explain this result
Share this result

Date and time results depend on your browser time-zone data and selected inputs. Time-zone laws can change; verify critical schedules with participants.

This tool runs in your browser. Your calculator inputs and results are never transmitted to us or to ad/affiliate partners. Ads and sponsored links may set third-party cookies to serve and measure them, but they never receive your calculation values. If you explicitly save a scenario, its permitted fields stay in local browser storage until you clear them. See our Privacy Policy.

Use this result

Share the current inputs or ask ChatGPT to explain the calculation in context.

More options
Report a calculation issue
Direct answer

What does this calculator estimate?

Time zone meeting planner: compare times across cities and find the best slot for every attendee. Free online calculator, runs in your browser, no signup.

Hourly probe times for Mumbai Dubai and London meeting planner
Best slot: 09:00-11:30 UTC for Mumbai, Dubai, London.
Transparent methodology

How this calculator works

Sources

Frequently asked questions

What is a time zone meeting planner?

A browser-based tool that helps you find overlapping meeting times across multiple time zones without needing to create an account.

Do I need to sign up or install anything to use it?

No, this time zone meeting planner runs entirely in your browser with no signup, no downloads, and no data stored on any server.

How does the time zone meeting planner handle different time zones?

It automatically detects your local time zone and lets you add participants' zones so you can instantly see shared availability windows.

Related tools

Date Difference CalculatorBusiness Days CalculatorHours and Minutes CalculatorTime to Decimal CalculatorWorld ClockCountdown TimerTime Zone ConverterBPM to MS CalculatorTime Duration Calculator

Cite this tool

BoringToolsKit. “Time Zone Meeting Planner.” boringtoolskit.com/time-zone-meeting-planner/. Free to reference in articles, syllabi, and answer posts with a link.

Privacy: Inputs and results stay in this browser. Any future sponsored recommendation or advertisement will be clearly labeled and kept separate from the calculation.

Worked example: Mumbai, Dubai, London

Set the date, keep the default 9-17 window, and pick Mumbai, Dubai, and London. Offsets on a standard winter date are UTC+5:30, UTC+4, and UTC+0. Mumbai's 9:00-17:00 workday is 03:30-11:30 UTC, Dubai's 9:00-17:00 is 05:00-13:00 UTC, and London's is 09:00-17:00 UTC.

The calculator probes each full UTC hour and keeps only the hours where all three cities sit inside 09:00-17:00 local. At 09:00 UTC the local times are 14:30 Mumbai, 13:00 Dubai, 09:00 London: all pass. At 10:00 UTC they are 15:30, 14:00, 10:00: all pass. At 11:00 UTC they are 16:30, 15:00, 11:00: all pass. At 12:00 UTC Mumbai hits 17:30, outside the window, so the run stops. The longest streak is 3 consecutive hourly probes, 09:00-11:30 UTC, which the tool reports as the best slot: 14:30-17:30 Mumbai, 13:00-16:00 Dubai, 09:00-12:00 London.

Where the hour-by-hour model breaks down

The engine samples on whole hours from 12:00 UTC on the chosen date, so a 30-minute-offset city can lose a slot that really exists. In the Mumbai example above, 11:30-12:00 UTC is inside the window for all three cities, but no probe lands there and it goes unreported. With Adelaide (UTC+9:30) or Delhi in the mix, treat the answer as good to plus or minus 30 minutes and check the edge yourself.

The scan covers 48 hourly probes, so it sees up to 24 hours past local midnight, but it cannot carry a run across the day boundary into a second date, and the day-offset comparison wraps modulo 28 days rather than handling month lengths. A 24-hour window (0-24) ignores the input start hour by design. DST is the other trap: zones are evaluated at their offset on the meeting date, so a slot found for a March date near a US-EU transition week can shift by an hour in the following weeks.