Compare up to six time zones hour by hour and find the slots that fall inside everyone's working day.
The Meeting Time Planner lays out a full day, hour by hour, across two to six time zones so you can see at a glance when a call lands inside everyone's working day. Each cell shows the local time in that zone and is colored green when it falls inside the working hours you set (9:00 to 17:00 by default), amber when it is within two hours of the start or end, and red when it is the middle of the night or a weekend. Rows where every zone is green are highlighted, and the best windows are listed above the table, falling back to the least-bad hours when no perfect overlap exists, which is common for New York, London, India, and Sydney together. The setup is stored in the page address so you can send the plan to the other participants.
Every zone is an IANA identifier such as Asia/Kolkata, and all offsets come from the browser's time zone database through Intl.DateTimeFormat rather than a fixed table, so daylight-saving rules for the chosen date are applied automatically. For each of the 24 hours of the chosen date in the first zone, the page converts that wall-clock time to an instant by guessing UTC, subtracting the zone's offset at the guess, and re-checking once so clock-change days resolve correctly. That instant is formatted in each other zone to get its local hour, minute, and weekday. A cell is 'in hours' when the local time is at or after the start hour and before the end hour on a weekday, 'edge' when it is within two hours outside that range, and 'off' otherwise. Each row scores 2 points per in-hours zone and 1 per edge zone; the best windows are the runs of consecutive rows sharing the highest score.
Because their working days do not overlap at all. When it is 9:00 in New York it is already 19:00 in Sydney (or 23:00 in the southern summer), and when Sydney starts at 9:00 it is 18:00 or 19:00 the previous evening in New York. The planner therefore lists the least-bad hours: typically 7:00 to 8:00 New York, which is noon in London, 17:30 in India, and 21:00 to 23:00 in Sydney, with two zones in hours and two on the edge.
Each cell shows the exact local time including minutes, so 9:00 in New York appears as 18:30 in Kolkata during US summer time and 19:30 in winter. The in-hours test uses the full local time, so 17:30 is treated as 'edge' when the working day ends at 17:00. Nepal (UTC+5:45) and other 45-minute zones work the same way.
They flag cells where the local date differs from the date in the first zone. A meeting at 18:00 in Los Angeles is 11:00 the next day in Tokyo, so the Tokyo cell shows +1. Always check these before sending an invitation across the Pacific, because 'Tuesday 6 pm' in one city can be 'Wednesday 11 am' in another.
Yes. The conversion is done for the specific date you pick, using the browser's time zone rules, so a plan for late March correctly reflects that the United States has already moved its clocks while Europe has not, and a plan for October reflects Australia starting summer time while the northern hemisphere ends it. The 'Zone offsets' line under the table shows the offset each zone is using on that date.
Life in Weeks · Age Calculator · Days Between Dates · Date Calculator · Countdown to a Date · Online Timer · Stopwatch · Pomodoro Timer · World Clock · Time Zone Converter · UTC Time Converter · New York to London Time
Browse all Time & Date Tools, or go back to every free tool on HeroYears.