World Time Meeting Planner: How to Find a Meeting Hour Across Two Cities
Reviewed by the FreeOnline.fyi team · Updated 2026-09-16
Pick two cities, then pick a date
Most time-zone tools answer "what time is it over there?" The World Time Meeting Planner answers a narrower, more useful question: on this specific date, which hours fall inside a normal working day in both places at once? Everything on the screen flows from three inputs sitting in one card at the top.
The two city selectors are searchable dropdowns backed by a bundled list of roughly 60 major cities, each mapped to an IANA time-zone ID. There is no network lookup behind them, which is why results update the instant you change something. The second selector defaults to a city in a different zone from the first, so the tool never opens on a useless zero-offset comparison.
The date field is the one people skip, and it is the one that causes embarrassing invites. Daylight saving changes are not simultaneous worldwide. London and New York sit five hours apart for most of the summer, four hours apart for the week between the UK's late-October change and the US change in early November, then five hours again. Move the date into that gap and the overlap window really does shift. That is exactly what the IANA time zone database rules are there to model.
Read the overlap timeline strip
Under the headline result sits a horizontal strip of 24 chips, one per hour, laid over a soft daylight band. Chips filled with the accent color are hours where both cities are inside 08:00–18:00 local time — the tool's definition of a workable hour. The headline above them states the window in both clocks, for example "Best overlap: 15:00–18:00 (your time) / 09:00–12:00 (their time) — 3 hours."
Run New York against Berlin on a summer date and you get six hours of offset, so the overlap is four hours: 08:00–12:00 in New York, 14:00–18:00 in Berlin. Switch to San Francisco against London, an eight-hour gap, and the accent block shrinks to two hours, 08:00–10:00 Pacific, 16:00–18:00 UK. The strip makes that squeeze visible at a glance in a way a pair of clock faces never does.
Because everything recomputes live, the strip is worth playing with. Swap the second city by one letter, flip the date forward a month across a DST boundary, or check what happens when the gap crosses an awkward number like seven hours. There is no submit button and no page reload, so experimenting costs nothing.
Decode the paired local-times table
The table below the strip is the part to screenshot into your calendar invite. Every hour of the chosen date gets one row, with City A's local time, City B's local time, a day-shift marker (+1 or −1) where the two cities sit on different calendar days, and both UTC offsets. Overlapping rows are highlighted to match the accent chips above.
The UTC offset columns are the quiet workhorses. They let you spot half-hour and quarter-hour zones at a glance — India at +05:30, Nepal at +05:45, Adelaide at +09:30 — instead of wondering why the numbers refuse to line up in whole hours. They also let you verify that the offset the tool applied matches what you expect; the official U.S. time service from NIST is a reasonable cross-check if something looks off.
Use the table to find a named hour rather than just a window. If a colleague's standup is at 10:00 their time, scan their column until you find it and read the same row across. If the day-shift column shows +1 for them, that row is tomorrow for them, which is fine for an early-morning call in one city and a headache in the other.
When no working hour exists
Some pairs simply never overlap inside 08:00–18:00. Sydney against New York is the classic case: a 14-hour summer gap puts New York's entire working day between 22:00 and 08:00 Sydney time. The tool does not pretend otherwise. It falls back to showing the closest two-hour window and flags it clearly as outside normal hours.
We built that fallback deliberately, because the alternative — silently returning a fake "best time" — is how people end up on a 03:00 call without realising it until the invite lands. A visible warning is more useful than a tidy answer.
When you hit this case, the honest options are rotation (someone takes the early or late slot each cycle), asynchronous handovers with recorded updates, or splitting the meeting into two shorter regional sessions. No scheduling tool removes a 14-hour distance; it just tells you the truth about it faster.
Common mistakes worth avoiding
The most frequent error is treating an offset as a constant. Offsets change on different dates in different countries, sometimes on different weeks, and the southern hemisphere flips opposite to the north. If you copy a number from a chat message written in March, re-check it for a November date rather than trusting the arithmetic.
The second is trusting the city label over the actual zone. The tool uses IANA zone IDs, so places that skip daylight saving — Arizona, Queensland, and others — are handled correctly behind the scenes, but it is still worth confirming which zone a teammate actually observes rather than assuming from a city name. If a new contractor's location is genuinely unclear, an IP Address Lookup can hint at the region, though it is a rough signal and never a substitute for simply asking.
The third is edge-hour sloppiness. A window ending at 18:00 means the 18:00 row is the end of the working day, not a free hour. And the tool knows nothing about lunch breaks, public holidays, school pickups, or Friday afternoon norms in a particular office. Treat the highlighted block as a candidate range to narrow by hand.
Verify before you send the invite
The planner is a fast filter, not an authority. Its job is to reduce a 24-hour day to two or three plausible hours in about ten seconds. Your job is to confirm those hours against the two humans involved, especially around DST transition weekends when a single hour can appear or vanish.
Before committing, check the date twice, glance at the day-shift column so nobody is booked on the wrong date, and confirm that neither city has a public holiday that day. If you are coordinating more than two regions, run the pairs separately and look for an hour that appears in every result — that is a far more reliable method than averaging offsets in your head.
If you want more utilities for distributed work, browse the rest of FreeOnline.fyi. Everything runs in the browser without an account, and the meeting planner in particular is built to be opened, used, and closed in under a minute.