Add cities to see working hours overlap in a visual timeline. Green = working hours, dark green = overlap.
Everything you need to know about scheduling across time zones.
The tool compares standard working hours (9 am–6 pm local time) across all cities you've added. An hour is counted as an overlap only when every city on your list is within working hours at that same UTC moment. The dark green segments on the timeline show exactly those hours, and the summary above the chart tells you the full overlap window.
Yes. All UTC offset calculations use your browser's built-in Intl API with the IANA timezone
database (e.g. America/New_York, Europe/London). This means DST transitions are handled
automatically — the offsets shown always reflect the correct local time for today's date, not a fixed
offset.
Enter a proposed meeting time in UTC and each city row will show what that time translates to locally. This is useful once you've identified a good overlap window and want to confirm how the time looks for each participant — for example, whether it falls before lunch or after end-of-day.
Yellow (early/late) covers the hours just outside core working hours: 7–9 am and 6–8 pm local time. These aren't ideal, but they're often acceptable for a quick standup or catch-up call when no green overlap exists. If your team spans very distant zones, the yellow window may be the most practical option.
Some combinations — like Tokyo and New York — have no common working hours when using a strict 9 am–6 pm window. A few strategies that help:
Use the yellow window. An 8 am start for one side and a 6 pm wrap for the other can work for occasional syncs.
Rotate the burden. Alternate who takes the inconvenient slot each week so no single team always bears the cost.
Go async. For teams with zero overlap, recorded video updates, shared docs, and structured handoff notes often work better than a live meeting anyway.
Click Copy shareable link. The button encodes all your selected cities into the URL as
query parameters (e.g. ?tz=America/New_York&tz=Asia/Tokyo). Anyone who opens the link will see
the same set of cities pre-loaded — no account or signup required.
There's no hard limit. In practice, most teams find 3–6 cities the most readable. Adding more cities makes the overlap window smaller (or disappears it entirely), since every city must be in working hours simultaneously. If your org spans many regions, consider grouping people by hub and treating each hub as one row.
No. Everything runs entirely in your browser — no data is sent to a server, no cookies are set, and nothing is stored between sessions. The only "state" is what's in the URL when you use the share link, which you control entirely.