Meeting time-zone planner

Compare one proposed meeting instant across participant time zones.

Compare meeting times

Enter one meeting time and two UTC offsets to verify the conversion before sending an invitation.

Enter or select values to calculate a result.

The calculation runs in your browser. Values entered here are not submitted to this site.

What it means

Compare one proposed meeting instant across participant time zones.

How to calculate or use it

Choose one source date and time, convert it to an instant, then render that instant in every participant zone.

Important details

UTC offsets alone do not encode future daylight-saving rules; named IANA zones are safer for scheduled meetings.

A reliable method

Compare one proposed meeting instant across participant time zones. A dependable answer starts by defining the reference and convention before doing the arithmetic.

  1. Define the reference

    Use one meeting instant anchored to the first participant's stated UTC offset. Write it down when another person must be able to reproduce the answer.

  2. Check the inputs

    Use the full date, local time and offset for the source participant, then select the destination offset.

  3. Apply the calculation

    Convert the source time to UTC once, then apply the destination offset to that same instant.

  4. Label the result

    Check the destination date as well as the clock time and state every participant's local date in the invitation.

Worked example

A meeting at 9:00 AM at UTC−5 corresponds to 2:00 PM UTC and 10:00 PM at UTC+8. The destination may be on another date near midnight.

How to interpret the answer

For meeting time-zone planner, the useful answer includes its assumptions. Check the destination date as well as the clock time and state every participant's local date in the invitation.

Accuracy checklist

  • Use a complete date whenever the result can cross midnight or a calendar boundary.
  • State the time zone or local-time basis instead of leaving it implied.
  • Label inclusive, exclusive, elapsed-time or calendar-based counting.
  • Recheck future results when civil-time or organizational rules may change.

Common mistakes

  • Using a familiar shortcut without checking whether it matches the guide's calendar convention.
  • Fixed offsets do not automatically model daylight-saving changes; use named IANA zones for recurring or future meetings.
  • Sharing only the final number without the reference date, zone, unit or rounding rule.

Frequently asked questions

What is the quickest practical way to use meeting time-zone planner?

Start with one meeting instant anchored to the first participant's stated UTC offset. Use the interactive tool on this page, then check the result against the method and limitations below.

What can make a meeting time conversion result inaccurate?

Fixed offsets do not automatically model daylight-saving changes; use named IANA zones for recurring or future meetings.

Does the calculator send my entries to the server?

No. The interactive calculation runs in the browser. For a result you plan to share, record the relevant date, time zone and counting convention alongside it.

Related meeting time conversion guides