Time zone converter.

Convert a local time, not just an hour.

Choose the date and time where an event starts, then select its source time zone and the target zone you want to compare. The date matters: a city’s offset from UTC can change during the year. Results use a 24-hour clock and show the target calendar date, UTC offset and difference from the source.

Use Now for the current instant in your chosen source zone. It takes a snapshot rather than running a live clock. Swap zones reverses the comparison while preserving that instant; it also updates the source date and time. Convert & save stores the inputs in this browser’s last 10 conversions so you can recall them later.

A dated example: New York to London.

On January 15, 2026, New York is on UTC−05:00 and London is on UTC+00:00. A meeting at 12:00 in New York therefore starts at 17:00 in London on the same date.

2026-01-15 12:00 New York → 2026-01-15 17:00 London

The five-hour difference is not a year-round rule. On March 15, 2026, New York has changed to daylight saving time but London has not yet changed, so 12:00 in New York converts to 16:00 in London. Always use the event’s actual date.

Why can a local time be missing or happen twice?

When clocks move forward, some local times do not exist. In New York on March 8, 2026, the clock skips from 01:59:59 to 03:00:00. Entering 02:30 on that date produces an error here rather than silently moving your event to a different time.

When clocks move backward, a local hour can repeat. In New York on November 1, 2026, 01:30 occurs first at UTC−04:00 and then again at UTC−05:00. This converter asks you to choose the first or second occurrence. They are distinct instants, one hour apart. Changes in some other zones are not exactly one hour.

Crossing midnight changes the calendar date.

A target location may already be on tomorrow’s date or still be on yesterday’s. For example, January 15, 2026 at 23:30 UTC is January 16 at 08:30 in Tokyo. Check the date beneath each clock before sending a calendar invitation or planning a call. Locations near opposite sides of the International Date Line can even differ by two calendar dates.

Reading the two clocks and matching timeline.

The analog clocks show source and target local time for one instant; the digital times disambiguate morning and evening. Each timeline column compares the same instant in both places, spaced three hours apart. The outlined column is your selection, and each cell includes its local month and day. Clock changes can make local labels skip or repeat even though elapsed time advances evenly.

Light cells represent 07:00 through 18:59, a rough daytime window for comparing schedules. Dark cells represent the remaining hours. These are not sunrise, sunset or guaranteed working hours; season, latitude and individual schedules matter.

Why use city-based IANA time zones?

Identifiers such as America/New_York, Europe/London and Asia/Kathmandu describe regional clock rules, rather than a single fixed offset. Familiar abbreviations can be ambiguous: CST can refer to different regions, and “Eastern time” changes offset seasonally. Choose a city that shares the rules relevant to your event. UTC is included as a fixed global reference.

The menu starts with common cities and adds the IANA zones exposed by your browser when that feature is available. Conversion uses Temporal and the runtime’s time zone data. Results can vary with browser or operating-system version, historical data coverage and how recently regional rule changes were published. Historical offsets may include seconds; the difference summary rounds fractional minutes to two decimal places. Future clock rules can change by law, so confirm important travel or meeting times with the organizer and an up-to-date calendar.