How do I find a good meeting time across multiple time zones?

Add all participant time zones using the selector above. The grid highlights business hours (9 AM–6 PM) in green for each zone. Look for columns where every row is green — these are your overlap windows. The banner at the top of the grid shows the optimal UTC window automatically.

Does the meeting planner account for daylight saving time?

Yes. Offsets are computed using the JavaScript Intl.DateTimeFormat API with the selected date, which applies IANA timezone rules including historical and future DST transitions. Change the date to see how DST affects your overlap windows — for example, the US switches DST two weeks before the EU, creating a temporary offset shift.

What does ''UTC anchor'' mean in the column headers?

The 24 columns represent UTC hours 0–23 on the selected date. UTC (Coordinated Universal Time) is the universal time reference. Each cell shows what local time that UTC hour corresponds to in a given timezone. This makes it easy to identify a single UTC time to put in a calendar invite that everyone can convert to their local time.

What is the best time for a US–Europe meeting?

The best overlap for New York (ET) and London is typically 2–5 PM ET / 7–10 PM London. For New York and Paris/Berlin (CET), the window is 3–5 PM ET / 9–11 PM CET. If the European team can start slightly early or the US team can stay slightly late, the window expands. Switching to ''flexible hours'' (8 AM–7 PM) can give another 1–2 hours.

What is the best time for a US–Asia Pacific meeting?

US–Asia meetings rarely have a business-hours overlap. New York and Tokyo are 13–14 hours apart depending on DST. The closest workable slot is 8–9 AM Tokyo / 6–7 PM New York (previous evening ET). For US West Coast and Tokyo, a 4–5 PM PT slot maps to 8–9 AM JST the next day — a practical early-morning Tokyo option.

Can I schedule meetings across more than two time zones?

Yes — add as many zones as your team spans. The planner computes overlap across all selected zones simultaneously. With three or more widely distributed zones (e.g., New York, London, Singapore), perfect overlap is rare; the banner shows the best partial-overlap window when no full overlap exists.

Why are some cells marked +1d or −1d?

These badges indicate the local calendar date differs from the date you selected. For example, if you select March 16 and a UTC hour in the middle of the night corresponds to March 17 in Tokyo, the Tokyo cell shows ''+1d''. This helps when booking calendar events — Tokyo participants would schedule the meeting on the following day.

What are IANA timezones and why does the planner use them?

IANA timezones (e.g., America/New_York, Asia/Tokyo) are the industry standard maintained by the Internet Assigned Numbers Authority. They encode the full history of UTC offsets and DST rules for every region. Using IANA identifiers ensures the planner gives the correct offset even for past events and future DST changes, unlike simple UTC offset strings like ''UTC-5'' which don''t capture DST.

How accurate is the planner near daylight saving transitions?

Very accurate. The planner uses the Intl.DateTimeFormat API, which applies IANA timezone data from the browser''s V8 or SpiderMonkey engine — the same engine used by your operating system''s clock. Edge cases like the two-week gap when the US changes DST before the EU (typically in March and November) are handled correctly: selecting a date within that window shows the temporary offset shift.

Why does the best meeting time change when I change the date?

Because UTC offsets change with DST. For example, London (GMT) is UTC+0 in winter but UTC+1 (BST) in summer. New York is UTC-5 in winter and UTC-4 in summer. The difference between New York and London is 5 hours in winter but only 4 hours in summer — opening an extra hour of overlap. The planner recomputes offsets for the exact date you select.

Can I use this for recurring meetings?

Yes, but check a few representative dates across the year to confirm overlap stays consistent — especially if any team location observes DST while others don''t. A recurring Monday slot that works in January may shift by an hour in March when US DST kicks in, and again when EU DST follows two weeks later.

Meeting Planner

Find overlapping work hours across multiple time zones for global team scheduling.

Date

Add Timezone

New York (GMT-4)London (GMT)Tokyo (GMT+9)

◐

No full overlap — best partial: 2/3 zones overlap simultaneously

Darker green columns show maximum overlap. Consider early/late start times for some participants.

TimezoneUTC hour →

New York

GMT-4

London

GMT

Tokyo

GMT+9

12 AM

1 AM

2 AM

3 AM

4 AM

5 AM

6 AM

7 AM

8 AM

9 AM

now10 AM

11 AM

12 PM

1 PM

2 PM

3 PM

4 PM

5 PM

6 PM

7 PM

8 PM

9 PM

10 PM

11 PM

8pm−1d

9pm−1d

10pm−1d

11pm−1d

12am

1am

2am

3am

4am

5am

6am

7am

8am

9am

10am

11am

12pm

1pm

2pm

3pm

4pm

5pm

6pm

7pm

12am

1am

2am

3am

4am

5am

6am

7am

8am

9am

10am

11am

12pm

1pm

2pm

3pm

4pm

5pm

6pm

7pm

8pm

9pm

10pm

11pm

9am

10am

11am

12pm

1pm

2pm

3pm

4pm

5pm

6pm

7pm

8pm

9pm

10pm

11pm

12am+1d

1am+1d

2am+1d

3am+1d

4am+1d

5am+1d

6am+1d

7am+1d

8am+1d

Green = business hours (9 AM – 6 PM)Current UTC hour+1d / −1d = next/previous calendar dayColumn headers = UTC time

Related Tools

World Clock Timezone Converter

How the Meeting Planner Works

The planner uses the browser''s built-in Intl.DateTimeFormat API backed by the IANA Time Zone Database — the same standard used by every major calendar app, operating system, and programming platform. All 24 columns represent UTC hours on the selected date. Each cell converts that UTC instant to the local time in the respective timezone, accounting for the exact UTC offset on that specific date, including all DST rules.

1
Select a date
Pick the date you want to meet. The planner automatically adjusts UTC offsets and DST for every timezone on that specific date.
2
Add your time zones
Add every location where participants are based. The grid supports unlimited zones — from two to a full distributed team across five continents.
3
Read the overlap grid
Each row is a timezone, each column is a UTC hour. Green cells are local business hours (9 AM–6 PM). Columns where all rows are green are your optimal meeting windows.
4
Book the meeting
The banner above the grid surfaces the UTC window where all zones overlap in business hours, or the best partial overlap if none exists.

DST Accuracy & Methodology

Daylight saving time transitions vary by country and year. The United States typically switches in mid-March and early November; most of Europe follows two weeks later. Some regions — Arizona, Iceland, most of Africa, Japan — observe no DST at all. This planner uses IANA timezone identifiers (e.g., America/New_York, Europe/London) rather than raw UTC offset strings, so it correctly reflects the precise offset on any date you select — including the two-week transition window when US and EU clocks are offset by one extra hour.

Best Meeting Times for Common Timezone Combinations

Reference guide for the most common global team pairings (standard time, non-DST period unless noted).

Location Pair	Best Window	Notes
New York + London	2 PM–5 PM ET / 7 PM–10 PM London	Small window. NY afternoon is London evening — tight but workable.
New York + Paris / Berlin	3 PM–5 PM ET / 9 PM–11 PM CET	Even tighter than NY–London due to +1 h difference.
London + Dubai	9 AM–5 PM London / 12 PM–8 PM Dubai	Excellent overlap — nearly a full working day in common.
London + Singapore	9 AM–1 PM London / 5 PM–9 PM SGT	Morning London / evening Singapore. 4-hour window.
New York + Mumbai	No natural overlap	Mumbai is 9.5–10.5 h ahead. Early morning NY = late evening Mumbai.
New York + Tokyo	No natural overlap	14 h difference. One party must meet outside standard hours.
London + Sydney	9 AM–11 AM London (summer) / 6 PM–8 PM AEDT	Very narrow. Best in boreal summer when DST widens the gap less.
Los Angeles + Tokyo	4 PM–5 PM PT / 9 AM–10 AM JST (+1 day)	Late afternoon LA = next-morning Tokyo. One-hour sweet spot.

Windows shift ±1 hour near DST transitions. Use the interactive planner above for exact dates.

Tips for Scheduling Global Team Meetings

→Rotate inconvenient slots fairly. When there''s no overlap, take turns holding the off-hours slot so the same team member isn''t always on a late-night call.
→Always share times in UTC. Calendar invites should specify UTC (or include it alongside local times). This avoids confusion during DST transitions when one party''s offset has already changed.
→Check DST dates twice a year. Build a recurring reminder in March and November (or April/October for the Southern Hemisphere) to verify that recurring meeting slots haven''t drifted by an hour.
→Prefer mid-week slots. Tuesday, Wednesday, and Thursday tend to have better attendance rates for cross-timezone meetings than Monday mornings or Friday afternoons.
→Record and async-follow-up. For teams where overlap is less than 1 hour, record the meeting and share it with team members in difficult time zones so they can catch up asynchronously.

Meeting Planner

Related Tools

How the Meeting Planner Works

DST Accuracy & Methodology

Best Meeting Times for Common Timezone Combinations

Tips for Scheduling Global Team Meetings

Frequently Asked Questions