Meeting Planner
Find a time that works for everyone. This page shows the best meeting windows for common city pairs — hours where both sides are within standard working hours (9 AM–6 PM local time). All offsets are computed live from the IANA tz database and reflect the actual DST state for today.
For any specific cities or a custom date, use the interactive planner — drag the time cursor to see the overlap window update in real time.
Open the live planner
Add any cities, pick a date, drag the cursor — share the link with your team
Working-Hour Overlap Windows
New York → London
London is 5h ahead of New York
Best window: 9am–1pm EST = 2pm–6pm GMT
Los Angeles → Tokyo
Tokyo is 16h ahead of Los Angeles
Best window: 5pm–6pm PST = 9am–10am JST
New York → Kolkata
Kolkata is 9.5h ahead of New York
No standard 9 AM–6 PM overlap. Consider async or early/late calls.
Los Angeles → Kolkata
Kolkata is 12.5h ahead of Los Angeles
No standard 9 AM–6 PM overlap. Consider async or early/late calls.
New York → Paris
Paris is 6h ahead of New York
Best window: 9am–12pm EST = 3pm–6pm CET
New York → Los Angeles
Los Angeles is 3h behind of New York
Best window: 12pm–6pm EST = 9am–3pm PST
New York → Chicago
Chicago is 1h behind of New York
Best window: 10am–6pm EST = 9am–5pm CST
Tips for Scheduling Across Time Zones
- ·Pick times that are within business hours for everyone — even if it's early or late, 9 AM–6 PM coverage is the practical benchmark.
- ·Account for DST transition weeks: the offset between two cities can shift by 1 hour during the 2–3 weeks when one region has switched and the other hasn't.
- ·Export an .ics calendar invite — attendees see the event in their local time automatically, reducing manual conversion errors.
- ·For recurring meetings with no overlap, rotate the inconvenient slot so one team isn't always the one taking the off-hours call.
- ·When scheduling internationally, confirm the date format (MM/DD vs DD/MM) and whether AM/PM or 24-hour time is expected.
Related Guides
- How TimezoneCast handles DST accuracy →Why offset-based conversion fails during transition weeks — and how IANA data fixes it.
- World Clock — current time in 27 cities →Check what time it is right now across every major business region.
- Time Zone Converter — all 50 conversion pages →Browse abbreviation pairs, city pairs, and specific-time conversions.
Browse City-to-City Converters
- New York → London
- London → New York
- Los Angeles → Tokyo
- Tokyo → Los Angeles
- Berlin → New York
- New York → Berlin
- San Francisco → London
- London → San Francisco
- New York → Los Angeles
- Los Angeles → New York
- Chicago → London
- London → Chicago
- Toronto → London
- London → Toronto
- Sydney → New York
- New York → Sydney
- Singapore → London
- London → Singapore
- Dubai → London
- London → Dubai
Frequently Asked Questions
- What is the best time to schedule a meeting across time zones?
- Aim for a window where all participants are within standard working hours (9 AM–6 PM local time). Use the overlap windows below as a starting point, then pick the specific time that works best for each team.
- How do I avoid scheduling mistakes during daylight saving time?
- Always use a tool that resolves the actual UTC offset for the specific date, not a fixed offset. TimezoneCast uses IANA timezone data so DST transitions are accounted for automatically.
- What if there is no overlap between working hours?
- When there is no 9 AM–6 PM overlap, consider early morning on the west side or late afternoon on the east side. Async communication (recorded video, Loom, written summaries) is often more sustainable than forcing off-hours calls.
- Can I share a specific meeting time with my team?
- Yes. Open the TimezoneCast planner, add all cities, move the time cursor to your preferred slot, then use the Share button. The link encodes your cities and time — anyone who opens it sees exactly your setup in their local zone.