Convert the same moment to another local time

A meeting can take place on the same instant worldwide while appearing on different clock times, and sometimes different dates. This converter starts with the local date and time in a source zone and shows how that moment appears in the destination zone. Use it for a call, a live event, or an appointment involving people in different regions.

  1. Enter the source date and time

    Use the date and clock time stated by the organiser. The date matters because seasonal clock changes can alter the conversion.

  2. Choose the source zone

    Select the named zone where that local time applies. Do not assume it is the same as your device’s zone.

  3. Choose the destination zone

    Select Calculate and read the destination date as well as the time. A conversion can cross midnight.

A straightforward UTC example

The same instant on 15 January 2026
Time zoneLocal dateLocal time
UTC15 January 202612:00
Asia/Karachi15 January 202617:00
Asia/Tokyo15 January 202621:00
America/New_York15 January 202607:00

Karachi is five hours ahead of UTC in this example, so noon UTC becomes 17:00. New York is five hours behind UTC on that January date, giving 07:00. A conversion checked for January should not automatically be reused for July: New York observes daylight saving, while Karachi does not.

Why named zones are better than a fixed offset

A name such as America/New_York identifies a region with rules that can change across the year. An offset such as UTC−05:00 describes only a difference from UTC. The converter uses your browser’s Intl time-zone data to apply the named zone’s rules for the selected date. Abbreviations such as CST are less useful because more than one region uses them.

Missing and repeated local times

During a spring-forward transition, some local times never occur. If you enter one of those times, this tool rejects it so you can choose a real local time. During a fall-back transition, the same local clock time may occur twice. The converter can resolve that repeated time to either occurrence, so it cannot identify a specific occurrence from the clock reading alone.

When an event falls inside that repeated hour, confirm its UTC time or offset with the organiser. For routine meetings, choosing a time outside a transition window avoids the ambiguity. Read the daylight saving guide for examples of how the missing and repeated hours arise.

Sharing the result

Send the full event date and a named time zone with an invitation. For a recurring meeting, check dates around each region’s clock changes because countries do not all change on the same weekend. A single conversion does not create or manage a recurring schedule. The scheduling across time zones guide covers that planning step.