Select participants' timezones and find overlapping business hours. Interactive visual timeline for scheduling.
Select the time zones of all meeting participants.
See which hours work for all time zones at a glance.
Choose the best slot and see the local time for each person.
Shows every participant's working day as its own row on a 24-hour timeline and highlights the hours where all business-hours windows overlap. Enter each person's time zone and typical business hours, pick a date, and the chart aligns every row to the same underlying instant so overlap reads directly. People often misread the rows as comparable clock times: 09:00 in one row is not 09:00 in another, and the overlap only exists for the exact date chosen because DST offsets change across the year.
A concrete input and expected output from the current implementation.
Input
Two participants on July 15, 2026, a summer date when both cities observe daylight saving time. New York business hours 09:00-17:00 in EDT (UTC-4). London business hours 09:00-17:00 in BST (UTC+1).
Expected output
Shared overlap of 3 hours: 09:00-12:00 in New York, 14:00-17:00 in London, which is 13:00-16:00 UTC.
Convert both windows to UTC: New York 09:00-17:00 EDT becomes 13:00-21:00 UTC, and London 09:00-17:00 BST becomes 08:00-16:00 UTC. The intersection is 13:00-16:00 UTC, a 3-hour block. Reading that block in each local time gives 09:00-12:00 in New York and 14:00-17:00 in London. London is five hours ahead of New York in July, so when New York reaches 09:00, London is already at 14:00; the shared window is the first three hours of New York's day and the last three of London's.
Every row displays the same underlying instant, converted to that participant's local time. The timeline is drawn on one universal scale, so a vertical slice through the chart is the same moment for everyone; overlap is computed by comparing each row's business hours on that shared scale, never by comparing raw clock numbers between rows.
Most of the world runs on whole-hour offsets, but some places do not: India is UTC+5:30 and Nepal is UTC+5:45, so overlaps involving them can start or end on half-hour or quarter-hour marks. Offsets also change with daylight saving time, so the same pair of cities can produce different overlaps on different dates; the result is only valid for the date shown.
US daylight saving runs from the second Sunday in March to the first Sunday in November; the EU runs from the last Sunday in March to the last Sunday in October. For several weeks each year, one side has switched and the other has not, so New York and London are 4 or 6 hours apart during those windows and 5 hours otherwise. The result is valid for the date shown.
No. The tool only shows you the window where business hours overlap; it does not generate calendar entries or send invites. It runs entirely in the browser, so your participant list, time zones, and hours stay on your device and nothing is uploaded to a server.
The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Create customizable checklists with groups, due dates, and priorities for any project.
Design a printable daily planner with time blocks, goals, and priority sections.
Measure your typing speed in WPM and accuracy with real-time feedback and stats.
Pomodoro timer with built-in ambient noise (rain, cafe, forest) generated via Web Audio API oscillators.
Stay focused with a customizable Pomodoro timer featuring work and break intervals.
A precise stopwatch with lap tracking, split times, and exportable results.