Timezone Converter

Runs in browser Utilities

Convert any moment across IANA timezones with DST awareness, compare several zones at once, and copy ISO strings with the correct offsets.

Privacy: This tool runs entirely in your browser. Your input never leaves your device.

How to use Timezone Converter

  1. Type the date and time as seen in the source zone (or use an epoch / ISO value with an offset).
  2. Pick the From and To zones.
  3. Add extra zones to compare in the world clock table.

Timezone Converter features

  • Every IANA timezone supported by your browser, with popular Middle-East, Asian, European and American zones first
  • DST-aware offsets and abbreviations for the exact instant
  • Difference between the two zones and day shift (next / previous day)
  • World clock table with any extra zones you add
  • ISO strings for source, target and UTC plus a datetime-local value

Timezone Converter example

Riyadh stand-up in other offices

Input:

2024-03-15 09:00 · From Asia/Riyadh · To America/New_York

Output:

New York: Friday, 15 March 2024 02:00 (UTC−04:00 EDT)
New York is 7 hours behind Riyadh

Frequently asked questions about Timezone Converter

Where does the timezone data come from?

From your browser's built-in Intl.DateTimeFormat, which ships the IANA tz database including daylight-saving rules. No external library or server is involved.

Does it handle daylight saving time?

Yes. Offsets are computed for the specific instant, so London shows +01:00 in summer and +00:00 in winter, and Riyadh stays at +03:00 all year.

How do I enter a time in the source zone?

Type it without an offset (2024-03-15 09:00) and pick the "From" zone. If you include Z or an offset, or an epoch number, the value is absolute and the "From" zone only affects the display.

Can I compare more than two zones?

The world clock table lists common zones automatically and you can add any IANA names in the "Extra zones" field, separated by commas.

Technical notes

Offsets are not looked up in a table: for the exact instant the engine formats the date with Intl.DateTimeFormat in the zone, rebuilds the wall-clock parts as UTC and diffs them (offsetMinutes), rounded to whole minutes — so Local Mean Time before standard time (Riyadh +03:06:52 until 1947) prints as +03:07. 'Difference' compares both offsets at that instant and therefore changes across DST; 'next day / previous day' compares calendar dates.

A wall-clock time without an offset is resolved by guess → offset → re-check (zonedToUtc): a time inside a spring-forward gap moves to the next valid instant (New York, 10 March 2024: 02:30 becomes 03:30 EDT); an ambiguous fall-back time takes its first, daylight-saving occurrence. Abbreviations are en-US short zone names, so North American zones show EDT or PST but most others GMT+3; Extra zones accepts any identifier the browser recognises, even aliases like US/Eastern.