Scheduling across time zones is where good collaborations lose their first hour to confusion. This free solver takes one meeting time in UTC and shows it instantly in every collaborator’s zone, so nobody has to do mental arithmetic before replying to a scheduling email.
What the tool does
You enter a meeting date and time in UTC, tick the zones your collaborators live in, and the tool returns a table with the local time for each zone. The zone list covers the major research hubs, from Los Angeles to Sydney, with fixed offsets from UTC. The result is a single, checkable table you can paste into an email or a calendar invite description, which removes the most common scheduling error: one person silently converting from the wrong base time.
How to use it
Write the meeting time in UTC, using the format YYYY-MM-DD HH:MM, for example 2026-11-10 15:00. Tick only the zones you need, so the table stays readable, and press the button. Read down the table and look for times outside working hours, such as a 02:00 start for one collaborator, and move the meeting if anyone is badly affected. Send the final time with its zone labels attached, not just a bare hour, so nobody has to guess which zone you meant.
Worked example
A meeting set for 2026-11-10 at 15:00 UTC shows as 15:00 in London, 16:00 in Berlin, 20:00 in Dubai, 20:30 in Delhi, 23:00 in Singapore, and 10:00 in New York. The table makes the trade-off visible at once: the time works well for Europe and the Americas but runs late for Singapore. Moving the meeting to 13:00 UTC would give Singapore 21:00 and New York 08:00, which may be fairer overall. The solver does not choose for you, but it shows the cost of each option plainly.
Reading the results honestly
The times use fixed offsets, which means zones that observe daylight saving may be one hour different on your actual date. London and New York, for example, do not change their clocks on the same weekend, so the gap between them changes during the year. Always confirm the final meeting with a calendar invite that carries the time zone, and ask collaborators in tricky zones to confirm the local time back to you. A two-minute confirmation beats a missed meeting.
Honest limits
This tool converts times; it does not know public holidays, working hours, or personal availability, and it cannot send invitations. Its zone list is a practical subset, not every zone on Earth, and its offsets are fixed rather than pulled from a daylight-saving database. For recurring meetings across a clock-change boundary, re-run the solver after the change instead of trusting the first result all year.
Practical tips
Rotate meeting times when a collaboration spans many zones, so the same person is not always the one joining at midnight. Keep a standing note of each regular collaborator’s zone and preferred window, and check it before proposing times. When a meeting must be awkward for someone, say so openly and offer notes or a recording, which keeps goodwill intact.
When no time works for everyone
Some collaborations span so many zones that no single hour suits all members, and chasing a perfect slot wastes more time than the meeting itself. In that case, split the meeting: hold one session for the eastern half of the team and one for the western half, with shared notes between them, or make the meeting optional for the worst-affected members and send them a recording. Record decisions in writing regardless of who attended, so nobody’s absence becomes a veto later. A meeting that works badly for one person every week will slowly lose that person; a meeting designed around the constraint keeps the collaboration whole.
Related tools
Spanish version: Solucionador de Reuniones en Zonas Horarias Gratis y Online · All free online tools.
Embed this tool on your website — free
Copy the code below to add this working tool to your own page. A small credit link stays with it — that’s all we ask.