Time Zone Converter

Convert a date and time from one time zone to several others with live UTC offsets that follow daylight saving rules, and share the setup as a link.

The interactive tool loads here when JavaScript runs.

About this tool

What is the Time Zone Converter?

The Time Zone Converter takes a date and time in a source time zone and shows the same moment in every zone you add, each on its own card with the local date and time, the UTC offset in force at that moment, and the source time for reference.

Zones are IANA time zone names such as America/New_York, Europe/London and Asia/Kolkata, searchable by city, country or abbreviation. The source zone starts as your browser's zone. Offsets come from the time zone database built into your browser, so a date in July shows summer time and a date in January shows winter time, and you can convert dates in the past or future.

Share copies a link containing the time, source zone and list of zones, so a colleague opens the same comparison. Conversion runs in your browser; no time server is called.

  • Converts one moment to as many zones as you add
  • Offsets follow DST rules for the chosen date, past or future
  • IANA zone names with search by city, country or abbreviation
  • Handles half-hour and 45-minute offsets
  • Dates shown month-first, day-first or year-first (ISO)
  • Shareable link with time, zone list and date format
  • Runs in your browser with its built-in time zone data
Read the guide: Time Zones for Developers: Offsets, DST and IANA Zone Names

Updated

How to use the Time Zone Converter

  1. Enter the date and time in the Time field. It is read as wall-clock time in the source time zone.
  2. Choose the Source Timezone, searching by city, country or abbreviation. Changing it keeps the clock time you typed and reinterprets it in the new zone.
  3. Add zones with Add Timezone or the Quick Add Popular Timezones buttons, and remove them with the X on each card.
  4. Read each card for the local time and UTC offset, and use the copy button to copy one time.
  5. Click Share to copy a link with the time, source zone and selected zones.

Worked examples

A 09:30 New York meeting in winter

Input

Time: 2026-01-15 09:30, Source: America/New_York

Output

UTC 14:30
Europe/London 14:30
Asia/Kolkata 20:00
Asia/Tokyo 23:30
Australia/Sydney 01:30 on 16 January

New York is on EST (UTC-5) in January, London on GMT (UTC+0), and Sydney is already into the next day because it is on summer time (UTC+11).

The same meeting in July

Input

Time: 2026-07-15 09:30, Source: America/New_York

Output

UTC 13:30
Europe/London 14:30
Asia/Kolkata 19:00
Asia/Tokyo 22:30
Australia/Sydney 23:30

New York moved to EDT (UTC-4), so UTC, India and Tokyo are an hour earlier than in January. London also moved to BST, so its gap to New York stays five hours, while Sydney left summer time and is now 14 hours ahead instead of 16.

Background and insight

UTC offsets are not time zones. America/New_York is UTC-5 in winter and UTC-4 in summer; the switch dates are set by law and have changed several times (the United States moved them in 2007). The IANA Time Zone Database, also called tzdata or the Olson database, records those rules and their history for every region, and it is what operating systems, browsers, Java and most databases use. Its zone names follow Area/Location, named after the most populous city, which is why India is Asia/Kolkata and there is no Asia/Mumbai.

Abbreviations are ambiguous: CST is Central Standard Time in the US, China Standard Time and Cuba Standard Time; IST is India, Ireland or Israel. That is why the tool shows numeric offsets such as GMT+05:30 next to each zone. Offsets are not always whole hours either: India is +5:30, Nepal +5:45 and parts of Australia +9:30.

Daylight saving creates two awkward cases. In spring an hour is skipped, so 02:30 on 8 March 2026 never happens in New York; this tool moves such times forward by the gap, to 03:30. In autumn an hour repeats, so 01:30 on 1 November 2026 happens twice; the tool uses the first one (EDT). Scheduling code has to make the same choices, which is why storing times in UTC and converting only for display is the usual advice.

Common use cases

  • Scheduling across offices

    Check what a proposed meeting time means for colleagues in each office, including on dates after a DST change.

  • Reading logs and incidents

    Convert a UTC timestamp from a log into the local time of the users or the on-call engineer.

  • Planning releases and events

    Announce a launch or webinar time and check it for each target region.

  • Travel planning

    Work out arrival times and call windows around a trip.

Tips and limitations

  • Check the date as well as the time. Converting across the date line or past midnight changes the day, as with Sydney in the example.
  • The US and Europe change clocks on different weekends in March and in October or November, so gaps between them shrink by an hour for a week or two each year.
  • Some zones have no DST at all, including Asia/Kolkata, Asia/Tokyo, America/Phoenix and, since 2022, America/Mexico_City.
  • Store timestamps in UTC (or with an explicit offset, as in ISO 8601) and convert only for display.
  • The shared link contains the chosen time and zones in the URL, so anyone you send it to can see them.

Sources and further reading

  1. Time Zone Database, IANA. The tz database that browsers and operating systems use
  2. Theory and pragmatics of the tz code and data, IANA. How zones are named after the most populous city
  3. Daylight Saving Time Rules, National Institute of Standards and Technology. The US rules in force since 2007
  4. RFC 6557: Procedures for Maintaining the Time Zone Database, IETF

Frequently asked questions

Does the time zone converter handle daylight saving time?

Yes. Each card uses the rules in force at the date you entered, from the IANA time zone database built into your browser. A New York time in January uses UTC-5 and one in July uses UTC-4, and the UTC Offset line on each card shows which applied.

What happens if I enter a time that is skipped by daylight saving?

It is moved forward by the length of the gap. In New York, clocks jump from 02:00 to 03:00 on 8 March 2026, so 02:30 does not exist and is treated as 03:30 EDT. For a time that occurs twice in autumn, the first occurrence (still on summer time) is used.

Why is India Asia/Kolkata and not Asia/Mumbai or New Delhi?

IANA names one zone per region with identical clock history, named after a representative city, and Kolkata (then Calcutta) was chosen for India. Mumbai, New Delhi and Bangalore all use Asia/Kolkata. Likewise all of mainland China uses Asia/Shanghai, so there is no Asia/Beijing.

What is the difference between UTC and GMT?

For converting clock times, none: both are offset zero. UTC is the atomic-clock based standard used by computers and aviation, kept within 0.9 seconds of Earth rotation by leap seconds. GMT is the older astronomical term, and Europe/London uses it as the name for its winter time.

Why does CST give different results in different tools?

CST is ambiguous: it can mean US Central Standard Time (UTC-6), China Standard Time (UTC+8) or Cuba Standard Time (UTC-5). Abbreviations are labels, not identifiers. Pick a zone by city or IANA name, such as America/Chicago or Asia/Shanghai, and check the numeric offset shown on the card.

How do I share a converted time with my team?

Click Share. It copies a link with the time, the source zone and your selected zones in the URL. Anyone opening it sees the same moment, source zone and cards, whatever time zone their own computer is set to.

Is there an in-depth guide to the Time Zone Converter?

Yes. “Time Zones for Developers: Offsets, DST and IANA Zone Names” covers the background, how it works, common pitfalls and worked examples. Read the full guide.