Meeting Time Across Time Zones
Paste one person per line — a name, their UTC offset, and the hours they are willing to meet — then give a proposed time and the offset it is stated in. You get that time on every person's own clock with the day it falls on marked, a plain list of who it inconveniences and by how much, and every slot that fits inside everybody's hours. Offsets are typed in rather than picked from a list of cities, and that is deliberate: daylight-saving rules and standard offsets are changed by governments several times a year, so a zone table baked into an offline tool goes quietly wrong within months, while an offset is something anyone can read off their own phone in five seconds. Half-hour and three-quarter-hour offsets are handled exactly — +05:30, +05:45 and +12:45 are ordinary cases here — and so is the off-by-one-day error that ruins more international calls than anything else. Night-shift windows that cross midnight work. If no time suits everyone it says so plainly and shows the least-bad options with the names of whoever is outside their hours and by how many minutes, because sometimes the honest answer is that one person has to take it early. Runs entirely on your device; nothing is uploaded and no clock is read.
Try it now
Worked example
Learn the method
Inputs
- Proposed time
15:00 - …stated in UTC offset
+00:00 - Meeting date
2026-09-15 - Meeting length (min)
60 - Default hours if a line omits them
09:00-17:00 - Search in steps of
30 minutes / 60 minutes / 15 minutes
Frequently asked
Why do I type offsets instead of choosing cities?
Because a city list would have to carry a copy of the world time-zone database, and that database changes several times a year — governments move daylight-saving dates, and occasionally standard offsets, sometimes with only weeks of notice. An offline copy starts going wrong within months and gives you a confident, wrong answer. A UTC offset is something each person can read off their own phone in seconds, cannot be misread, and is true for the date they are looking at. The arithmetic is the error-prone part, and that is the part done here.
Does it handle daylight saving?
No, and it will not pretend to. It uses exactly the offsets you type. If your meeting is near a date when clocks change somewhere, ask each person for the offset they will be on that day. Clock changes do not happen on the same weekend in every country and the southern hemisphere shifts the opposite way, so a recurring call across a change date moves for some people and not for others.
What offsets can I write?
+5:30, -08:00, +9, UTC+2, GMT-3, 0, Z, +0545 and +5.75 are all accepted. Anything from -12:00 to +14:00 works, because +13 and +14 are real. What is never accepted is a zone name or abbreviation: "EST" is used for two different offsets in different parts of the world, so it is rejected with a message rather than guessed at, and an unreadable offset is never quietly read as UTC.
What format do the participant lines take?
One person per line: name | UTC offset | hours. For example "Priya | +5:30 | 09:30-18:00". Pipes are clearest, but tabs and commas work too. The hours are optional — leave them off and the default-hours field is used, and the table marks which rows that happened to. Blank lines and lines starting with # are ignored.
Can somebody's hours cross midnight?
Yes. 22:00-06:00 is read as a night-shift window of eight hours starting at ten in the evening, not as an error and not as a backwards window. Overlap searching treats it exactly like any other window.
What if no time suits everybody?
It says so in those words, and then shows the least-bad options ranked by the total number of minutes anyone is outside their hours, naming each person, the time on their clock, and how far outside they are. It does not invent a compromise or quietly widen anyone's hours. Options that cost the same are listed earliest-first, which is an arbitrary tie-break and is labelled as one.
How does it decide the day?
Every time is turned into an absolute number of minutes, then split back into a date and a clock time using floor division, so an instant before midnight lands on the previous day rather than on an impossible negative time. The day marker is relative to the meeting date you gave. It can legitimately read two days later: from -12:00 to +14:00 is a twenty-six-hour spread, so the same instant really can be Monday for one person and Wednesday for another.