Time & Productivity Utility
World Meeting Planner
Convert one UTC meeting instant into three destination time zones.
Plan across time zones
Method
The planner treats the entered date and time as UTC by appending the UTC designator to an ISO timestamp. It then formats that one instant separately for each chosen destination with the browser’s Intl.DateTimeFormat time-zone support. This keeps all destinations synchronized to the same moment.
Worked example
For January 15, 2026 at 17:00 UTC, the example compares New York, London, and Tokyo. Under the browser’s time-zone rules, New York is five hours behind UTC, London matches UTC in January, and Tokyo is nine hours ahead and has crossed into January 16.
When this is useful
This planner is useful for remote teams, interviews, webinars, launches, support rotations, and international calls. Starting from UTC is especially useful when a schedule already publishes its canonical time in UTC.
Privacy
The date, time, and selected zones are processed locally with browser APIs. No meeting details are sent to a scheduling service.
Limitations
This version accepts UTC as the source rather than an arbitrary named source zone. Time-zone abbreviations and offset rules are supplied by the browser and can vary as political or historical time-zone data changes. It does not check participant calendars or business hours.
FAQ
Why is the source time UTC?
UTC provides one unambiguous reference instant. That avoids silently guessing which offset applies to a typed local time in another region.
Does it handle daylight-saving changes?
The browser formats the UTC instant using its installed IANA-style time-zone data, so seasonal offsets are applied according to that data.
Related tools