Time Zone Converter
Convert a time across multiple world time zones simultaneously. Select time zones, enter a reference time, and see the equivalent local time in each zone.
When a time zone converter is the right tool
Use this page to compare one date and time across a fixed list of 20 common world time zones. Pick a source zone, enter a local date and time, and read the equivalent time in each selected zone. The table updates as you change the form. It is not a complete IANA picker, and it is not a Unix timestamp tool — for seconds since epoch use Timestamp Converter.
Use cases
Comparing a meeting time in a few cities
Set the source to the zone the meeting was announced in, type the clock time, and keep the cities you care about selected. A row that has already moved into the next calendar day is tagged +1 day. India uses a half-hour offset; Dubai, Bangkok, Shanghai, and Tokyo are in the list, but Singapore and Hong Kong are not.
Starting from UTC
The default source is UTC. Entering a midday UTC time such as 2026-11-15 12:00 is a reliable way to read the other columns, because the source instant is computed correctly in that situation. Prefer UTC as the source if you want to avoid the date-adjustment edge cases described below.
Using Now carefully
Now copies this device’s local clock digits into the field. If your source zone is not the zone the computer is set to, those digits are the wrong local time for the source. Change the source to your own zone first, or type the intended local time yourself.
How conversion works
The date-and-time control provides calendar numbers (seconds are dropped). The page builds a UTC timestamp from those numbers, formats it in the source zone, and adjusts hours and minutes — and the day of month — once so the result should display as the time you entered. Each selected zone is then formatted with Intl.DateTimeFormat: a 24-hour time, an en-CA date, a short abbreviation, and a short offset.
Source: UTC 2026-11-15 12:00
UTC 12:00:00 2026-11-15
New York (EST, GMT-5) 07:00:00 2026-11-15
London (GMT, GMT+0) 12:00:00 2026-11-15
Shanghai (GMT+8) 20:00:00 2026-11-15
Tokyo (GMT+9) 21:00:00 2026-11-15
Auckland 01:00:00 2026-11-16 +1 dayAuckland is already on 16 November, so it shows +1 day. New York is on standard time (EST, GMT−5) on that date; the label still mentions EST/EDT, but the abbreviation under the name reflects the actual instant.
What this tool does not do
It does not list every IANA zone, accept a raw UTC offset, or convert Unix timestamps. The one-pass source adjustment can produce the wrong date for some evening times in eastern zones and around some DST or month boundaries. It does not upload anything. For adding days on a calendar, use Date Calculator.
How to use Time Zone Converter
- Choose a source time zone and enter a date and time, or click Now after setting the source to your own zone.
- Review the converted rows. The source row is marked if that zone is selected.
- Use Select Time Zones to add or remove cities from the table. Clicking a selected chip removes it.
Frequently asked questions
Which time zones can I convert between?
A fixed list of 20 IANA zones: UTC, Los Angeles, Denver, Chicago, New York, São Paulo, London, Paris, Helsinki, Moscow, Dubai, Karachi, India (Kolkata), Dhaka, Bangkok, Shanghai, Tokyo, Seoul, Sydney, and Auckland. You cannot type an arbitrary zone such as Asia/Singapore. By default the results table shows UTC, New York, London, Shanghai, and Tokyo; use the picker to add or remove zones.
How is the source time turned into an instant?
The date-and-time field is read as wall-clock numbers in the source zone: a UTC guess is built from those numbers, then a single hour, minute, and day-of-month adjustment is applied so the instant should display as the time you typed. Seconds in the input are ignored. This works for many cases — for example 12:00 UTC on 2026-11-15 converts correctly to 07:00 in New York, 20:00 in Shanghai, and 01:00 the next day in Auckland.
When can the converted times be wrong?
The one-pass adjustment can land on the wrong calendar date when the UTC reading of the same clock numbers already falls on a different local day, or when the day-of-month wraps a month boundary. Evening times in zones east of UTC (for example 20:00 in Shanghai) and some DST transition or month-start times in America/New_York have been observed to be off by one or more days. Midday times entered with UTC as the source were accurate in those checks. The tool does not iterate until the instant is stable, and it does not specially handle skipped or repeated DST hours.
What does the Now button do?
It fills the date-and-time field with the current year, month, day, hour, and minute from this device’s local clock, without seconds. Those numbers are then interpreted in the selected source time zone, not necessarily in the zone your computer uses. If the source is Tokyo and your computer is in Shanghai, Now is not “current time in Tokyo.”
What do the source badge and ±1 day labels mean?
The row whose zone matches the source is highlighted and labeled source, if that zone is selected. A +1 day or −1 day tag appears when that row’s calendar date (YYYY-MM-DD in the en-CA format) differs from the source row’s date. Offsets and abbreviations come from the browser’s Intl API for that instant (for example EST, GMT+8, or GMT+5:30). The static labels such as PST/PDT do not change with the season; the abbreviation under the name does.
Is my data sent to a server?
No. Conversion runs in your browser with the Intl date-time APIs. Closing the tab discards the form.
Related tools and guides
References
- The zone names are IANA identifiers such as
America/New_York. Offsets and daylight-saving rules come from your browser’s ICU/Intl data, not from a clock this page keeps itself. - For a Unix timestamp rather than a wall-clock time in a named zone, use the Timestamp Converter on this site.