Find the one hour everyone can make.
The free time zone meeting plannerthat overlays every teammate’s working day on a single 24-hour grid, picks the best shared window, and hands you a ready-to-send calendar invite. A full time zone converter, minus the guesswork.
Coordinated Universal Time
--:--:--
syncing…
- New York · United States--:--:--
- London · United Kingdom--:--:--
- Tokyo · Japan--:--:--
- Sydney · Australia--:--:--
Build your overlap panel
5 locations · all times update for DST- New YorkUTC-5
- LondonUTC+0
- New DelhiUTC+5.5
- TokyoUTC+9
- SydneyUTC+10
Tip: add every location with attendees — the grid shows all 24 hours at once.
No hour keeps anyone inside 09:00–17:00. Widen the working range or remove far-apart locations.
How the planner finds your best meeting time
Three steps from “where is everyone?” to a booked slot — no mental math, no conversion apps.
- 1
Add every location
Search 50+ cities and remote-work hubs — New York, London, Bengaluru, Tokyo and more. Each chip shows its live UTC offset.
- 2
Read the 24-hour grid
Each column is one UTC hour. Filled cells are inside a location’s working day, dimmed cells are night. The score strip counts who’s available.
- 3
Schedule & export
Snap to the highlighted best window (or click any hour), set a duration, and download an .ics invite that lands in each attendee’s local time.
Major time zones & their standard UTC offsets
A quick-reference converter for 52 major cities and remote-work hubs. Offsets shown are standard (non-DST) values; the live planner above always uses real-time IANA data, so daylight saving is applied for your chosen date.
| City | Region | IANA zone | Std. offset |
|---|---|---|---|
| Honolulu | United States | Pacific/Honolulu | UTC−10 |
| Anchorage | United States | America/Anchorage | UTC−9 |
| Los Angeles | United States | America/Los_Angeles | UTC−8 |
| Vancouver | Canada | America/Vancouver | UTC−8 |
| Denver | United States | America/Denver | UTC−7 |
| Phoenix | United States | America/Phoenix | UTC−7 |
| Chicago | United States | America/Chicago | UTC−6 |
| Mexico City | Mexico | America/Mexico_City | UTC−6 |
| Bogotá | Colombia | America/Bogota | UTC−5 |
| New York | United States | America/New_York | UTC−5 |
| Toronto | Canada | America/Toronto | UTC−5 |
| Santiago | Chile | America/Santiago | UTC−4 |
| Buenos Aires | Argentina | America/Argentina/Buenos_Aires | UTC−3 |
| São Paulo | Brazil | America/Sao_Paulo | UTC−3 |
| Dublin | Ireland | Europe/Dublin | UTC+0 |
| Lisbon | Portugal | Europe/Lisbon | UTC+0 |
| London | United Kingdom | Europe/London | UTC+0 |
| Amsterdam | Netherlands | Europe/Amsterdam | UTC+1 |
| Berlin | Germany | Europe/Berlin | UTC+1 |
| Lagos | Nigeria | Africa/Lagos | UTC+1 |
| Madrid | Spain | Europe/Madrid | UTC+1 |
| Paris | France | Europe/Paris | UTC+1 |
| Rome | Italy | Europe/Rome | UTC+1 |
| Stockholm | Sweden | Europe/Stockholm | UTC+1 |
| Warsaw | Poland | Europe/Warsaw | UTC+1 |
| Zurich | Switzerland | Europe/Zurich | UTC+1 |
| City | Region | IANA zone | Std. offset |
|---|---|---|---|
| Athens | Greece | Europe/Athens | UTC+2 |
| Cairo | Egypt | Africa/Cairo | UTC+2 |
| Helsinki | Finland | Europe/Helsinki | UTC+2 |
| Jerusalem | Israel | Asia/Jerusalem | UTC+2 |
| Johannesburg | South Africa | Africa/Johannesburg | UTC+2 |
| Istanbul | Türkiye | Europe/Istanbul | UTC+3 |
| Nairobi | Kenya | Africa/Nairobi | UTC+3 |
| Dubai | United Arab Emirates | Asia/Dubai | UTC+4 |
| Karachi | Pakistan | Asia/Karachi | UTC+5 |
| New Delhi | India | Asia/Kolkata | UTC+5:30 |
| Dhaka | Bangladesh | Asia/Dhaka | UTC+6 |
| Bangkok | Thailand | Asia/Bangkok | UTC+7 |
| Ho Chi Minh City | Vietnam | Asia/Ho_Chi_Minh | UTC+7 |
| Jakarta | Indonesia | Asia/Jakarta | UTC+7 |
| Hong Kong | Hong Kong | Asia/Hong_Kong | UTC+8 |
| Manila | Philippines | Asia/Manila | UTC+8 |
| Perth | Australia | Australia/Perth | UTC+8 |
| Shanghai | China | Asia/Shanghai | UTC+8 |
| Singapore | Singapore | Asia/Singapore | UTC+8 |
| Seoul | South Korea | Asia/Seoul | UTC+9 |
| Tokyo | Japan | Asia/Tokyo | UTC+9 |
| Adelaide | Australia | Australia/Adelaide | UTC+9:30 |
| Brisbane | Australia | Australia/Brisbane | UTC+10 |
| Melbourne | Australia | Australia/Melbourne | UTC+10 |
| Sydney | Australia | Australia/Sydney | UTC+10 |
| Auckland | New Zealand | Pacific/Auckland | UTC+12 |
Tips for scheduling across time zones
- 1
Anchor on the overlap, not on one person’s morning — the score strip shows the hour that works for the most people.
- 2
Watch half-hour zones: a “clean” 14:00 UTC slot is 19:30 in India, so check the grid, not just the hour.
- 3
Rotate recurring meeting times so the same city isn’t always taking the early or late call.
- 4
Double-check dates near DST switches (March & November in the US, late March & October in the EU) — offsets can differ by an hour.
- 5
Export the .ics file: because it stores UTC, every calendar app converts the meeting to the attendee’s own zone automatically.
- 6
If there’s no overlap inside 9–17, widen the working range or split the meeting into two shorter sessions.
Time zone meeting planner FAQ
What is a time zone meeting planner?
A time zone meeting planner lays every attendee’s local working day on top of a single 24-hour grid so you can instantly see where they overlap. TimeZonePlanner shows each location’s local time for every UTC hour, highlights everyone’s working hours, scores each hour by how many people are available, and recommends the best window — then exports it as a calendar invite.
Does the planner handle daylight saving time (DST)?
Yes. Every offset is computed at runtime from the IANA time zone database via your browser’s Intl API, so DST transitions are applied automatically for the exact date you pick. The static reference table below shows standard (non-DST) offsets only.
What is the best time to meet across time zones?
The best time is the hour where the most attendees fall inside their local 9:00–17:00 working day. For US–Europe teams that is usually 13:00–16:00 UTC; for US–Asia teams it is often early-morning US Pacific time. Use the “best overlap” band above to find it for your exact set of cities.
How do I export the meeting as a calendar invite (.ics)?
Pick your date, start hour and duration, then click “Download .ics invite”. The file stores the meeting in UTC, so Google Calendar, Outlook and Apple Calendar each display it in the attendee’s own local time. Open the file or attach it to an email invitation.
Why do some time zones have :30 or :45 offsets?
Not every country aligns to whole-hour offsets. India (UTC+5:30), Nepal (UTC+5:45) and parts of Australia such as Adelaide (UTC+9:30) use half or quarter-hour offsets, which is why a meeting that looks round in one city can land at :30 in another. The grid displays these precisely.
Is this time zone converter free to use?
Yes. TimeZonePlanner is completely free, runs entirely in your browser, and stores nothing on a server. Add as many locations as you like and export unlimited .ics invites.