World Clock & Meeting Planner
See the time in several cities at once — and find the window when everyone’s actually awake. Add up to six cities, pick a reference, and read off a call time that works for all of them.
- Free, no sign-up
- Works worldwide
- Instant results
Loading clocks…
Times update live and account for daylight saving automatically — offsets are read from each city’s time zone, not stored, so they won’t go stale. The working-hours band (9 am–6 pm) is a sensible default for finding a call time; adjust for your own schedule.
How do you find a meeting time across time zones?
Line each city’s working day up against one shared clock and look for where they overlap. This planner does that for you: add your cities, and where every city’s bar falls in the 9 am–6 pm band, everyone’s comfortably available — shown above the bars in your reference city’s time. For a quick example, 4 pm in London is mid-morning in New York and early evening in much of Europe, but the middle of the night in East Asia.
Methodology: Each city’s UTC offset is read live and DST-aware from its IANA time zone (computed, never hardcoded), then its day is laid out as a 24-hour band aligned to a reference city: asleep before 7 am or after 10 pm, comfortable working hours 9 am–6 pm, and fringe hours in between. The planner marks every reference hour where all selected cities fall in working hours — or, failing that, where all are at least awake — and reports it in the reference city’s local time. The 9-to-6 working window is a stated convention, not a hard rule; the bars show exactly whose early morning or evening any given slot would use. How we test & calculate.
When two cities isn’t enough
Comparing your time with one other place is easy. Coordinating a call across three, four or five — a team spread over continents, family scattered around the world, colleagues you’re travelling to meet — is where it gets fiddly, because every pair has a different gap and the overlaps aren’t obvious. This tool lays every city out on one shared clock so the answer is something you can simply see.
Read it like a chart
Each city gets a bar for the day, coloured green where it’s working hours, amber at the early and late fringes, and dark where people are asleep. Stack them up and scan downwards: a column that’s green all the way down is a time when everyone is comfortably available. The planner finds that window for you and states it in your reference city’s time, so there’s no mental arithmetic.
Always right, never stale
Time zones are deceptively tricky — daylight saving shifts them twice a year, and not on the same dates everywhere — so every offset here is read live from the city’s zone rather than stored. That means the clocks are correct through the changeover seasons, when two places can be an hour closer or further apart than usual. Pair it with the best-time-to-call tool for one-on-one calls, or the jet-lag planner when you’re the one crossing the zones.
Frequently Asked Questions
How is this different from the time-difference tool?
The time-difference and best-time-to-call tools compare you with one other city. This one handles several at once — add up to six cities and see them side by side, with a band for each showing who’s asleep, who’s at the fringe of the day, and who’s in working hours. That makes it the right tool when you’re coordinating a call across a whole team or trip spanning three or more zones, not just two.
How does it find a good meeting time?
Each city gets a 24-hour bar aligned to your reference city’s clock. Where every city’s bar is green — in the 9 am to 6 pm working window — that column is a time when everyone’s comfortably available, and it’s called out above the bars in the reference city’s local time. If there’s no fully-green overlap, it falls back to when everyone is at least awake, and if the cities are simply too far apart it tells you so.
Does it handle daylight saving time?
Yes, automatically. Each city’s offset is read live from its time zone rather than stored as a fixed number, so when a region springs forward or falls back the clocks and the overlap shift with it — and there’s nothing to go out of date. It’s also why two cities that are normally, say, five hours apart can briefly be four or six around the changeover dates, which this reflects.
What does the “reference city” do?
It sets the clock that the bars line up against — the hour scale along the top is in the reference city’s local time, and the suggested meeting window is given in that city’s time too. Set it to wherever you are (or wherever the meeting is being hosted from) so the times read naturally. You can change it at any time without affecting which cities are shown.
Why only the working-hours definition of 9–6?
It’s a sensible default for finding a time that’s polite for everyone, but it won’t fit every situation — some people start at seven, some are happy to take an evening call. Treat the green “working hours” band as a guide rather than a rule: the amber fringe hours (7–9 am and 6–10 pm) are perfectly workable for many people, and the bars let you see exactly whose evening or early morning you’d be using.