How to Convert Time Zones: UTC Offsets & Examples

To convert a local time correctly, you need the source date, time and named time zone, plus the destination zone. The date matters: a city's UTC offset can change with daylight saving time (DST), and two countries may change their clocks on different weekends.

Open the searchable time zone converter to compare a dated meeting and export its instant as a one-hour calendar event. Sharing or saving the calculation preserves its settings locally; exported calendar files do not create a recurring series.

The Conversion Method

1. Resolve the source local date and time to an exact instant using its named zone, such as America/New_York.
2. Display that same instant in the destination zone, such as Europe/London.
3. Keep the destination date as well as its clock time. Midnight crossings can change the calendar day.

If the local time is valid and unambiguous, the equivalent arithmetic is destination time = source time + destination UTC offset - source UTC offset. Offsets must be those at the same instant, not today's offsets applied to a future meeting.

New York to London: The Date Changes the Answer

At 14:30 in New York on October 7, 2026, London is at 19:30 on the same date. On October 28, 2026, that same New York clock time maps to 18:30 in London. The difference changes from five hours to four during the countries' different clock-change schedules.

Open the October 28 example. Search for a city or IANA zone name, then choose the matching zone in the selector. The converter still compares two zones at a time; it is not a multi-city meeting planner.

Minutes and Date Crossovers

Some offsets are fractional hours. In January, London at 14:00 maps to Mumbai at 19:30, reflecting a five-and-a-half-hour difference. Preserve the minutes instead of rounding to a whole hour.

Los Angeles at 09:00 on January 12, 2026 maps to Tokyo at 02:00 on January 13. In July, the corresponding Tokyo time is 01:00 the next day because Los Angeles has a different seasonal offset.

Missing and Repeated Local Times

At a forward clock transition, some local times do not exist. New York's March 8, 2026 at 02:30 is such a gap; DigiCalc rejects it rather than silently moving the meeting.

At a backward transition, a local time can happen twice. New York's November 1, 2026 at 01:30 refers to two instants one hour apart. Choose the first or second occurrence explicitly. Temporal's time-zone documentation explains these ambiguities.

Planning a Call

The converter shows hourly samples for the selected source date and highlights when both local clocks fall between 09:00 and 17:00. Each sample is converted separately, so a DST transition during that day is not treated as a fixed 24-hour offset. This highlight does not exclude weekends, holidays or personal working schedules.

For a scheduled event, include both local dates and a named zone in the invitation. A recurring meeting can move relative to colleagues' clocks; check each affected date. The countdown calculator can preserve a specific event instant and export a calendar event.

Sources and Scope

Worked dates and transitions are generated or checked using DigiCalc's shared Temporal-based conversion engine. The named-zone rules come from the runtime's time-zone data; future legal changes can alter future results. This is an automated technical check, not a guarantee about future government decisions.

• TC39 Temporal: time zones, UTC offsets and disambiguation.

For date intervals rather than local clock conversions, see days between two dates. For events, see counting down to an event.