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.

What is the Time Zone Meeting Planner?

Free time zone meeting planner. Choose a date and time in any reference time zone and instantly see the equivalent local time across major cities, with daylight saving handled. Privacy-first — everything runs in your browser and nothing is sent anywhere. It runs free in your browser on Gera Tools, with nothing uploaded.

Time Zone Meeting Planner

Name: Time Zone Meeting Planner
Creator: Gera Tools
License: https://creativecommons.org/licenses/by/4.0/

Get one useful tool a week

Like this tool? Enter your email and we'll send you one genuinely useful Gera tool a week — plus a link to come back to this one. No spam, one-click unsubscribe any time.

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.

Why daylight saving makes this tricky to do by hand

The naive approach — “subtract 5 hours for New York” — breaks twice a year, because the US and Europe do not change their clocks on the same date. In the two-to-three-week gap around each clock change, the offset between, say, New York and London shifts by one hour. The planner uses the browser’s built-in IANA tz database, which knows every transition date for every zone, so the conversion is correct for the exact date you enter regardless of where it falls relative to DST boundaries.

Worked example

A team has members in San Francisco, London, Dubai, and Singapore. The London lead proposes a call at 2:00 PM GMT on a Tuesday in February.

For that date in February, the planner shows:

San Francisco — 06:00 AM (a stretch, but workable)
London — 02:00 PM (the reference)
Dubai — 06:00 PM (after core hours, but still reasonable)
Singapore — 10:00 PM (late; the Singapore member may prefer async)

The day names confirm everyone is still on Tuesday for this time.

Now try the same meeting in late March, after the UK has shifted to BST but before the US has moved to daylight saving. The planner automatically adjusts the UTC offsets and the San Francisco time shifts to 07:00 AM — the gap narrows for one week, which is exactly the kind of detail mental arithmetic misses.

Finding the right slot

When no single time works for everyone, look for the window where all cities fall between roughly 08:00 and 20:00. The cities that most often constrain the window are on the far ends of the span: a team spread from the US West Coast to Southeast Asia faces a 15+ hour gap where there is essentially no overlap in standard working hours. In those cases, rotating meeting times so no single city always carries the early-morning or late-evening burden is a common team policy.

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