gizmobench
BrowseDaily

Meeting Time Zone Planner

Plan a cross-time-zone meeting by comparing local times in multiple cities on a date you choose. Add cities by name or IANA zone, set a shared working-hours window and select a time from the board. This global meeting planner looks up each sampled instant in the browser's time zone database, including daylight-saving differences and half-hour or quarter-hour offsets. Green marks samples inside your working window; the ranked suggestion offers a shared sample or a compromise. The board checks 24 hourly samples starting at 06:00 in the first city, so a short overlap may exist between samples. Copy the chosen slot or the full city list into an invite. This is a date-based comparison, not a live world clock or a check of participants' calendars, weekdays or holidays. Recheck each intended date when planning recurring meetings.

Setting the board up from your own time zone.

Working hours
Clock
Offsets are looked up for the date, because they change. A planner that stores London as +1 is wrong for five months of the year, and wrong by a different amount in the week between the UK leaving summer time and America leaving it. This one asks the browser's own time zone database for each city on the day you chose. Its rules depend on the browser's time zone database version. Half-hour and quarter-hour zones are shown exactly in the slot text even where the grid rounds them to a cell. The 24 samples begin at 06:00 in the first city and cover 24 real hours, which can extend into the next local date. One working-hours window applies to every city; these samples do not check personal calendars, weekdays or holidays.

Common questions

How do I plan an international meeting across different time zones?
Choose the meeting date, add each city and set the shared working-hours start and end. Compare the aligned samples, then click a cell or use the keyboard arrows to choose one instant for every city. Copy the Chosen slot line or Copy for the invite for the full city list. The first city anchors the board at 06:00 on the selected local date. All cities use the same working-hours window; individual availability is not imported.
Can I compare multiple cities and time zones?
Yes. Add cities through search or the common-city buttons. Search understands IANA zone names and bundled aliases such as Boston, Bengaluru and Kathmandu; accents are optional. Each row represents the same instants in that city. Different city names may share one zone. Remove a row to change the reference city when needed. Compare places for a remote team call or an international event.
How does the best meeting-time suggestion work?
The planner ranks 24 hourly samples: most cities inside working hours first, then fewest outside the extended work window, then the smallest worst distance from working hours, then total distance and the earliest sample. A shared sample puts every listed city inside the supplied window. If none does, the page offers a ranked compromise. This is not a minute-by-minute search, a universal best time or confirmation that people are available.
Can there be overlap even when no sampled time fits everyone?
Yes. For example, a 09:15 to 09:45 work window can fall between 09:00 and 10:00 samples. The page says no shared working-hour sample, rather than claiming that no overlap exists anywhere on the date. The board also covers 24 real hours from 06:00 in the first city, so its final samples can occur on the next local date.
Does the meeting planner account for daylight saving time?
Offsets come from the browser time zone database for each sampled instant. For example, on 28 October 2026 New York and London are four hours apart because their autumn changes occur on different dates; after 1 November they are normally five hours apart. A transition inside the board can repeat or skip a local hour. Future rules depend on the browser database version and government changes, so recheck the actual meeting date.
Are India, Nepal and other fractional time zones supported?
Yes. The chosen slot text keeps exact local minutes, such as :30 in Bengaluru and :45 in Kathmandu relative to a whole-hour New York sample. Grid cell labels show only the hour and say that fractional rows round down. Shading uses the exact local minute. Chatham and Lord Howe also use database-derived offsets, including their seasonal changes.
What do the working-hours colours mean?
Green is inside the supplied start/end window. Amber covers the two hours before its start and four hours after its end. Unlit cells are outside that extended window, which is not necessarily nighttime for a night shift. Windows crossing midnight are supported. The end is excluded. One common window applies to every city; weekends, holidays, breaks and individual calendars are not checked.
Can I convert meeting times and copy them into a calendar invite?
Selecting a column converts that sampled instant into each city's local time. The short line marks local date changes; Copy for the invite includes the full reference date and named city lines. Zone abbreviations come from the browser, with a UTC offset used when an English abbreviation is unavailable. It is a meeting comparison and text-copy workflow, without arbitrary minute input, an ICS file, calendar-provider integration or booking invitations.
Will the displayed time work for a recurring meeting?
Choose each occurrence's actual date and check the board again. The DST note reports the next offset changes found over 365 days in the current browser database; it does not promise that the same local times or participant availability continue until a particular date. It does not create recurrence rules, send invitations or maintain a calendar.
Is there an Excel template, native app or world time-zone map?
This page runs in the browser. It does not provide an Excel workbook, native mobile app download or geographic time-zone map. Those are separate workflows. The date-based rows compare local clocks, but they do not continuously update as a live world clock. Generic arbitrary-time conversion may also need a dedicated converter because this board samples whole hours.
What if the first city skipped the date or time I selected?
Some historical clock or date-line changes skipped local times or an entire day, such as Apia on 30 December 2011. If the first city's 06:00 anchor does not exist, the page refuses that board and tells you to choose another date or remove that first city. It does not silently substitute the previous day. Invalid dates, unknown zones and unreadable working hours also show actionable errors.
Are my cities and working hours remembered?
After you explicitly change the board or settings, cities, working hours and clock format can be remembered in local browser storage. A visit alone does not overwrite saved preferences, and a deliberately empty board stays empty. The selected date and chosen column are not saved; a new visit begins with the current date in your browser's zone. Blocked storage leaves the comparison usable. No account, calendar access or tool-input upload is required.

Offsets use the browser's time zone database, including daylight saving for each sampled instant. Half-hour and quarter-hour zones are exact in the text and rounded to a cell in the grid. Overlap compares 24 hourly samples, not every minute or calendar availability.