Skip to main content

Time Zone Converter

Converts a date and time between any two IANA time zones using the browser Intl API, so daylight saving transitions resolve automatically. The hourly mapping table refreshes for the chosen date, and each result includes weekday and the resolved short zone abbreviation (PST versus PDT, GMT versus BST).

Runs entirely in your browser

This tool sends nothing over the network. Everything you enter is processed on your device and never reaches our servers.

Productivity
Scheduling
Travel
Communication
Development
Loading the tool
Reference

Documentation

The time zone converter pairs a calendar date with a wall-clock time in a chosen source zone, resolves that moment to an absolute instant, and renders it in a target zone using the IANA time zone database. Daylight saving transitions are honored automatically: converting 02:30 on a spring-forward date in America/Los_Angeles produces a result reflecting the actual offset on that calendar day, rather than a fixed eight-hour shift.

  1. The source and target zones can each be picked from a list grouped by region, UTC, North America, Europe, Asia, Australia and Pacific, and so on, labeled with the zone's short abbreviation and its daylight-saving behavior.
  2. A custom IANA zone identifier, such as Pacific/Tahiti or Indian/Mauritius, can be entered directly for a zone outside that list, and overrides the region list for that side.
  3. The date entered anchors the conversion, since the same clock time in the same zone pair can resolve to a different offset depending on the calendar day: a DST transition changes the offset from one day to the next. The default is today.
  4. Time can be entered in 12-hour format with an AM or PM designation, or in 24-hour format, which hides the AM/PM control.
  5. The result gives the weekday, full date, time, and the short zone abbreviation resolved for that specific date, such as PST or PDT, GMT or BST, since the abbreviation itself can change across a DST boundary.
  6. Reversing the two zones keeps the entered time in place rather than requiring it to be retyped; the headings, labels, and conversion table all flip with it.

A real-time clock panel runs continuously and shows the current moment in both selected zones, so the live offset is visible without converting a specific value. An hourly conversion table, under a disclosure, lists every whole hour of the selected source date and its target-zone equivalent in both 12-hour and 24-hour notation. Each row is built by treating the hour as a wall-clock value in the source zone, resolving it to UTC, and formatting that instant in the target zone, so a DST jump appears as a duplicated or skipped hour exactly where it actually occurs. The last zone pair, date, time, and mode are restored automatically on a return visit.

Time zone coordination comes up in distributed engineering, content publishing, customer support, broadcast, travel, and any schedule spanning hemispheres. Real IANA zones, rather than a single hard-coded offset, keep a conversion correct through the spring-forward and fall-back weekends that historically cause the most missed meetings.

  • Distributed engineering: a Europe/London incident timeline translated to America/Los_Angeles tells the on-call engineer it lands at 06:00 PT; reversing the pair maps their fix back to UTC for the public status page.
  • Product launches and webinars: a 10:00 launch in America/New_York converted to Europe/Berlin, Asia/Kolkata, and Australia/Sydney gives the local times for regional invites without hand offset math.
  • Customer support coverage: a follow-the-sun rotation maps by converting UTC ticket windows to America/Chicago, Europe/Dublin, and Asia/Singapore shift hours for the selected day.
  • Travel planning: a flight departure listed in Europe/Paris, converted to Pacific/Auckland, gives the local arrival time to message family with.
  • Broadcast and live events: a 20:00 UTC sports kickoff converted to America/Sao_Paulo and Asia/Tokyo viewer-local times supports a watch-party announcement.
  • Cron jobs and pipelines: the hourly table shows whether a 03:15 UTC nightly job lands inside America/Denver office hours on Monday and outside them on Saturday.
  • Education and academic deadlines: an assignment deadline set in Europe/London, checked from Asia/Bangkok, may fall on the next calendar day locally, which the conversion confirms.
  • Finance and trading windows: a New York market open (America/New_York 09:30) aligned with Asia/Hong_Kong and Europe/London desk shifts stays accurate during weeks that span a DST boundary.
  • Family scheduling: a call time across Pacific/Honolulu, America/Chicago, and Europe/Athens is found by converting each candidate hour until one falls inside everyone's waking range.
Inputs, outputs, and what the Time Zone Converter computes

What the Time Zone Converter asks for and what it returns, as a plain list. Defaults, units, and ranges are the ones the form loads with.

Inputs

  • From · default: UTC (Coordinated Universal Time)
  • To · default: UTC (Coordinated Universal Time)
  • Custom from zone (text input)
  • Custom to zone (text input)
  • Date (date input)
  • 12-hour / 24-hour · default: 12-hour
  • Hour (numeric input) · range: 1 to 12
  • Minute (numeric input) · range: 0 to 59
  • AM/PM · default: AM
  • Hour (numeric input) · range: 0 to 23

Controls

Convert · Reset