Does it account for daylight saving time?

Yes. Conversions use the browser's built-in IANA time-zone database, so daylight saving is applied correctly for the specific date you choose, not a fixed offset.

How accurate are the converted times?

Times are computed from the same UTC instant for every city, so they are exact to the minute. The accuracy of future-dated DST transitions depends on your browser's time-zone data being up to date.

Is my meeting time sent anywhere?

No. The planner is privacy-first — the date, time and zone you pick stay in your browser and are never uploaded to a server.

Which cities are shown?

A spread of major hubs across the world, from Honolulu and Los Angeles through London, Paris, Dubai and Mumbai to Singapore, Tokyo, Sydney and Auckland, covering most working time zones.

Why does one city show the next day?

When a meeting time in one zone falls after midnight in another, that city's row shows the next calendar day. The day name in each row makes these wrap-arounds obvious.

Can I plan across the international date line?

Yes. Because every row is derived from the same UTC instant, cities on opposite sides of the date line show the correct local day and time, including when they differ by a calendar day.

What is an IANA time zone?

It is a Region/City identifier such as Europe/London or Asia/Tokyo from the canonical tz database, which encodes each zone's offset and its daylight-saving rules over time.

Time Zone Meeting Planner

Time zone meeting planner

This planner removes the mental arithmetic from scheduling across borders. Pick a reference time zone, a date, and a time, and it shows the same moment as a local wall-clock time in major cities worldwide — ideal for remote teams, international calls, and webinar scheduling.

How it works

The tool anchors on a single UTC instant. It finds the instant that, when formatted in your chosen reference zone, reads back as the wall-clock time you entered — correctly handling that zone’s UTC offset and daylight saving via the browser’s Intl time-zone support. It then formats that same instant in each target city’s IANA zone. Because every city is derived from one instant, the times are mutually consistent to the minute, and each row shows the UTC offset and day name so next-day and previous-day overlaps are obvious.

Example

Set a meeting for 9:00 AM in New York. The planner shows 2:00 PM in London, 3:00 PM in Paris/Berlin, 6:30 PM in Mumbai, and 11:00 PM in Tokyo — with Tokyo’s row flagged so you can see it is late evening there. Daylight saving is applied for the exact date chosen.

It is privacy-first: the date, time and zone you enter stay in your browser and are never sent anywhere.