🗓️ Meeting Time Zone Planner
By ToolNimba Editorial Team · Updated 2026-06-19
| Time zone | Local meeting time | UTC offset | Hours difference |
|---|
This meeting time zone planner shows what your meeting time looks like for everyone, wherever they are. Pick the date and time in the organizer time zone, add each participant zone from the built-in list, and see the local meeting time, UTC offset and hours difference for every person at once. It is the fast way to find a slot that works across regions without juggling a world clock or doing the maths in your head.
What is the Meeting Time Planner?
Scheduling across time zones is awkward because a single meeting happens at one instant in time, yet that instant reads as a different wall-clock time in every region. A 9:00 AM call in New York is 2:00 PM in London and 10:00 PM in Tokyo, the same moment, three very different local times. This planner pins down that one instant from the organizer side, then renders it through each participant zone so you can see the whole picture in a single table.
The conversion is done entirely in your browser using the JavaScript Intl.DateTimeFormat API with a timeZone option, which reads from the IANA time zone database built into modern browsers. That database carries the real rules for each zone, including its standard offset from UTC and the dates daylight saving time starts and ends. Because the tool evaluates those rules on the exact meeting date, a meeting planned in March is handled correctly even if some zones have already sprung forward and others have not. Nothing is sent to a server, so your plans stay private.
The trickiest part of time zones is daylight saving. Not every country observes it, and those that do switch on different dates, so the gap between two cities is not fixed. London and New York are usually five hours apart, but for a couple of weeks each spring and autumn that gap becomes four or six hours because the two regions change their clocks on different weekends. A planner that resolves the offset on the actual meeting date, as this one does, avoids the classic mistake of assuming the difference never moves.
When to use it
- Scheduling a team standup or client call when people are spread across several countries.
- Checking whether a proposed slot lands in working hours or the middle of the night for remote colleagues.
- Planning a webinar or product launch and sharing the start time as a local time for each region.
- Coordinating an interview, podcast or family video call between people in different time zones.
How to use the Meeting Time Planner
- Set the meeting date and time, entered in the organizer time zone.
- Choose the organizer time zone from the dropdown (use the "Use now" button to set today and your local zone).
- Add a participant time zone row for each region you need to cover.
- Read the table to see the local meeting time, UTC offset and hours difference for everyone, then adjust the time until the slot suits all participants.
Formula & method
Worked examples
A meeting set for 9:00 AM on a July weekday in New York, with participants in London and Tokyo.
- Organizer zone New York in July is on daylight time, UTC-04:00, so 9:00 AM is 13:00 UTC.
- London in July is on summer time, UTC+01:00, so 13:00 UTC is 2:00 PM in London.
- Tokyo has no daylight saving and is UTC+09:00, so 13:00 UTC is 10:00 PM in Tokyo.
- Hours difference: London is +5h, Tokyo is +13h relative to the organizer.
Result: New York 9:00 AM = London 2:00 PM = Tokyo 10:00 PM (same instant).
A meeting set for 3:00 PM on a January weekday in London, with a participant in Los Angeles.
- London in January is on standard time, UTC+00:00, so 3:00 PM is 15:00 UTC.
- Los Angeles in January is on standard time, UTC-08:00.
- Apply the offset: 15:00 UTC minus 8 hours = 7:00 AM in Los Angeles.
- Hours difference: Los Angeles is -8h relative to the organizer.
Result: London 3:00 PM = Los Angeles 7:00 AM, a workable early-morning slot.
Typical UTC offsets for common meeting hubs (standard time, before daylight saving)
| City | IANA zone | Standard UTC offset | Observes DST |
|---|---|---|---|
| Los Angeles | America/Los_Angeles | UTC-08:00 | Yes |
| New York | America/New_York | UTC-05:00 | Yes |
| London | Europe/London | UTC+00:00 | Yes |
| Berlin | Europe/Berlin | UTC+01:00 | Yes |
| Dubai | Asia/Dubai | UTC+04:00 | No |
| Kolkata | Asia/Kolkata | UTC+05:30 | No |
| Singapore | Asia/Singapore | UTC+08:00 | No |
| Tokyo | Asia/Tokyo | UTC+09:00 | No |
| Sydney | Australia/Sydney | UTC+10:00 | Yes |
Rough overlap of standard working hours (9 AM to 5 PM local) for popular zone pairs
| Zone pair | Best overlap window | Notes |
|---|---|---|
| New York and London | 9:00 AM to 12:00 PM New York | Mornings in New York, afternoons in London. |
| London and Singapore | 9:00 AM to 10:00 AM London | Very narrow, early UK morning only. |
| Los Angeles and Sydney | No standard-hours overlap | Use early or late edges, or rotate times. |
| New York and Berlin | 9:00 AM to 11:00 AM New York | Late afternoon in Berlin. |
Common mistakes to avoid
- Assuming the hour gap between two cities never changes. Daylight saving means the difference between regions shifts a few times a year, and only one side may change on a given weekend. Always plan against the actual meeting date, which is exactly what this tool does, rather than a remembered offset.
- Forgetting that the date can roll over. A late-evening meeting in one zone can be the next morning in another. Check the weekday and day shown in the table, not just the clock time, so nobody joins on the wrong calendar day.
- Picking a slot that is the middle of the night for someone. A time that feels normal to the organizer can land at 3:00 AM for a remote colleague. Scan every row for working-hours fit, and for very wide spreads consider rotating the meeting time so the burden is shared.
- Confusing a time zone abbreviation with an offset. Labels like CST or IST are ambiguous and can mean different offsets in different countries. Selecting a city or IANA zone, as this planner does, removes that ambiguity.
Glossary
- Time zone
- A region that keeps a common standard time, defined by its offset from UTC and its daylight saving rules.
- UTC
- Coordinated Universal Time, the global reference time from which every zone offset is measured.
- UTC offset
- How far ahead of or behind UTC a zone is, written like UTC+05:30 or UTC-08:00.
- IANA zone
- A standardized time zone identifier such as America/New_York, used by browsers to look up the correct rules.
- Daylight saving time (DST)
- The seasonal practice of moving clocks forward, usually by an hour, which temporarily changes a zone’s offset.
- Wall-clock time
- The local time a clock on the wall shows in a particular place, as opposed to the underlying UTC instant.
Frequently asked questions
How does the meeting time planner work?
You enter the meeting date and time in the organizer time zone. The tool pins that down to a single instant in time, then displays the same instant as the local time in each participant zone you add, so everyone sees their own correct meeting time.
Does it handle daylight saving time?
Yes. It uses your browser’s built-in IANA time zone database and evaluates each zone’s rules on the actual meeting date, so daylight saving is applied or not applied for each zone exactly as it would be on that day.
How do I find the best time across time zones?
Add every participant zone, then adjust the meeting time and watch the table. Aim for a slot that falls within working hours (roughly 9 AM to 5 PM) in as many rows as possible. For very wide spreads, rotating the time between meetings shares the inconvenience.
Why does the day sometimes change for a participant?
Because a single instant can fall on different calendar days around the world. A 9:00 PM meeting in New York is already the next morning in Tokyo, so the table shows the weekday and date for each zone to make that clear.
Is my meeting information sent anywhere?
No. All conversions run locally in your browser using the Intl.DateTimeFormat API. Nothing about your meeting, dates or participants leaves your device.
Can I plan a meeting for any number of participants?
Yes. Use the Add participant button to include as many time zones as you need. Each one gets its own row showing the local meeting time, UTC offset and hours difference from the organizer.