This planner lines up each added city or IANA timezone (like "Europe/Berlin" or "Asia/Kolkata") on its own row of a shared 24-hour timeline, so you can see at a glance where everyone's working hours actually overlap instead of doing the math in your head. It reads offset and daylight-saving rules straight from your browser's built-in timezone database, so the timeline stays correct even across a DST transition.
Because each city is tied to a real IANA timezone rather than a fixed UTC offset, the tool automatically applies whatever DST rule is in effect for the date you're planning around — so a meeting slot picked in winter won't silently be an hour off if one side of the call has since sprung forward.
Yes — you can search by city name or type an IANA timezone identifier directly, and any zone your browser's Intl API recognizes can be added to the timeline.
Not every timezone is a whole-hour offset from UTC — India (UTC+5:30) and Nepal (UTC+5:45) are common real-world examples. The planner reflects these fractional offsets exactly as they're defined, which is why the timeline can show a half-hour stagger between regions that look "close" on a map.