Find the best meeting times across multiple cities. See overlapping business hours across any combination of time zones.
Acceptable windows (some early/late start)
| 🇬🇧 London (base) | 🇺🇸 New York | 🇯🇵 Tokyo |
|---|---|---|
| 12am | 7pm-1d | 8am |
| 1am | 8pm-1d | 9am |
| 2am | 9pm-1d | 10am |
| 3am | 10pm-1d | 11am |
| 4am | 11pm-1d | 12pm |
| 5am | 12am | 1pm |
| 6am | 1am | 2pm |
| 7am | 2am | 3pm |
| 8am | 3am | 4pm |
| 9am | 4am | 5pm |
| 10am | 5am | 6pm |
| 11am | 6am | 7pm |
| 12pm | 7am | 8pm |
| 1pm | 8am | 9pm |
| 2pm | 9am | 10pm |
| 3pm | 10am | 11pm |
| 4pm | 11am | 12am+1d |
| 5pm | 12pm | 1am+1d |
| 6pm | 1pm | 2am+1d |
| 7pm | 2pm | 3am+1d |
| 8pm | 3pm | 4am+1d |
| 9pm | 4pm | 5am+1d |
| 10pm | 5pm | 6am+1d |
| 11pm | 6pm | 7am+1d |
With a team spread across London, Singapore, and New York, there is no overlap of normal business hours. London and Singapore share 09:00–17:00 overlap only when London evening (17:00–18:00) meets Singapore morning (01:00). The best compromise meeting window is early London morning / Singapore afternoon — though someone always ends up at an inconvenient hour.
The US, EU, UK, and Australia all change their clocks — but on different dates. The US typically changes on the first Sunday in November, the UK on the last Sunday in October, and the EU on the last Sunday in October. During the transition weeks, the offsets between regions change, invalidating standing meeting times.
Not all time zones are offset by whole hours. India is UTC+5:30, Nepal is UTC+5:45, Iran is UTC+3:30, and Australia's Northern Territory is UTC+9:30. Always verify exact offsets rather than assuming whole-hour differences.
When scheduling across time zones, it's generally considered polite to rotate inconvenient times fairly rather than always expecting the same party to take the difficult slot. A recurring meeting that always favours one region's convenience signals an imbalance of power in the relationship.
For complex multi-party scheduling, tools like World Time Buddy, Every Time Zone, and Calendly's time zone detection handle the complexity automatically. For ad hoc conversions, this tool or a quick search works well.
Find the best meeting times across multiple cities and time zones. See when business hours overlap so everyone can meet at a reasonable time.
London + New York overlap
14:00–18:00 London = 09:00–13:00 New York
London + Singapore overlap
Very limited — 09:00 Singapore = 02:00 London
The International Date Line is not a straight line — it bends around Russia, Kiribati, and Samoa so that countries don't get split across two calendar days. Kiribati, which spans both sides of the anti-meridian, lobbied in 1994 to move the Date Line east so the entire nation shares the same date.
Begin with the decision or task you want this page to support. Find the best meeting times across multiple cities. See overlapping business hours across any combination of time zones. Write down the expected kind of answer before entering values, so you can notice if a default, unit, or mode does not fit your situation. If more than one input could change the result, hold the others steady while you test one value at a time. This makes it easier to understand what the tool is responding to instead of treating the first number on screen as a complete recommendation.
Follow the page instructions in order and check the labels as you go. The first step is: Add the cities you need to schedule a meeting between.. Next, the grid shows all 24 hours for each location simultaneously. Use consistent units and a consistent time period, and avoid replacing an unknown value with zero unless the tool explicitly treats zero as a valid input.
The page's worked example is a reference point, not a forecast for every situation. It shows how the inputs lead to an output: 14:00–18:00 London = 09:00–13:00 New York Compare the assumptions in that example with your own values, then check the units, rounding, and any optional settings before comparing results. If your scenario differs, describe that difference explicitly rather than expecting the example's answer to transfer unchanged.
Use the result as one part of a decision rather than a substitute for the context around it. If you are comparing alternatives, run each one with the same definitions and change only the factor you want to compare. For repeated tasks, save a short note of the inputs and date; this makes later results easier to reproduce and helps distinguish a real change from a difference in how the values were entered.
A useful final check is to compare the answer with a second route: a hand calculation, a known example, an official reference, or the instructions for the service that will receive the result. One point worth checking on this page is “Does the planner account for daylight saving time?” A close match on a simple case can confirm the basic method; it does not prove that every complex case is covered.
For low-consequence tasks, a quick spot check may be enough. For anything that affects money, health, safety, access, or a deadline, verify the result against an authoritative source or the system that will use it. The tool can make routine work faster, but you remain responsible for confirming that the inputs and intended use are appropriate.
The displayed relationship uses time-zone rules and the current date context, but offsets can change during daylight-saving transitions and historical rules are not identical everywhere. Recheck a recurring meeting near a clock change and include the date in invitations. Name the city or IANA time zone rather than relying on an abbreviation such as CST.
Start with the overlap between working hours, then look for a slot that avoids the extremes of the day for every participant. When no perfect overlap exists, rotate the inconvenient time, record the meeting in each person’s local zone, and offer an asynchronous alternative. A technically possible time is not automatically a considerate one.
Cities may use half-hour or quarter-hour offsets, and daylight-saving rules can differ by country or region. Political decisions can also change future rules. Select the precise city or region, confirm the date, and check the calendar invitation after saving it. Do not manually add hours when a time-zone-aware calendar can convert it.
Choose whether the meeting should stay at one location’s local time or at a fixed instant for everyone, because daylight-saving changes can shift the other participants’ local hour. Include the date, city or IANA time zone, and a calendar-zone-aware invitation. Recheck the series before seasonal clock changes and tell attendees how exceptions will be handled.