Time Zone Converter

Convert a date and local clock time from one named time zone to another. Include the event's date so the browser can apply its rules for that date, rather than today's time difference.

Choose a date, time and zones

Source date

Choose a date from 2000 to 2099.

Source time

Use the clock picker or enter a 24-hour time with minutes.

Source zone

Search for a zone or a familiar city, then select an option.

Target zone

Search for a zone or a familiar city, then select an option.

Converted time

Enter a date and time, select the zones, and choose Convert.

Convert one dated local time

Enter the source date and time, choose the zone already stated for that time, then choose the target zone. Search by the visible zone identifier or an available translated city label.
Select Convert. If the source clock reading occurs twice, choose the earlier or later instant using the displayed UTC times and offsets. If the clock skipped that time, enter a different source time.
Read the complete target date and time, not only its hour. Check the source and target offsets, UTC instant and calendar-day shift before optionally copying the qualified result.

A clock reading needs a zone and date

An IANA identifier such as America/New_York describes a region's time rules. A UTC offset such as UTC−04:00 describes the difference at one instant. The offset can change, so a zone name is not a permanent offset.

When a local clock moves forward, some clock readings do not exist. When it moves backward, a reading can identify two different instants. This converter does not silently move a skipped time or choose a repeated-time branch for you.

After the source instant is known, the target date and time are determined by the target zone's rules. A target clock reading can also be repeated, but the displayed UTC instant and offset identify which occurrence is meant.

The day-shift label compares target and source calendar dates, not elapsed hours. Crossing the international date line can produce a two-date shift. This tool does not calculate a meeting duration or travel time.

Date-sensitive examples

For 1 July 2026 at 09:00 in America/New_York, the example rules give 14:00 in Europe/London and 13:00 UTC. On 20 March 2026, the same New York clock time gives 13:00 in London because the regions change seasonal offsets on different dates.

In America/New_York, 1 November 2026 at 01:30 has two occurrences in the example rules: 05:30 UTC with UTC−04:00, or 06:30 UTC with UTC−05:00. Choosing one occurrence is necessary even if both source and target zones are New York.

For 1 January 2026 at 23:30 in Pacific/Niue, the example rules give 3 January at 00:30 in Pacific/Kiritimati. The target is two calendar dates later, although both labels describe the same instant.

Browser rules and supported inputs

Results use the time-zone rules installed in your browser. Governments can change those rules, and a browser may not contain the latest update. Verify critical or future arrangements with the organizer or an authoritative current source; this is not a legal-deadline guarantee.

Source dates are limited to 2000–2099 and whole minutes. The method supports whole-minute UTC offsets up to 24 hours and at most two source occurrences. Unsupported formatting or rules are reported rather than guessed. No live clock, recurrence, city database, custom offsets, leap seconds or multi-location meeting planner is included.

In-page conversion

The tool uses your browser's installed rules without uploading your entries, detecting your location, requesting a time-zone service or adding saved history or input-bearing links. Copy is optional. Existing site services still apply; this is not a certification of third-party services.

Time-zone questions

The difference between two named zones can change with seasonal or political clock rules. Regions may change offsets on different dates, so applying today's difference to a future event can give the wrong result.

The source clock reading repeats when an offset moves backward. The two options identify different UTC instants. Choose the intended occurrence using the UTC offset or confirm it with the organizer; the tool does not choose silently.

A clock change can skip that local time, or even a whole local date. A valid Gregorian label does not guarantee that the clock reading occurred in the chosen zone. Enter an existing source time rather than expecting an automatic forward adjustment.

No. Abbreviations can describe different regions or offsets. Choose a supported named zone from the searchable list. The UTC offsets in the answer apply to the selected instant, not permanently to every date in that zone.

No. The result follows the rules currently installed in your browser, which may be older than current policy. Future policy can also change after a conversion. Confirm important arrangements and update your browser or device when appropriate.

Sources and calculation method

The browser resolves the source clock reading to an instant, then formats that instant in the target zone.

Reviewed 4 November 2026. Your browser's installed rules may not reflect current policy. Confirm important or future arrangements with an authoritative source.