Time Zone Converter

The Complete Time Zone Converter Guide

How time zones, UTC offsets and daylight saving time combine, and how to read every part of the converter results.

Open Time Zone Converter

Why Time Zones Are Tricky

A time zone is more than a fixed number of hours from UTC. It is a named rule set, kept in the IANA time zone database, that says what the local clock shows at each moment in history. A zone can change its standard offset, start or stop daylight saving time, or switch its rules. The same zone can therefore sit at different offsets on different dates.

This converter takes a wall-clock date and time in one zone, works out the single moment it refers to, and then shows what the clocks in your chosen zones read at that moment. All of the work uses the Intl API built into your browser, so the answers follow your browser's copy of the time zone data.

Nothing is sent to a server. Your selections stay in the page only while it is open.

Working from one instant is the reliable approach. Storing a local time and an offset separately, or converting by adding a fixed number of hours, breaks as soon as a zone changes its rules or a date falls near a clock change. Converting through the instant avoids that, because every target row is read from the same starting moment.

Step-by-Step: Every Control Explained

  1. Source date and time. These are read as the wall clock in the source zone. The time uses the 24-hour clock with a one-minute step.
  2. Source time zone. Defaults to the zone your browser reports. The list is built from the zones the browser supports, and falls back to about 40 common zones where that is not available.
  3. Use the current time. Fills in the present moment as seen in the source zone, so you can compare where the clocks stand right now.
  4. Compare with these zones. Each chip is a target zone. Add zones with the selector and remove them with the cross. The page allows up to 12 targets at once.
  5. Results table. The first row is the source. Each row shows the weekday with the local date and time, the UTC offset at that instant, and whether daylight saving time applies.
  6. Same instant in UTC. The line above the table gives the UTC reading, a useful reference when you are writing down a meeting time.
  7. Notes. A yellow note appears when the time you entered falls in a clock gap or a repeated hour.

Worked Example

A meeting in New York. Set the source date to 2026-10-12, the time to 09:00 and the source zone to America/New_York. New York is on Eastern Daylight Time, which is UTC minus four hours on that date, so the instant is 13:00 UTC.

From that instant the rows read: London, on British Summer Time at UTC+01:00, shows Mon 2026-10-12 14:00. Kolkata, at UTC+05:30 with no daylight saving time, shows Mon 2026-10-12 18:30. Tokyo, at UTC+09:00, shows Mon 2026-10-12 22:00. Sydney is on daylight saving time at UTC+11:00, so it shows Tue 2026-10-13 00:00.

A clock gap. On Sunday 8 March 2026, New York clocks jumped from 02:00 to 03:00, so 02:30 never happened there. Entering that time moves it forward by the skipped hour and shows 03:30 EDT, with a note.

A repeated hour. On Sunday 1 November 2026, the clocks in New York went back from 02:00 to 01:00, so 01:30 occurs twice. The converter uses the earlier instant, 01:30 EDT, and says so.

Tips and Common Mistakes

  • Check the date, not just the time. A meeting set in one country can fall on a different calendar day in another, so read the weekday column.
  • Store zone names, not offsets. A saved +05:30 can be wrong after a rule change, while a zone name such as Asia/Kolkata always resolves to the current rules.
  • Pick the right source zone. A wrong source shifts every row by the same error, so confirm it before you read the table.
  • Watch repeated hours. During a fall-back change one clock reading names two moments. Decide which one you mean before you send an invitation.
  • Do not add fixed hours by hand. Adding a constant number of hours ignores any daylight saving change between the two dates, so use a zone-aware calculation such as this converter.
  • Expect future rules to move. Results for dates far ahead depend on the rules in your browser's database, which governments may still change.

Frequently Asked Questions

Why does the source zone matter so much?

The source zone decides which single moment your wall-clock entry refers to. Every target row is calculated from that moment, so a wrong source zone moves all of them by the same amount.

Does the converter show the time for a zone not in the list?

It lists the zones your browser supports. If a zone you need is missing, choose the nearest city in the same region with the same rules, and confirm the offset in the results.

Why does the tool say daylight saving time is on when the offset looks standard?

The check compares the offset at that instant with the lower of January and July offsets for the same year. An unusual historical change can make that comparison misleading, so confirm important dates against an official source.

What does the UTC line show?

It shows the same instant written in Coordinated Universal Time. UTC does not change with daylight saving time, so it is the most dependable reference for scheduling, while each local clock may move twice a year.

Can the converter tell me the time right now?

Yes. The Use the current time button fills in the present moment as seen in the source zone. The page does not refresh by itself, so press the button again if you leave it open.

Open Time Zone Converter