Meeting Time Zone Planner
Add everyone, see their working hours side by side, and get the best — and fairest — time to meet. Scored, explained, and ready to paste into an invite.
Meeting details
Who’s in the meeting?
Names are optional. Working hours are per person.
Best meeting times
Everyone’s day, side by side
Each column is the same moment in time. Tap any cell to move the meeting.
Fair rotation for your recurring meeting
Nobody should take the 6am call every single week.
Who carries the load
Meeting Time Zone Planner by 101planners.com · time zone and daylight saving data from your browser’s IANA database
This free meeting time zone planner finds the best — and fairest — time to meet across multiple time zones. Add everyone by city or country, set each person’s working hours, and the planner lines up all their local times on one synchronised timeline, scores every possible slot, and tells you which one causes the least inconvenience for the group. No sign-up, no app, nothing to install.
Most tools stop at showing you a colour-coded grid and leave you to work out the answer. This one answers the actual question: when should we meet? — and when there is no good answer, it finds the fairest compromise and explains why.
One tool, many names
People search for this in a dozen different ways and mean exactly the same thing. If you came looking for a time zone meeting planner, a world meeting planner, a world time clock meeting planner, a global meeting time planner, an overseas meeting planner, an international meeting scheduler or simply a time zone scheduler — and whether you spell it time zone or timezone — you are in the right place. They all describe the same job: picking one moment that several people in different places can actually attend.
Find the Best Meeting Time Across Time Zones
Scheduling across time zones goes wrong in three predictable ways: someone does the arithmetic in their head and gets it backwards, someone forgets that daylight saving does not change on the same date everywhere, and someone books a slot that is technically “business hours” for four people and 10:00 PM for the fifth.
The time zone meeting planner above removes all three. Here is how to use it in about ten seconds:
- Add your people. Your own time zone is detected automatically. Add the rest by city, country or IANA time zone — “Mumbai”, “Australia/Sydney” and “UTC+05:30” all work.
- Set working hours. Everyone defaults to 9:00 AM–5:00 PM. Change any of them individually — including split hours for a lunch break, and shifts that cross midnight.
- Pick the date and duration. The date matters: time differences shift with daylight saving, so a meeting in March may not sit where a meeting in July does.
- Read the recommendations. Three ranked options, each with a fairness score out of 100 and a plain-English explanation of who is being asked to stretch.
- Copy or export. One click for a paste-ready message, a Google Calendar or Outlook event, or a downloadable
.icsfile.
What the fairness score actually measures
Every recommended time gets a score out of 100. It is not an average — averages hide the person being sacrificed. The score deliberately protects whoever would suffer most, so an option where everyone is mildly inconvenienced beats one where three people are perfectly comfortable and the fourth is joining at 5:30 AM.
| Local time falls… | Comfort |
|---|---|
| Inside their stated working hours | 100 |
| Within an hour either side | ~83 |
| Two hours outside — early start or evening call | ~66 |
| Three to four hours outside | ~50 to 33 |
| Inside their sleeping hours | 0 to 12 |
The curve is continuous rather than banded, which matters more than it sounds. When a group is spread so widely that somebody is always asleep, banded scoring makes every slot in the day tie on the same number and the ranking becomes useless. A smooth curve still knows that ten minutes past someone’s bedtime is meaningfully better than 3:00 AM.
World Clock Meeting Planner
The timeline is a world clock meeting planner in the classic sense: one row per person, twenty-four columns, and every column is the same actual moment in time. Moving one column to the right advances everybody by exactly one hour, whatever their offset. Half-hour and quarter-hour zones — India at UTC+5:30, Nepal at UTC+5:45, Adelaide at UTC+9:30, the Chatham Islands at UTC+12:45 — sit exactly where they should, which is where a lot of simpler world clock tools quietly round to the nearest hour and go wrong.
Colour tells you the state of each hour for each person, and because colour alone is not accessible, each state also carries a distinct texture and label:
- Working hours — inside the hours that person told you they work.
- Just outside — within about two hours. Reasonable to ask.
- Early or late — awake, but this is a favour.
- Asleep — do not book this.
- Public holiday — flagged separately, because a perfectly timed meeting on someone’s national holiday is still a meeting nobody attends.
Current UTC offsets for major business hubs
A quick reference for the cities that turn up most often in international meeting planning. Note how several of them move by an hour twice a year and several never move at all.
| City | January (UTC) | July (UTC) | Observes DST? |
|---|---|---|---|
| Los Angeles | −8 | −7 | Yes |
| New York | −5 | −4 | Yes |
| São Paulo | −3 | −3 | No — abolished in 2019 |
| London | 0 | +1 | Yes |
| Berlin, Paris, Madrid | +1 | +2 | Yes |
| Lagos | +1 | +1 | No |
| Tel Aviv | +2 | +3 | Yes |
| Dubai | +4 | +4 | No |
| Mumbai, Delhi, Bengaluru | +5:30 | +5:30 | No |
| Singapore, Shanghai, Hong Kong | +8 | +8 | No |
| Tokyo, Seoul | +9 | +9 | No |
| Sydney, Melbourne | +11 | +10 | Yes (southern summer) |
| Brisbane, Perth | +10 / +8 | +10 / +8 | No |
| Auckland | +13 | +12 | Yes (southern summer) |
Find Overlapping Working Hours
The single most useful thing a meeting planner can show you is the overlap: the window where everybody is genuinely at work at the same moment. Because working hours are set per person rather than assumed, the overlap the planner finds is the real one, not a 9-to-5 approximation.
Some common team shapes and the overlap they actually have, assuming a standard 9:00 AM–5:00 PM day in each place during northern summer:
| Team | Shared working hours | What it means in practice |
|---|---|---|
| London + New York | 2:00 PM–5:00 PM London / 9:00 AM–12:00 PM New York | Three comfortable hours. The easiest transatlantic pairing there is. |
| London + Mumbai | 9:00 AM–12:30 PM London / 1:30 PM–5:00 PM Mumbai | Three and a half hours, London mornings. |
| London + Singapore | 9:00 AM–10:00 AM London / 4:00 PM–5:00 PM Singapore | One hour. Tight, but it exists. |
| New York + Berlin | 9:00 AM–11:00 AM New York / 3:00 PM–5:00 PM Berlin | Two hours — and for three weeks each March it briefly grows to three, while the US has changed its clocks and Europe has not. |
| New York + Singapore | None | Somebody starts early or finishes late. There is no honest overlap. |
| San Francisco + Sydney | About one hour, on different days | 4:00 PM Thursday in San Francisco is 9:00 AM Friday in Sydney. The exact slot slides by an hour or two through the year, because the two hemispheres change their clocks in opposite directions. |
| Tel Aviv + New York | 4:00 PM–5:00 PM Tel Aviv / 9:00 AM–10:00 AM New York | One clean hour, and it is a reliable one. |
| London + New York + Singapore | None | Three-continent teams almost never have a true overlap. This is where fairness scoring earns its keep. |
Working hours are a per-person setting, not a per-city one
Two colleagues in the same city do not necessarily have the same availability. One starts at 8:00 AM and leaves at 4:00 PM for the school run; the other rolls in at 10:00 AM and works until 7:00 PM. A planner that treats “London” as a single availability block will confidently recommend a time that only one of them can make.
That is why this tool is participant-first rather than location-first. You add Sarah — London — works 8:00–4:00, not just London. You can also give one person split hours (9:00–12:00 and 1:00–5:00, protecting a lunch break) or hours that cross midnight for night-shift and on-call staff. Sleeping hours are derived from whatever you set, so a person working 10:00 PM–6:00 AM is correctly treated as asleep during the middle of their local afternoon.
Find the Fairest Time for Global Meetings
Here is the problem most global meeting planners refuse to engage with. Once your team spans more than about eight hours of longitude, there is no time that suits everyone. A tool that only visualises overlap has nothing useful to say at exactly the moment you most need help.
When there is no shared working window, this planner switches into a different mode. Instead of an empty result it gives you a ranked set of genuinely different compromises:
- Fairest overall — the option that minimises the worst individual experience.
- Earliest reasonable — the earliest slot where nobody is being asked to attend from bed.
- Latest reasonable — the same, at the other end of the day.
- Better for a specific region or person — deliberately tilted, so you can decide consciously who takes the hit rather than discovering it afterwards.
Each option comes with an explanation rather than a bare number: “There is no shared working window. This option avoids overnight calls and spreads the inconvenience as evenly as the map allows.” You should never be asked to trust an unexplained algorithmic score about your own team.
Recurring meetings: stop making the same team wake up early
This is the part that matters over months rather than minutes. If your weekly global stand-up has no convenient time, optimising each meeting independently produces the same answer every week — and the same team pays for it every week. Over a year that is fifty early mornings for one office and zero for another.
Set the meeting to repeat and the planner optimises the series instead of the individual meeting. It rotates the slot so the inconvenience moves around the group, and it keeps a running ledger of who has carried how much, so the rotation is genuinely balanced rather than just varied.
| Meeting | Suits | Who stretches |
|---|---|---|
| Week 1 | Americas + Europe | Asia takes a late evening |
| Week 2 | Europe + Asia | Americas take an early morning |
| Week 3 | Best available compromise | Everyone stretches slightly |
| Week 4 | Pattern repeats | — |
Importantly, if your group does have one slot that suits everybody every time, the planner says so and keeps the time fixed. Rotating for the sake of rotating just makes a meeting harder to remember.
International Meeting Planner for Remote Teams
A few habits that make an international meeting planner unnecessary most of the time. Worth adopting alongside the tool, because the best meeting scheduler for time zones is a team that writes times unambiguously in the first place.
Write the time zone every single time
“Let’s meet at 3.” is the single most expensive sentence in remote work. Always write 3:00 PM CET (2:00 PM UTC). Prefer unambiguous labels: “ET” rather than “EST” (which is wrong for eight months of the year), and UTC as the anchor when the audience is genuinely global.
Name the date in every time zone when it differs
A 9:00 PM Tuesday call in New York is 11:00 AM Wednesday in Tokyo. Sending “Tuesday at 9” to a Tokyo colleague means they will show up on the wrong day, and it will be nobody’s fault but the sender’s. The planner labels any participant whose local date differs with a clear +1 day or −1 day.
Book from a shared anchor, not from your own clock
Send the meeting as a calendar invite with a real time zone attached, or as an .ics file, rather than as text. Calendar software then does the conversion for each attendee and gets daylight saving right automatically.
Protect a genuine core-hours window
Distributed teams that work well tend to agree a narrow band of overlapping hours — often only two or three — and keep it sacred for anything synchronous. Everything else moves to writing. If your team spans twelve hours or more, accept that a single all-hands time does not exist and rotate deliberately.
Check public holidays before you send the invite
A colleague’s national holiday is invisible from another country. Late November means nothing in Europe and everything in the United States; early May is a public holiday across most of Europe and an ordinary Tuesday in the US. The planner flags public holidays for each participant’s country automatically, including moveable feasts such as Easter and holidays that follow the Hebrew and Islamic calendars.
Daylight Saving Time: the two weeks that break every recurring meeting
This is the failure mode that catches experienced people, because the tool they used was technically correct and still gave them a wrong answer for a fortnight.
The time difference between two cities is not a constant. It changes whenever either of them starts or ends daylight saving — and they almost never do it on the same date. New York and London are normally five hours apart. But in 2026:
| Period | New York | London | Difference |
|---|---|---|---|
| 1 Jan – 7 Mar 2026 | UTC−5 | UTC+0 | 5 hours |
| 8 Mar – 28 Mar 2026 | UTC−4 | UTC+0 | 4 hours |
| 29 Mar – 24 Oct 2026 | UTC−4 | UTC+1 | 5 hours |
| 25 Oct – 31 Oct 2026 | UTC−4 | UTC+0 | 4 hours |
| 1 Nov – 31 Dec 2026 | UTC−5 | UTC+0 | 5 hours |
For those three weeks in March and one week in October, a recurring 9:00 AM New York meeting is 1:00 PM in London, not 2:00 PM. Every “always 5 hours” mental model silently produces a meeting an hour out. The planner works from live IANA time zone data for the specific date you choose, so it never makes this mistake — and it warns you when a clock change is coming that will move your meeting.
Daylight saving change dates, 2026 and 2027
| Region | 2026 starts | 2026 ends | 2027 starts | 2027 ends |
|---|---|---|---|---|
| United States & Canada | Sun 8 March | Sun 1 November | Sun 14 March | Sun 7 November |
| United Kingdom & European Union | Sun 29 March | Sun 25 October | Sun 28 March | Sun 31 October |
| Israel | Fri 27 March | Sun 25 October | Fri 26 March | Sun 31 October |
| Australia (NSW, VIC, SA, ACT, TAS) | Sun 4 October | Sun 5 April | Sun 3 October | Sun 4 April |
| New Zealand | Sun 27 September | Sun 5 April | Sun 26 September | Sun 4 April |
| Chile | Sun 6 September | Sun 5 April | Sun 5 September | Sun 4 April |
India, China, Japan, Singapore, most of Africa, Brazil, the Gulf states, Queensland, Western Australia, Arizona and Hawaii do not observe daylight saving at all. If your team includes any of them, the gap to your DST-observing colleagues moves twice a year even though nothing changed on their end.
How to Schedule Meetings Across Multiple Time Zones
If you would rather schedule a meeting across time zones by hand — or you just want to understand what the tool is doing — here is the method in full:
- Convert everything to UTC first. UTC never changes, so it is the only safe common language. Work out the meeting in UTC, then convert outward to each participant.
- Use the actual date, not “usually”. Look up offsets for the specific date of the meeting, because daylight saving may have moved one participant and not another.
- Map each person’s working window onto UTC. A 9:00 AM–5:00 PM day in Singapore is 01:00–09:00 UTC; in New York during summer it is 13:00–21:00 UTC. Now the overlap — or the absence of one — is obvious.
- Find the intersection. If one exists, take it. If not, decide who stretches, and write down that you decided.
- Check the calendar date for everyone. Anything after roughly 19:00 UTC is already tomorrow in Asia-Pacific.
- Send a calendar invite, not a sentence. Let each attendee’s software do the final conversion.
- For recurring meetings, diarise the DST dates. Or rotate the slot, so no single office absorbs the whole cost.
The planner above does all seven steps, but the reasoning is worth understanding — particularly step two, which is where almost every manual mistake originates.
Rough guide: which hours suit which pairs of regions
| Regions involved | Usual best window (UTC) | Notes |
|---|---|---|
| Europe + Asia | 08:00 – 11:00 | European morning, Asian late afternoon. |
| Europe + Americas | 14:00 – 17:00 | European afternoon, American morning. The comfortable one. |
| Americas + Asia-Pacific | 21:00 – 00:00 | American evening, next-day Asian morning. Someone is out of hours. |
| Europe + Australia / NZ | 07:00 – 09:00 | Very early Europe, late afternoon Australia. |
| All three: Americas, Europe, Asia | 13:00 – 15:00 | No true overlap. Europe is comfortable; Americas start early; Asia stays late. Rotate this one. |
Time Zone Scheduler for Conference Calls, Webinars and Events
Not everything you schedule is a meeting. The same planner doubles as a world clock conference planner for a multi-region conference call, as a time zone event planner for a webinar or product launch, and as a plain time zone calculator for meetings when you only need to know what your 3:00 PM is somewhere else.
A few cases where getting the time zone for meetings right matters more than usual:
- Webinars and launches. Pick the slot that reaches the largest share of your audience while they are awake, then publish the start time in UTC alongside two or three local times.
- Client conference calls. A client is not a colleague. Give them the comfortable end of the overlap and take the early start yourself.
- Interviews across borders. Candidates almost never push back on a bad time. Check it is reasonable for them before you send it — and write the time zone in the invitation, because “MST” and “MT” are not the same thing and recruiters lose candidates over it.
- On-call and support handovers. Set the outgoing and incoming shifts as overnight working hours and the planner shows the true handover window rather than assuming a 9-to-5 day.
- Deadlines and cut-offs. “Midnight” is a different moment in every country on the call. State the time zone, or better, use UTC.
Share the Plan Without Anyone Signing Up
The planner keeps its entire state in the URL. Click Copy planner link and the participants, their time zones, their working hours, the date, the duration and the selected slot all travel inside the link itself. Whoever opens it sees exactly what you see — no account, no login, nothing stored on a server.
That also makes the link a bookmark. Keep one for “US + Israel team” and another for “London / Sydney client call” and you never rebuild the same group twice. If you would rather not manage links, Save this team stores the group in your own browser and it reappears next visit.
Once a time is chosen, Copy message produces a ready-to-send block:
How does this time work for everyone?
Wednesday, September 16, 2026 — 60 minutes
Dan (Tel Aviv) — Wed 4:00 PM
Sarah (London) — Wed 2:00 PM
Mike (New York) — Wed 9:00 AM
Frequently Asked Questions
What is a meeting time zone planner?
A meeting time zone planner is a tool that lines up several people’s local times side by side so you can see, at a glance, which hours work for everyone. A basic one shows a colour-coded grid of everybody’s day. This one goes further: it scores every possible slot for how convenient it is for the whole group, ranks the best options, and explains the trade-off in each one.
How do I find the best meeting time across time zones?
Add every participant with their city and working hours, choose the date, and read the ranked recommendations. The planner checks each candidate slot against every person’s real availability for that specific date — including daylight saving, half-hour offsets and public holidays — and ranks by how fairly the inconvenience is distributed rather than by simple average.
What time works for everyone during working hours?
If a shared working-hours window exists, the planner finds it and marks it green on the timeline. If none exists, it says so plainly rather than showing an empty result, and offers the fairest compromises instead. For teams spanning more than about eight hours, no such window usually exists at all — which is normal, not a failure.
Which meeting time is fairest when there is no overlap?
The fairest option is the one that minimises the worst individual experience, not the one with the best average. Three people at a perfect time and one at 5:00 AM scores worse here than four people all mildly stretched. For anything recurring, fairness also means rotating who stretches, so the same office does not absorb the cost every week.
What will 3:00 PM my time be for everyone else?
Set the meeting to 3:00 PM by clicking that hour on your row of the timeline, and every other row updates instantly to show the same moment in their local time — with a +1 day or −1 day label wherever the calendar date differs from yours.
Will daylight saving time change these meeting times?
Yes, and not on the same date everywhere. The planner uses date-aware IANA time zone data, so the times shown are correct for the specific date you pick. It also warns you when a clock change is coming that will move your meeting — including the awkward two-to-three-week windows each spring and autumn when the United States and Europe are temporarily an hour closer than usual.
How do we schedule a weekly global meeting without always making the same team join at 6:00 AM?
Set the meeting to repeat. The planner then optimises the whole series rather than each meeting on its own, rotating the slot so the inconvenience moves around the group, and showing a ledger of who has carried how much. If one slot genuinely suits everyone every week, it keeps that slot instead of rotating pointlessly.
What time zone am I in?
The planner detects it automatically from your device and shows it as a city plus a GMT offset — for example Tel Aviv — GMT+3. You can override it if you are travelling or planning on someone else’s behalf.
Is this a meeting planner, a time zone converter or a scheduler?
All three, depending on what you need from it. Used as a meeting planner it recommends and ranks times. Used as a time zone converter it tells you what one moment is everywhere at once. Used as a meeting time zone scheduler it hands you a calendar invite at the end. There is nothing to switch between — the same screen does all of it.
How many time zones or people can I add?
Up to fourteen. In practice two to eight is where the timeline stays readable; beyond that, group people who share both a time zone and a working pattern into one row.
Does it handle half-hour and quarter-hour time zones?
Yes. India (UTC+5:30), Nepal (UTC+5:45), Adelaide (UTC+9:30), Newfoundland (UTC−3:30), Iran (UTC+3:30) and the Chatham Islands (UTC+12:45) are all handled exactly, not rounded to the nearest hour.
Can I set different working hours for different people?
Yes — that is the point of a participant-first planner. Each person has their own hours, and you can give someone split hours around a lunch break, or hours that cross midnight for night shifts and on-call rotations.
Can I add the meeting to Google Calendar or Outlook?
Yes. Once you have chosen a time, use the Google Calendar or Outlook buttons, or download an .ics file that works with Apple Calendar, Thunderbird and anything else that reads standard calendar files. Recurring meetings carry their repeat rule into the invite.
Can I share the result with my team?
Yes, three ways: copy a paste-ready message with everyone’s local time, copy a link that reopens the whole plan exactly as you left it, or send a calendar invite. Nobody you share with needs an account.
Is this meeting time zone planner free?
Completely. No sign-up, no account, no email, no limits, and nothing is stored on a server — saved teams live in your own browser and shared plans live inside the link.
What is the best time of day to schedule a global meeting?
For teams spanning Europe and the Americas, 14:00–17:00 UTC is usually comfortable for both. For Europe and Asia, 08:00–11:00 UTC. For all three regions at once there is no comfortable answer, and 13:00–15:00 UTC is the usual least-bad compromise — which is exactly the situation the fairness scoring and the rotation planner are built for.
My name is