Timezone meeting planner
Choose a base timezone and compare the same moment across common cities.
TIMEZONE PLANNER
Choose a base timezone and compare the same moment across common cities.
Choose a base timezone and compare the same moment across common cities.
READ BEFORE YOU GO
How it works, examples, limits and sources behind the tool.
The planner converts one moment in a base timezone into the local time of other cities at that same instant. Conversion uses the offsets and daylight-saving rules in the IANA time zone database; a city can differ by an hour between winter and summer, so the result changes with the selected date.
It does not add travel time or pick a “fair” slot for you. You set a local date and time in the base city; every other column is that same UTC instant. Change the date around March or November to see whether a weekly call shifts when a region enters or leaves daylight saving.
Suppose you schedule a 9:00 meeting in Shanghai while colleagues in London must join. In winter London is UTC+0, so the local time is 1:00; in summer (daylight saving, UTC+1) it is 2:00. The tool converts the base moment to UTC, then applies each target city's offset for that day.
A second check: 09:00 in New York on a July Tuesday is 14:00 in London (BST) and 21:00 in Shanghai. In January the UK and US are both on standard time, so the London clock can look unchanged while Shanghai is still 13 hours ahead. India is UTC+5:30 — do not subtract a whole number of hours. Paste the candidate into the planner before you send the invite.
Use it to schedule calls with remote teams, confirm the exact moment of international flights or livestreams, and double-check arrival local times when booking tickets.
Use it again in the week a region changes daylight saving, and whenever a half-hour timezone (India, Nepal) is on the invite. The meeting-time guide on this site covers overlap windows and fairness; this page only shows the conversion.
The most common mistake is ignoring daylight saving: converting with a fixed offset drifts by an hour in spring and autumn. Mixing up the arrival city's local time with the departure city's time is another, as is forgetting that some cities, such as Shanghai, never observe daylight saving.
Another is writing “Tuesday 09:00” with no zone name, or using the phone’s system timezone after it has already switched on a trip. Across the date line, say which calendar day you mean. Half-hour offsets rounded to whole hours miss by 30 minutes.
Offsets and daylight-saving rules come from the IANA time zone database and follow the selected date. The tool assumes a city follows the rules currently published there; if a region changes its offset or drops daylight saving at short notice, results may be inaccurate for a while.
The city list is a planning set, not every IANA zone. The tool does not read airline schedules or visa calendars. For a high-stakes slot, confirm with the other person after you have a candidate from the grid.
Yes. Conversion uses the IANA database for the date you pick. A city can shift by an hour between winter and summer.
A fixed offset ignores daylight saving and one-off political changes. Pick the date of the meeting, not an offset you memorised.
No. It converts one instant across cities. For arrival local time on a flight, use the flight-time tool and then confirm the ticket.