Time Zone Converter — Compare Times Across the World

Pick a time in one zone and see it in as many others as you like, with the date shift and DST handled for you.

🔒 Runs in your browser — files never uploaded ⚡ No signup 💯 Free

ZoneLocal timeDateOffset

Convert a date and time from one time zone to any others — for a meeting, a launch, a flight or a call home. Choose the source zone and moment, add the zones you care about, and each row shows the local time, the date (flagged when it's tomorrow or yesterday there) and the UTC offset in force on that day.

Daylight saving is handled from the browser's own time zone database, so summer and winter offsets are right without you having to know when each country switches.

How to use Time Zone Converter

  1. Set the date and time, or tap Now.
  2. Choose the zone that time is in — it defaults to your device's zone.
  3. Add zones to compare from the list (any IANA zone, e.g. America/New_York, Asia/Kolkata).
  4. Copy all to paste the whole table into an invite or a message.

Why "New York time" and not "EST"

Abbreviations lie. EST is UTC−5 in winter but New York runs EDT (UTC−4) all summer; "CST" means three different things in Chicago, China and Cuba; and "IST" is India, Israel or Ireland. The only unambiguous names are the IANA zone identifiers — America/New_York, Europe/London, Asia/Kolkata — which carry the full history of a region's rules, DST included. That's why the pickers here use them, and why you should put them in calendar invites.

Daylight saving traps

  • Different switch dates. The US changes clocks in mid-March and early November; Europe at the end of March and October. For a few weeks each year the New York–London gap is 4 hours, not 5. A recurring 9 a.m. call drifts on those weeks.
  • Opposite hemispheres. Sydney is on summer time when London is on winter time, so the gap swings between 9 and 11 hours across the year.
  • No DST at all in most of Asia and Africa, Arizona, and Queensland — their offsets never move while everyone else's does.
  • Times that don't exist. At spring-forward, 02:30 never happens. If you enter one, the converter says so and shows the next real time.

Scheduling across many zones

Add all the participants' zones and look for a row where every local time is between about 08:00 and 18:00 — with a large spread (San Francisco to Mumbai, say) no such hour exists and someone has to take an early or late slot; rotate who. Always state the date as well as the time: 22:00 in Los Angeles is tomorrow in Tokyo, and the "+1 day" marker exists for exactly that reason.

For converting a Unix timestamp rather than a wall-clock time, use the timestamp converter; to schedule a recurring job in a server's zone, the cron parser previews runs in UTC.

Frequently asked questions

Where do the time zone rules come from?

From your browser's built-in IANA time zone database — the same one operating systems and servers use, updated with the OS. There's no hand-maintained offset table here to go stale when a government changes its daylight-saving rules.

Why can't I pick "EST" or "CET"?

Because abbreviations are ambiguous and don't encode DST: EST becomes EDT in summer, "IST" is three different countries, "CST" is three continents. Choose the region instead — America/New_York is always right for New York, winter or summer.

The time I typed jumped forward an hour — why?

You entered a time that doesn't exist in that zone on that date — the hour skipped at the spring-forward change. There is no such moment, so the converter uses the next real one and tells you. Times in the autumn fall-back hour exist twice; the earlier (daylight-time) instance is used.

What does "+1 day" mean in the date column?

That the moment falls on the next calendar day in that zone. 22:00 Tuesday in Los Angeles is 15:00 Wednesday in Tokyo. Always include the date when arranging anything across the Pacific.

Which zone should a meeting invite use?

One explicit IANA zone (or UTC) plus the local times for each attendee — this table, copied. Calendar apps convert correctly when the invite carries a proper zone; they fail when it says "3pm EST" in June.