Timezone Overlap Finder: How to Find the Best Meeting Slot
Reviewed by the OnlineFree.app team · Updated
Key points
- The Timezone Overlap Finder turns two timezones and a shared work-hour range into an overlap figure plus ranked meeting slots.
- It applies one working-hours range to both sides, so a colleague on different hours needs a manual adjustment.
- The overlap is calculated for today's date only, so rerun the tool around daylight-saving transitions.
- Every suggested slot is listed in both local times and UTC, which prevents conversion errors in invites.
- Half-hour offsets like India's UTC+05:30 rarely produce clean whole-hour overlaps, so read the lanes carefully.
What the Timezone Overlap Finder shows
The Timezone Overlap Finder answers one question fast: how many working hours do two timezones share today, and when should the two of you meet? You pick two zones and a shared work-hour range, and it returns the overlap in hours plus up to three ranked meeting slots, each written out in both local times and UTC.
There are only three inputs. Your timezone is auto-detected from the browser (falling back to America/New_York), their timezone defaults to Europe/London, and the working-hours range defaults to 09:00–17:00 and is limited to a window of 4 to 14 hours. The zone lists come from the browser's own IANA data where available, so you get entries like America/Chicago and Asia/Kolkata rather than vague abbreviations.
It is built for the ten-second question — the one you ask on a phone between other tasks, not the one you open a scheduling suite for. No signup, no account, one screen. If you want to see what else runs on the same site, the free online tools on OnlineFree.app are all browser-based in the same style.
How to read the 24-hour overlap band
The timeline is a horizontal 24-hour bar split into two lanes, Zone A on top and Zone B below. The band where the two working-hour windows actually intersect is highlighted and labelled with the overlap figure, and a small caption underneath reads "Today: <date> · DST-aware".
The number is expressed in hours with one decimal, and it comes from minutes — so a two-hour-forty-five-minute intersection shows as 2.8 hours, not 2.75. Don't round it a second time when you write the invite; use the slot cards instead, which give exact clock times.
Half-hour and 45-minute offsets are where people misread the band. India is UTC+05:30 and Nepal is UTC+05:45, so their overlaps rarely land on clean hour boundaries. Read the two lanes rather than assuming the band is symmetric around either side's lunch break.
How do you pick the best meeting slot?
The tool ranks up to three slots by how deep they sit inside both work windows, so the middle of the highlighted band always scores highest — that is the slot labelled something like "Best for both". The other two carry friendly warnings such as "Early for London" or "Late for New York", which tell you who is absorbing the inconvenience.
Read the UTC column before you send anything. Every suggested slot shows the same instant three ways — Zone A local, Zone B local, and UTC — and copying the UTC value into the invite removes the most common source of "wait, was that 9am your time?" replies.
Slot lengths default to 30 and 60 minutes, so a 30-minute stand-up and a 60-minute review can use the same band. If your overlap is under about two hours, alternating the awkward slot week by week is usually fairer than locking one region into an early start forever.
One thing the band cannot see: time off. When a recurring slot collides with leave on one side, the window you negotiated disappears for a week. The Vacation Day Optimizer is a quick way to see how days off reshape a calendar before you commit to a recurring meeting.
Common mistakes that shrink your overlap
The biggest one is assuming a fixed offset. Timezone gaps are not constant: US daylight saving begins on the second Sunday in March and UK daylight saving begins on the last Sunday in March. Between 8 March and 29 March 2026, New York and London are only four hours apart instead of five, and the same New York–London pair produces a 4.0-hour overlap in that stretch versus 3.0 hours once both sides have switched. The IANA Time Zone Database is the authoritative record of those rules.
The second mistake is applying your own hours to both sides. The tool uses one 09:00–17:00-style range for both zones, which is a reasonable default and a wrong assumption for a colleague in São Paulo or Dubai who starts at 08:00 or finishes at 18:00. Widen your range slightly to see how the band moves.
The third is typing an ambiguous abbreviation. "CST" could be US Central, China Standard Time, or Cuba Standard Time. Always pick the full identifier such as America/Chicago from the searchable list. And remember the tool computes for today's date only — if the meeting is three weeks out and crosses a transition, rerun it closer to the day. Background on how the switches work is in the Wikipedia article on daylight saving time.
A worked example: New York and London
Take the defaults: America/New_York and Europe/London, working hours 09:00–17:00 on both sides. In summer, when both regions are on daylight saving, New York's 09:00–17:00 EDT is 13:00–21:00 UTC, and London's 09:00–17:00 BST is 08:00–16:00 UTC. The intersection is 13:00–16:00 UTC — 3.0 hours — and the deep middle of the band sits at 14:30 UTC, which is 10:30 in New York and 15:30 in London.
Now take the awkward March stretch. With the US already on EDT and the UK still on GMT, New York's working day runs 13:00–21:00 UTC while London's runs 09:00–17:00 UTC. The overlap stretches to 4.0 hours, running 13:00–17:00 UTC, and the best slot moves to roughly 15:00 UTC — 11:00 in New York, 15:00 in London.
Same two cities, same two work-hour ranges, different answer. That is why the "Today: <date> · DST-aware" caption matters, and why a screenshot of a slot from last month is not a safe reference. If a number on screen decides a real meeting, confirm it against the IANA rules for that specific date before you send the invitation.
Frequently asked questions
Is the Timezone Overlap Finder free and does it need an account?
It is free and requires no account, signup, or email — you open one screen, pick two timezones and a work-hour range, and read the result immediately in the browser. Defaults are auto-detected from your device with a fallback of America/New_York for zone A and Europe/London for zone B.
Why does the Timezone Overlap Finder show zero overlap hours?
Zero means the two working-hour windows never intersect in absolute time. With 09:00–17:00 on both sides, New York covers 13:00–21:00 UTC while Tokyo covers 00:00–08:00 UTC, so there is no shared minute. Widen the range (up to 14 hours) or shift one side's hours to create a band.
Does the Timezone Overlap Finder account for daylight saving time?
Yes. It is DST-aware and shows a caption reading "Today: <date> · DST-aware" under the timeline, so the offset it uses matches the current date's rules. Note that it calculates for today only — a figure taken in March may not hold in April, because transition dates differ between countries.
How many meeting slots does the Timezone Overlap Finder suggest?
It returns up to three ranked slots, ordered by how deep they sit inside both work windows. Each slot is shown as the same instant in Zone A local time, Zone B local time, and UTC, with a friendly label such as "Best for both" or "Early for London", and slot lengths default to 30 and 60 minutes.
Can I plan a meeting weeks ahead with the Timezone Overlap Finder?
Not directly — the overlap figure and the suggested slots are computed for today's date, so they are not a projection for a date weeks out. For meetings that cross a daylight-saving transition, rerun the tool nearer the day, or check the IANA time zone rules for the specific date.