Xerobit

World Time Meeting Planner: Find Overlapping Hours

Enter your local time and select up to five cities to instantly see the corresponding time in each location. This world time meeting planner marks which hours fall within standard business hours (09:00 to 17:00) so you can spot the best overlap for a call. It runs entirely in your browser using built-in time zone data, and nothing is uploaded anywhere.

Result

  • New York (Eastern)
    09:00

    Business hours

  • London
    14:00

    Business hours

  • Tokyo
    23:00

    After hours

How to use the world time meeting planner

  1. Set Your local hour and Minute using 24-hour format (e.g., 14 for 2 PM).
  2. Choose two to five cities from the dropdown menus. Leave unused slots on (none).
  3. Read the result rows to see the exact time in each selected city right now.
  4. Check the note beside each city: Business hours means the time falls between 09:00 and 17:00 locally.
  5. Adjust the hour up or down until every participant shows business hours for a viable meeting window.

How the time conversion works

The world time meeting planner uses the IANA time zone database built into every modern browser via Intl.DateTimeFormat. When you enter a local hour, the tool constructs a reference timestamp in your first selected zone, then formats that same instant for every other zone you picked.

For example, if you set 09:00 in New York (America/New_York) during standard time (UTC-5), the underlying UTC moment is 14:00. Formatting that UTC instant in London (Europe/London, UTC+0) yields 14:00, and in Tokyo (Asia/Tokyo, UTC+9) yields 23:00. Daylight saving transitions are handled automatically because the IANA identifiers contain the full historical offset rules.

Common offset reference table

This table shows standard (winter) offsets from UTC for popular zones. During daylight saving time, regions that observe it shift one hour forward. Always verify with the planner above, since DST start and end dates differ by country.

Zone identifierCity labelStandard UTC offset
America/New_YorkNew YorkUTC-5
America/ChicagoChicagoUTC-6
America/DenverDenverUTC-7
America/Los_AngelesLos AngelesUTC-8
Europe/LondonLondonUTC+0
Europe/ParisParisUTC+1
Asia/KolkataMumbaiUTC+5:30
Asia/TokyoTokyoUTC+9
Australia/SydneySydneyUTC+10

Note that India uses a half-hour offset. If you need to convert specifically between US zones, tools like the EST time converter or the Central to Eastern time converter handle those pairs directly.

Finding the overlap window

A practical rule for global teams is to aim for a slot where every participant falls between 09:00 and 17:00 local time. With two or three zones this is usually straightforward. With four or more spread across continents, the overlap may shrink to a single hour or disappear entirely.

When no perfect window exists, rotate the inconvenience. Schedule one meeting at a time that favors the Asia-Pacific team, and the next one to favor the Americas. The world time meeting planner makes this easy: just slide the hour input up or down and watch the business-hours markers update live.

Daylight saving pitfalls

Not every region observes daylight saving time, and those that do switch on different dates. The United States changes clocks on the second Sunday in March and the first Sunday in November. The European Union shifts on the last Sunday in March and the last Sunday in October. This creates a two to three week gap twice a year where transatlantic offsets change by an extra hour.

Because this tool relies on the browser's Intl API, it applies the correct offset for whatever date the system clock holds. If you are planning a recurring meeting months ahead, double-check the result close to the actual date to confirm no DST transition has moved the window.

Why use IANA zone names

Abbreviations like EST, CST, or BST are ambiguous. EST can mean Eastern Standard Time in North America or Eastern Standard Time in Australia. IANA identifiers such as America/New_York or Australia/Sydney point to a specific geographic location with a complete history of offset changes, eliminating guesswork.

Using these identifiers also ensures that half-hour and quarter-hour offsets, like India's UTC+5:30 or Nepal's UTC+5:45, are computed correctly without manual adjustment. For deeper conversions involving Unix epochs, the timestamp converter is a useful companion.

Worked examples

Each result below was produced by the same code the tool runs, so you can check your own numbers against them.

ExampleInputResult
NYC, London, Tokyo at 9 AMYour local hour (0-23): 9; Minute (0-59): 0; City / Zone 1: America/New_York; City / Zone 2: Europe/London; City / Zone 3: Asia/TokyoNew York (Eastern): 09:00; London: 14:00; Tokyo: 23:00
US coast-to-coast at 1 PM EasternYour local hour (0-23): 13; Minute (0-59): 0; City / Zone 1: America/New_York; City / Zone 2: America/Chicago; City / Zone 3: America/Denver; City / Zone 4: America/Los_AngelesNew York (Eastern): 13:00; Chicago (Central): 12:00; Denver (Mountain): 11:00; Los Angeles (Pacific): 10:00
Europe and India at noon Paris timeYour local hour (0-23): 12; Minute (0-59): 0; City / Zone 1: Europe/Paris; City / Zone 2: Europe/London; City / Zone 3: Asia/KolkataParis / Berlin / Rome: 12:00; London: 11:00; Mumbai / Delhi (India): 16:30

FAQ

Does this world time meeting planner account for daylight saving time?

Yes. It uses IANA time zone identifiers and your browser's built-in Intl API, which automatically apply the correct daylight saving offset for the current date.

Can I compare more than five cities?

The interface supports up to five zones at once to keep the display readable. For larger groups, run the planner twice with different combinations and cross-reference the results.

What counts as business hours in the results?

Any local time from 09:00 through 17:00 is marked as business hours. Times outside that range are labeled after hours.

Is my data sent to a server?

No. All calculations happen locally in your browser. No network requests are made and no information is stored.

Why does the tool use city names instead of abbreviations like EST or PST?

Time zone abbreviations are often ambiguous and do not encode daylight saving rules. IANA city-based identifiers like America/New_York are precise and universally understood by software.

How do I handle half-hour offsets like India or Nepal?

Select the appropriate zone, such as Asia/Kolkata for India. The planner computes fractional offsets automatically, so you will see times like 13:45 when applicable.

What if there is no overlapping business hour for all participants?

Try shifting the meeting earlier or later to find a compromise where most participants are within business hours, or consider splitting the meeting into two sessions for different regions.