Orpheus

Time Zone Converter

One instant, shown in every zone you care about.

Options
Show every zone, not just the majors
Result

Everything is processed in this tab. Nothing you paste is sent anywhere.

Every tool runs entirely in your browser. Your files are never uploaded to a server.

A time zone converter maps one instant onto local clocks. 14:30 UTC is 10:30 in New York, 15:30 in London, 20:00 in Kolkata and 23:30 in Tokyo — all the same moment.

How to use Time Zone Converter

  1. Enter the date and time. As 2026-08-22 14:30. Several lines at once are fine.
  2. Say which zone it is in. The conversion is only meaningful once the source zone is known.
  3. Read the list. Each zone with its date, time and current offset.

About converting between time zones

A time zone converter answers one question: given a moment expressed on one local clock, what does every other local clock read at that same moment. The subtlety is that a local wall-clock time is not itself a moment. It becomes one only when paired with a zone, and the mapping between the two is not a fixed arithmetic offset — it depends on the date, because of daylight saving, and on the year, because governments change the rules. That is why zone names matter more than abbreviations. Europe/Berlin carries the full history and future schedule of transitions for that location; CET is a label for one of its two states and says nothing about when it applies. Abbreviations are also genuinely ambiguous: CST is used for Central Standard Time in North America, China Standard Time and Cuba Standard Time, and IST for India, Ireland and Israel. Two edge cases are worth knowing when scheduling across zones. In spring an hour is skipped, so a local time inside it does not exist and any event scheduled there has no instant to occur at. In autumn an hour repeats, so a single local time corresponds to two different moments an hour apart, which is why hourly jobs sometimes run twice and reports occasionally double-count. Offsets are also not all whole hours — India at UTC+05:30 and Nepal at +05:45 are the usual counterexamples.

Frequently asked questions

Why does the offset change through the year?
Daylight saving. Most of Europe and North America shift by an hour in spring and back in autumn, but not on the same dates, so the gap between London and New York is four hours for a couple of weeks each year rather than the usual five.
Are all offsets whole hours?
No. India is UTC+05:30, Nepal +05:45, parts of Australia +09:30, and the Chatham Islands +12:45. Any scheduling logic that assumes whole hours is already wrong for several hundred million people.
Why use zone names like Europe/Berlin rather than CET?
Because abbreviations are ambiguous and static. CST refers to at least three different zones, and IST to three more. An IANA zone name carries the full history of offset changes for that place, including transitions that have not happened yet.
What happens to a time in a skipped hour?
It does not exist. When clocks jump from 01:59 to 03:00, a local time of 02:30 has no instant, so the conversion lands on the nearest valid moment instead. The reverse happens in autumn, where an hour occurs twice and one local time maps to two instants.
Is this affected by my own computer's time zone?
No. The conversion uses the zone you select as the source and the browser's time zone database for the targets, so the result is the same wherever you run it. Your own clock is not part of the calculation.

Last updated