Does the tool handle daylight saving time?

Yes. Offsets are computed from the full IANA time zone database for the date you pick, so spring-forward and fall-back shifts show up correctly. If you're planning a meeting two months out, change the date to that week and the grid will reflect the right offsets.

What if no time works for everyone?

If the overlap row is all grey, the working hours don't intersect for the people you've added. Widen the global working hours, drop the lowest-priority attendee, or split the meeting into two timezone-friendly sessions.

Is my team roster saved anywhere?

Only in your browser. The roster, reference zone, and working-hour settings are stored in local storage on your device. Nothing is sent to a server. Clear the list any time with one click.

Why is the tool capped at 10 people?

Beyond ten people the grid gets dense and the chance of a clean overlap drops to near zero anyway. If you're scheduling for more than ten across zones, the answer is usually an async channel or a rotating meeting time rather than one shared slot.

Timezone Overlap

Find meeting times that work across time zones. Up to 10 people, no sign-up.

Show times in

Date

Working hours

Team roster

Up to 10 people. Saved in your browser.

More free tools

Meeting Timer

Countdown for standups & workshops.

Meeting Cost

What this meeting costs in real time.

All free tools

The full kit.

Distributed teams need daily glue.

Halftime is a 2-minute game your team plays together each workday. Async-friendly, timezone-tolerant, and infinitely more fun than a status channel.

See how Halftime works Try a game free

Free for teams up to 8 · No credit card · 30-second setup

How to schedule a meeting across time zones

The first rule of scheduling across time zones: don't do it in Slack. A chat thread where three people try to compare their calendars is a slow, manual version of what this tool does automatically. Drop the team in the grid, look at the green row, pick a slot, copy the invite time, send it.

What the overlap row is telling you

The overlap row at the bottom of the grid summarises every attendee's status for each hour. Emerald means every person is inside their defined working hours. Amber means at least one person is on the edge of their day (the hour before start or the hour after end). Grey means somebody is well outside working hours or asleep. Pick emerald when you have options; pick amber if you don't.

When there is no overlap

For teams that span more than about nine hours of time zone (say, California to Singapore), a nine-to-five working hour window won't intersect. You have three options:

Widen hours. Agree as a team that anyone joining a cross-zone meeting stretches by an hour or two. The tool surfaces the edge candidates in amber.
Rotate who absorbs the pain. Alternate meeting times so the burden of odd hours doesn't always land on the same person.
Go async. If the meeting is a status update, it probably doesn't need to be a meeting. If it's a decision, record context and ask for votes instead of consensus.

Daylight saving time makes this worse

Twice a year, the world gets half a meter out of phase with itself and time-zone offsets shift. If you're planning something two weeks out, change the date picker to that week rather than today. The grid recomputes using the correct offsets for that date. This is especially important for meetings that cross the US–Europe gap, which changes by an hour twice a year at different dates on each side.

What gets copied when you click a column

Selecting an hour and hitting copy gives you a clipboard payload like:

Mon 3:00 pm London
  Alex: Mon 3:00 pm London
  Jordan: Mon 10:00 am New York
  Sam: Mon 7:00 am Los Angeles

Paste that into your calendar invite description, your Slack message, or the email you're sending. It's the format most teams already use, and every attendee can immediately see their own local time without doing math.