Find a meeting time across time zones in seconds: add 2 to 6 cities, pick a date, and the planner shows every participant's local hours side by side. Blue cells mark working hours, lighter cells mark waking hours, and a summary lists the windows where the whole group can realistically meet.
The grid shows one full day, hour by hour, in the first participant's time zone (by default, yours). Each row translates those same 24 moments into another city's local clock. A cell shaded solid blue means that person is inside normal working hours, 9:00 to 17:59. A light blue cell means they are awake but outside office hours, 7:00 to 8:59 or 18:00 to 21:59. A gray cell means they would normally be asleep.
The planner does the comparison for you. A best time to meet card shows the single strongest window, the longest stretch of hours where all participants are in working hours (labeled Ideal). If no such hour exists, it falls back to the longest stretch where everyone is at least awake (labeled Workable), and every other qualifying window is listed below the grid. If even that fails, it says so plainly rather than pretending a 3:00 call is fine for someone. Tap any hour column in the grid to see that exact moment spelled out for every city.
Most scheduling mistakes come from treating time zones as fixed offsets. They are not. Daylight saving time starts and ends on different dates in different places: the US springs forward in early March, Europe in late March, and Australia moves in the opposite direction because its seasons are reversed. For a few weeks each year the usual gap between New York and London is 4 hours instead of 5, and a recurring meeting that was fine in February suddenly lands during someone's commute.
The international date line adds a second trap: when it is Thursday afternoon in San Francisco it is already Friday morning in Sydney, so "let's meet Friday" means two different days depending on who says it. Half hour offsets (India at UTC+5:30, for example) break mental math too. This planner sidesteps all of it by computing each cell from a real instant in time using each city's official IANA time zone rules, so DST switches, date changes, and odd offsets are handled for the exact date you pick. When a participant's time lands on a different calendar day than the reference city, the grid shows a small weekday label inside that cell so nobody books "Friday" on someone else's Saturday.
For a one-off call, someone taking an 8:00 or a 20:00 slot is a small favor. For a weekly meeting, always giving the bad slot to the same region quietly burns people out. If your group spans more than about 8 hours of offset, rotate the meeting time: alternate between a time that suits the Americas and one that suits Asia Pacific, so the early morning or late evening burden moves around instead of becoming one office's permanent tax.
Two more habits help. First, keep the live meeting short and move status updates into a shared document that people read in their own morning. Second, record every session, so skipping an occurrence at 22:00 local is a real option rather than a career risk. Our guide on scheduling meetings across time zones covers rotation patterns and async alternatives in more depth.
The planner tells you when a meeting is theoretically possible. It cannot tell you that Priya has a dentist appointment or that half the Berlin office is at an offsite. Working hours are a model; calendars are reality. So treat the overlap window as a shortlist, not a decision.
The reliable next step is a quick availability poll: propose a few slots from the Ideal or Workable window, share one link, and let everyone mark when they are actually free, each person seeing the times in their own time zone. You get a single grid showing the slot that works for the most people, without a reply-all thread. Once the time is set, our add to calendar link generator turns it into a one-click calendar entry, and if you are wondering whether the meeting is worth 6 people's time at all, the meeting cost calculator will tell you.
Late morning on the US East Coast is usually best. 11:00 in New York is 16:00 in London and 17:00 in Berlin or Paris, so everyone is inside or close to normal working hours. If the group includes the US West Coast, push to 12:00 or 13:00 Eastern (9:00 or 10:00 Pacific), which still lands before 19:00 in Central Europe.
There is no hour where both sides are in standard office hours, so the fairest slots sit at the edges. 8:00 to 10:00 on the US East Coast is 17:30 to 19:30 in India (18:30 to 20:30 when the US is on standard time), which is early for one side and late for the other but keeps everyone awake. For US West Coast and India, early Pacific morning (7:00 to 8:00) maps to Indian evening (19:30 to 20:30 during daylight saving time).
Yes. Every cell is computed from a real moment in time for the exact date you pick, using each city's IANA time zone rules, not a fixed offset. Because the US, Europe, and the southern hemisphere change their clocks on different dates, the overlap between two cities can shift by an hour for a few weeks each year, and the planner reflects that automatically.
The planner treats 9:00 to 17:59 local time as working hours (the best case), and 7:00 to 8:59 plus 18:00 to 21:59 as awake but outside office hours (acceptable for occasional meetings). Anything from 22:00 to 6:59 is treated as sleep time and should not be asked of anyone on a regular basis.
Groups spanning the Americas, Europe, and East Asia often have no hour where everyone is awake. In that case, rotate the meeting time so the painful slot moves between regions each occurrence, record the meeting for whoever misses it, and move status updates to async documents so the live call is short. An availability poll helps you find the least bad option because people can mark early or late slots they are genuinely willing to take.
The 24 columns show one full day in the reference city, which defaults to your own time zone. Use the 'Times shown in' selector above the grid to switch the reference to any city you have added. Every row shows what each of those same moments looks like on that participant's local clock, and a small weekday label appears inside a cell when that time lands on the previous or next calendar day.
Create a poll with your best slots, share one link, and see everyone's real availability in a single grid. Free, no sign-up needed to respond.