Time zones
Meeting Time Finder
Find hours that fall inside shared daytime windows across several timezones for calls, interviews, and client meeting panels.
Zones and times stay in this tab. Rosters are not uploaded.
How zones are handled
Samples the day in UTC steps and keeps slots where every selected zone is inside the shared daytime range you set. Narrow the local window when you only want civil daytime for calls, interviews, or client panels. If no slot fits, the tool says so plainly so you can move to async or split sessions instead of inventing a midnight compromise. When each person has different working hours, use Team Time Zone Planner instead of one shared band. Convert a single proposed clock with Time Zone Converter after you pick a candidate.
How to use it
Add the IANA zones for everyone on the call, pick the real meeting date, and set one shared local daytime window (for example 09:00-17:00). Review the candidate list, convert a favorite slot with Time Zone Converter if you need one more label, then send the invite. If the list is empty, widen the window, drop a region, or plan async.
Assumptions
Every zone uses the same local daytime band you enter. Sampling walks the chosen date using browser IANA offsets. Empty overlap is a valid result, not a failure of the page.
Worked example
Scenario
Date 2026-08-26 · shared local daytime 09:00–17:00 Zones: Europe/Zagreb, Europe/London, America/New_York
Output
Shared overlap (UTC 13:00–15:00): • 15:00–17:00 Zagreb (CEST, UTC+2) • 14:00–16:00 London (BST, UTC+1) • 09:00–11:00 New York (EDT, UTC−4) Example candidate: 15:00 Zagreb / 14:00 London / 09:00 New York Why: intersection of each zone’s 09–17 local window after DST for that date.
Quick comparison
| Tool | Input shape | Output |
|---|---|---|
| Meeting Time Finder | Several zones, one shared daytime band | Candidate slots or no overlap |
| Team Time Zone Planner | Roster with per-person hours | Overlap chips across individuals |
| Working Hours Overlap | Exactly two custom ranges | Overlap in both local clocks |
More coordination scenarios
- Zagreb, London, and New York with a shared 09:00-17:00 local window.
- Interview panel across three cities when “afternoon for everyone” is the goal.
- Widen the local window only after a strict daytime search returns no overlap.
Practical use cases
- Three cities need one overlapping daytime slot this week for a sync.
- You proposed a time and want to check whose evening it is before sending the invite.
- You need candidates before you send the calendar invite to a distributed panel.
- An interview loop spans regions and “afternoon for everyone” is the goal.
- You want an honest empty result before agreeing to a late-night compromise.
Limitations
One shared daytime band only; it cannot model different hours per person. Does not check personal calendars for conflicts. Does not create the invite. Sampling resolution may skip sub-step edges on unusual windows.
Timezone questions
- When should I use Team Time Zone Planner instead?
- Use Meeting Time Finder for one shared daytime band. Use Team Time Zone Planner when each person has different working hours on a roster.
- What if there is no overlap?
- The tool reports that honestly. Switch to async, split the meeting, or widen the local window if evenings are acceptable.
- Does the date matter?
- Yes. DST transitions can change offsets. Always pick the real meeting date when searching for slots.
- Can each person have different hours?
- Not in this tool. Shared band only. Move to Team Time Zone Planner for per-person ranges.
Timezone math uses your browser’s IANA data for the chosen instant. How our tools work · Editorial policy · Contact