Convert a date and time between any two time zones, using the IANA time-zone database your browser already ships — the same one your operating system's clock uses. Offsets are computed for the exact date you enter, so a July conversion and a January conversion correctly differ where daylight saving applies. Two things most converters get wrong are handled explicitly: on the morning clocks go forward an hour does not exist, and on the morning clocks go back an hour happens twice, so this page tells you which you have hit rather than silently picking an answer. Add cities to see the same moment everywhere, or turn on the meeting grid to find an hour that suits all of them. Nothing is uploaded — no times, no dates, no location.
| Zone | IANA name | Standard | Daylight saving |
|---|---|---|---|
| Pacific (US) | America/Los_Angeles | −08:00 | −07:00 |
| Eastern (US) | America/New_York | −05:00 | −04:00 |
| UTC / GMT | UTC | +00:00 | none |
| UK | Europe/London | +00:00 | +01:00 |
| Central Europe | Europe/Berlin | +01:00 | +02:00 |
| Pakistan | Asia/Karachi | +05:00 | none |
| India | Asia/Kolkata | +05:30 | none |
| Nepal | Asia/Kathmandu | +05:45 | none |
| Japan | Asia/Tokyo | +09:00 | none |
| Sydney | Australia/Sydney | +10:00 | +11:00 |
Yes, and for the specific date you enter rather than today. That distinction is the whole point: 09:00 in Los Angeles is 17:00 UTC in July and 16:00 UTC in January, because Pacific time shifts by an hour between them. Enter a summer date and a winter date and you will see the offsets differ.
The page says so. When clocks go forward, an hour is skipped entirely — 02:30 on 10 March 2024 simply never happened in New York. A converter that answers anyway is answering a different question, so instead you get a warning and the reading for the moment the clocks landed on.
When clocks go back, the hour before the change repeats, so 01:30 occurs twice about an hour apart. The earlier one is shown by default, which is the standard convention, and the later one is shown alongside it, because which you meant depends on what you were doing and the tool cannot know.
Your browser. Every modern browser ships the full IANA time-zone database for Intl formatting, including historical rules and scheduled future changes. Nothing is fetched from a time-zone API, which also means the tool keeps working offline.
Yes. India is +05:30, Nepal is +05:45, parts of Australia are +08:45, and all of them are handled, because offsets here are measured in minutes rather than hours. Differences are shown as fractions — 5½ hours ahead — since a decimal reads like a bug.
Yes. Every conversion runs in your browser and nothing is sent anywhere. Your own zone is detected locally to prefill the form and you can change it; it is never transmitted or stored.
Yes. The field is a plain text input with typeahead, so any IANA name your browser recognises works, whether or not it appears in the suggestions. An unrecognised name is flagged rather than silently ignored.
The hard part of time-zone conversion is not the arithmetic, it is that JavaScript cannot do half of it. `Intl.DateTimeFormat` will format an instant in any IANA zone, but nothing in the language parses a wall-clock time *in* a named zone: `new Date("2026-07-01 09:00")` is interpreted in whatever zone the visitor's machine happens to be set to, which is exactly the assumption a converter exists to remove. So the offset is measured rather than looked up. An instant is formatted in the target zone, the resulting year, month, day, hour and minute are read back as though they were UTC, and the gap between that and the real instant is the zone's offset at that moment. This works for every zone the browser knows, including the half-hour ones like India at +05:30 and the quarter-hour ones like Nepal at +05:45, and for every historical and scheduled rule change, without shipping a time-zone database or calling an API. The inversion — wall-clock time to instant — is then done by candidate and check, and this is where naive converters go wrong. Daylight saving makes the mapping from clock time to instant neither total nor unique. On the morning clocks go forward, an hour does not exist: 02:30 on 10 March 2024 never happened in New York, and a converter that quietly answers for 03:30 has responded to a question nobody asked. On the morning clocks go back, an hour happens twice: 01:30 on 3 November 2024 occurred at 05:30 UTC and again at 06:30 UTC, so a converter that silently picks one is wrong half the time. Two candidate instants are built, one from the offset in force a day before the entered date and one from a day after — probing a day out rather than near the entered time matters, because an offset sampled next to a backward transition returns the same value twice and the second reading of the ambiguous hour is never found at all. Each candidate is then formatted back in the source zone and kept only if it reproduces the clock time that was typed. Two survivors means the time is ambiguous, and both readings are reported. None means the time does not exist, and the page says so rather than inventing an answer. The meeting-hours grid reads each zone's local hour through the same formatter, so the highlighted rows account for the transitions too.