Skip to content
overlaply

Meeting times across time zones

Add the places your meeting spans, set the hours each one works, and read off the hours that overlap.

Looking for a single conversion rather than a whole day? The time zone converter answers what one time is somewhere else, pair by pair.

Choosing the hour is only part of it. The guide to scheduling across time zones covers whose working hours count, who takes the awkward hour, and how to write a time nobody misreads.

How the planner works

  1. Every moment is graded per place

    Each cell is one time step in one place. Its grade comes from the working hours and the awake hours you set, and from that place's own local date — which is why a Friday afternoon in San Francisco can be a Saturday morning in Tokyo.

  2. The verdict reads the whole day

    The banner names the longest run of hours that sits inside everybody's working hours. When no such run exists it says so, and ranks the least-bad options with the cost attached to each rather than picking one and staying quiet about it.

  3. Nothing leaves your device

    Time-zone rules ship with the page and every calculation runs in your browser. A share link carries the setup in the address itself, so there is nothing stored on our side for a link to point at.

Questions about time zones

Yes, and it shows them rather than hiding them. A spring-forward day is drawn with 23 columns and the missing hour is named; a fall-back day is drawn with 25, and the hour that happens twice appears twice with its two offsets. A grid that normalised every day to 24 hours would be wrong on exactly the four days a year you most need it to be right.

Because the abbreviation belongs to the instant, not to today. A November meeting in Alberta reads MST while today reads MDT, and a fall-back day's two 01:00 columns read PDT and PST. Labelling an April meeting in Sydney AEDT because today is January is a real and common bug, and it is the reason every label here is resolved for the moment being shown.

Yes, and that is the point. Open a place and set its window, or set one window for everybody at once. Each place can also treat weekends as non-working, graded against that place's own local date — a tool that assumes Monday to Friday nine-to-five is wrong for that person in a way they cannot correct.

One event at the exact instant you pinned, with a real VTIMEZONE block for the anchor place derived from that zone's actual clock changes. No participants are collected and none are written into the file. The event carries the instant, so it lands correctly in a calendar whose own time-zone data differs from ours.

The IANA time zone database, pinned to a named release and re-derived rather than trusted to your browser. The release and the date it was checked are printed in the footer of the planner, and the methodology page shows the source URL and the years the table covers. If your browser's own data is older, the planner says so instead of quietly disagreeing with itself.