How are DST shifts handled?

The offset for each timezone is computed from `Intl.DateTimeFormat` at noon UTC on the date you pick. Pick a date in the actual meeting week and you'll get the right offset; meetings that straddle a DST change still need a second look.

Why are working hours per-zone?

Cultural norms differ — many Asian offices start at 09:30 and run past 18:00, US tech runs 09-17, Spain has a long lunch. Set them per person to avoid scheduling 8 AM calls into 7 PM for someone.

Meeting Time Finder Across Timezones

Time

Plots every participant's working hours on the same 24-hour UTC row and highlights the hours where everyone is online. Each row also shows the local hour in that zone so you can read the slot in any local calendar. Built from `Intl.DateTimeFormat` so DST transitions are handled correctly for the chosen date — pick a date that falls inside the meeting week and the offsets respect summer/winter time shifts. No accounts, no calendar access, no API calls.

—

How to use

Add each participant's timezone (start typing for autocomplete) and adjust their working-hours window.
Pick a date inside the meeting week so DST handling is right.
Dark-green cells are the overlap window — pick from the best-slots list below the grid.

Frequently asked questions

How are DST shifts handled?: The offset for each timezone is computed from `Intl.DateTimeFormat` at noon UTC on the date you pick. Pick a date in the actual meeting week and you'll get the right offset; meetings that straddle a DST change still need a second look.
Why are working hours per-zone?: Cultural norms differ — many Asian offices start at 09:30 and run past 18:00, US tech runs 09-17, Spain has a long lunch. Set them per person to avoid scheduling 8 AM calls into 7 PM for someone.