World Time Zone Meeting Planner
Pick a date, time and home city to see the local time in 9 major world cities at once, and how many fall within working hours — for scheduling meetings
3 of 9 locations are in working hours at this moment
Time zone offsets and daylight-saving transitions come from your browser's built-in IANA time zone database, the same source operating systems and calendar apps use — not a fixed, hardcoded UTC offset per city, so results stay correct across DST changes throughout the year.
About this tool
How to use it
- Choose the date and the proposed hour/minute for the meeting, in your home city's local time.
- Select your home city (or the closest match to your own time zone) from the dropdown.
- Optionally adjust the working-hours window if 9:00-18:00 doesn't match the teams you're scheduling around.
- Press Find Meeting Times, or just change any field — the table updates live.
- Scan the table for how many locations show 'Working hours', and try a different hour if too few do.
Why it matters
A meeting time that's mid-morning for you can be the middle of the night somewhere else, and the only way to know for sure is to check every time zone individually — daylight saving makes this worse, since the gap between two cities' clocks can change by an hour depending on the time of year. Converting every city at once, using the same real time zone database your operating system uses, removes both the manual arithmetic and the DST guesswork.
When to use it
Useful when scheduling a call or meeting across offices, teams, or collaborators in different countries, especially near a daylight-saving transition when a time that worked last month might not work this month. Also useful for planning when to post, publish, or go live for an audience spread across time zones.
Good to know
Time zone offsets and daylight-saving transitions are read from your browser's built-in IANA time zone database — the same source your operating system and calendar apps use — not a fixed, hardcoded UTC offset per city, so the tool stays correct as DST start/end dates shift. The 9-to-5 default 'working hours' window is just a common starting assumption, not a universal standard; adjust it to match the actual hours of the teams you're scheduling around. The nine cities shown are a fixed, curated set meant to represent commonly-referenced regions — not every city or time zone in the world.
Common questions
Does this account for daylight saving time correctly?
Yes — the conversion is computed for the specific date entered using the browser's real time zone database, which includes each zone's actual DST start and end dates, rather than a fixed year-round offset. Checking the same meeting hour in January versus July can show a different time gap between two cities for exactly this reason.
Why are only 9 cities shown?
They're a fixed, curated set chosen to span a wide range of commonly-referenced time zones across the day, not an exhaustive list. If your specific city isn't listed, pick the city in the list that shares its time zone, or use your own detected zone as the home city and read the other 8 as reference points relative to it.
What does 'working hours' mean here?
It's whatever window you set in the two working-hours fields (9:00-18:00 local time by default) — the tool simply checks whether each city's converted local hour falls inside that window. It has no knowledge of actual holidays, weekends, or any team's real working schedule beyond the hours you specify.
Can I use this to schedule a meeting on a specific weekday?
The tool shows the weekday for each city's converted time (since a very early or very late hour can push the date into the next or previous day locally), but it doesn't check whether that day is a weekday or weekend for any city — check the shown date/day against a calendar if that matters for your meeting.