Timezone Meeting Planner
Map a meeting hour in UTC to local times across a list of UTC offsets, with a worked example for a 15:00 UTC call. Handles half-hour zones.
Results
Local times· 7 zones
- UTC offset
- -8
- Local time
- 7:00 AM
- UTC offset
- -5
- Local time
- 10:00 AM
- UTC offset
- +0
- Local time
- 3:00 PM
Showing 3 of 7 rows — swipe the schedule below for the full table.
| UTC offset | Local time |
|---|---|
| -8 | 7:00 AM |
| -5 | 10:00 AM |
| +0 | 3:00 PM |
| +1 | 4:00 PM |
| +5.50 | 8:30 PM |
| +8 | 11:00 PM |
| +9 | 12:00 AM |
You might also need
Educational estimates · not financial advice · free, no signup
Formula / how it works
Local hour = (UTC hour + offset) mod 24. Enter offsets as a comma list (e.g. -5, 0, 5.5, 9).
Detailed guide
What it is, how to use it, how to read the numbers, common mistakes, a worked example, formulas, and FAQs.
What this calculator is
Scheduling across time zones is easier if you pick the meeting time in UTC and then translate it for everyone. This planner takes a meeting hour in UTC and a list of UTC offsets and returns the local clock time for each. It handles half-hour offsets like +5.5 for India and wraps correctly across midnight. Daylight saving changes offsets for part of the year in some regions, so use the offset currently in effect for each location. The tool does not look up zones automatically; it applies the offsets you type. Use it to find a window that is not at 3 a.m. for anyone.
When to use / who it helps
- You are scheduling a call among colleagues in several countries.
- You want to check how a UTC time looks locally.
- You are looking for a reasonable shared meeting hour.
- You are planning a livestream or release at a fixed UTC time.
- You need to explain an event time to participants.
How to use
Steps
- Enter the meeting hour in UTC, from 0 to 23.
- Enter the offsets for each location, separated by commas, for example −8, −5, 0, 1, 5.5.
- Read the local time for each offset.
- Look for results between about 8 and 20 for all participants.
- Adjust the UTC hour until the spread is comfortable.
- Check for daylight saving differences before confirming.
How to interpret results
- A negative offset means the location is behind UTC, so local time is earlier.
- A result such as 20.5 means 20:30.
- A value that wraps to 0 or low numbers is the next day locally.
- The offsets must be current; daylight saving changes them seasonally.
- The tool does not know country names, only offsets you enter.
Common mistakes & gotchas
- Using standard-time offsets during daylight saving time.
- Forgetting half-hour or 45-minute offsets.
- Reading a wrap-around time as the same day.
- Entering the sign of the offset the wrong way.
- Confirming a time without checking dates, since the day may differ.
Worked example
Worked example — 15:00 UTC for seven offsets
- Offset −8: 15 − 8 = 7:00.
- Offset −5: 15 − 5 = 10:00. Offset 0: 15:00. Offset +1: 16:00.
- Offset +5.5: 15 + 5.5 = 20.5, which is 20:30.
- Offset +8: 23:00. Offset +9: 15 + 9 = 24, which wraps to 0:00 the next day.
Result: A 15:00 UTC meeting is 7:00, 10:00, 15:00, 16:00, 20:30, 23:00 and midnight (next day) in those zones.
To load the form's own demo values, tap Try example above the Calculate button.
How to calculate / formula
Local hour = (UTC hour + offset) mod 24. Enter offsets as a comma list (e.g. -5, 0, 5.5, 9).
Frequently asked questions
What is UTC?
Coordinated Universal Time, the reference time standard used to define time zones.
How do I write India's offset?
+5.5, since India is 5 hours 30 minutes ahead of UTC.
Does the tool handle daylight saving time?
Not automatically. Use the offset currently in effect.
What is a good meeting hour for several zones?
Choose a UTC time that lands between about 8:00 and 20:00 for most participants, accepting some compromise.
Why is one result the next day?
Adding the offset can pass midnight, so the local date is one day later.
Can I use negative half-hour offsets?
Yes, such as −3.5 for some locations.