Time Zone Meeting Planner
Plan a meeting across time zones: enter a date and time in your home zone and each participant's IANA time zone, and see everyone's local date, local time and whether it lands in their working hours.
Input
The date as it reads in your home time zone.
24-hour clock, e.g. 14:30.
The time zone the date and time above are given in.
One IANA zone name per line (comma-separated also works).
Hour (0–23) when the working day begins.
Hour (1–24) when the working day ends.
Output
| Time zone | Local date | Local time | Status |
|---|---|---|---|
| No data yet | |||
Guides
Scheduling a call across time zones is where good intentions go to die. Someone proposes "3 PM" and everyone quietly does the mental arithmetic — badly. The Time Zone Meeting Planner does that arithmetic for you: pick one date and time in your home zone, list everyone's location, and instantly see the local date, local time, and whether it lands inside working hours for each participant.
How to use it
- Set the meeting date and time. Enter them exactly as they read in your own
(home) time zone, using a 24-hour clock for the time —
14:30, not2:30 PM. - Choose your home time zone. This is the reference the date and time are
measured against. Start typing to search the full IANA zone list
(
America/New_York,Europe/London,Asia/Kolkata, …). - List the participants' time zones, one IANA name per line (commas work too). Each becomes a row in the schedule.
- Adjust the working-hours window if 9-to-5 isn't right for your team, and flip on 24-hour time if you prefer it.
The result is a table with one row per participant showing their local date
(with a +1 day / -1 day marker when the meeting crosses midnight for them),
their local time, and a status:
- Business hours — the time falls inside the working window you set.
- Early / late — within two hours either side of the window; workable, but not ideal.
- Outside hours — before the early buffer or after the late one; likely an evening or overnight ask.
A summary line at the top restates the meeting time in your home zone with its UTC offset, so you always have a canonical reference to paste into an invite.
Does it handle daylight saving time?
Yes. Because it works with IANA zone names rather than fixed abbreviations, the
offset is resolved for the actual meeting date. America/New_York returns
UTC-05:00 in January and UTC-04:00 in June automatically — no manual EST/EDT
juggling. The UTC offset shown next to each zone is the one in effect on the
meeting date.
Which time zone names can I use?
Any IANA time zone identifier —
the Region/City form such as Europe/Paris, Asia/Singapore, or
Australia/Sydney, plus UTC. The home-zone picker lists every zone your device
supports; the participant box accepts the same names, one per line.
Is my data private?
Completely. All conversions run in your browser using the built-in
Intl date facilities — nothing about your meeting, dates, or participant list
is ever sent to a server.
Use it from code
From 3 credits per callREST API
curl -X POST https://api.iotools.cloud/v1/tool/time-zone-meeting-planner \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"meetingDate": "2026-06-17",
"meetingTime": "14:00",
"homeZone": "America/New_York",
"participants": "America/New_York\nEurope/London\nAsia/Tokyo",
"businessStart": "9",
"businessEnd": "17"
}'Swap in your own key from your account. The tool's fields are the body — no wrapper.
Ask an AI agent
Use the IOTools `time-zone-meeting-planner` tool (Time Zone Meeting Planner) on this input:
YOUR_INPUT_HEREPaste this at any agent connected to the IOTools MCP server, then add your input.