Time Zone Converter

Coordinate internationally, schedule across zones, support global operations, and keep accurate local times.

Doing it in your head works until it does not. The arithmetic is easy — add five and a half hours — and it is wrong twice a year in every place that changes its clocks, wrong for three weeks a year in any pair whose two halves change on different dates, and wrong by a whole day whenever the answer crosses midnight. A converter that reads the actual rules for the actual date removes all three.

Benefits of Time Zone Conversion

• International Communication: Meetings and calls
• Scheduling: Events and appointments
• Business Operations: Global teams
• Travel Planning: Adjust to local time
• Coordination: Align many regions

We compute differences with DST rules and show results in real time on your device using IANA zones.

A time zone is not an offset. It is a rule that says which offset applies at which instant, and those rules change: countries add and drop daylight saving, move the dates they switch on, and occasionally change their standard offset outright. So converting a time means finding the instant the wall clock in the source zone named, then asking the destination zone what its clock read at that instant — two lookups against a table of transitions, not one addition.

Supported Time Zones

• UTC: Coordinated Universal Time
• EST/EDT: US Eastern
• CST/CDT: US Central
• MST/MDT: US Mountain
• PST/PDT: US Pacific
• GMT/BST: London
• CET/CEST: Central Europe
• JST: Tokyo
• CST: China (Shanghai)
• GST: Gulf (Dubai)
• IST: India (Mumbai)
• AEDT/AEST: Sydney
• NZDT/NZST: Auckland

The table under the converter maps every time of day in the source zone to the same moment in the destination. It is there so you never have to type a second time: find the row you want and read across.

What each column means

• From: a time of day in the source zone. Every row is present, including the ones a clock change removed.
• To: the same moment, on the destination zone's clock.
• Day: whether that moment falls on the previous day, the same day or the next day. This is the detail people miss most often, and it is why an invite sent for “9am Friday” sometimes arrives on Thursday.

Why each row is worked out separately

A table built by adding one fixed difference to every row is wrong for every row after a clock change. Here each row is resolved on its own, so on a transition day the difference column genuinely changes part-way down and the rows that never happened are marked rather than quietly renamed.

Twice a year, in most places that observe daylight saving, the local clock stops being a reliable name for a moment. Converting a time in those two windows is the one case where a confident answer is usually a wrong one.

The hour that never happens

When clocks go forward, the wall clock jumps — in New York on 8 March 2026 it reads 01:59:59 and then 03:00:00. There is no 02:30 that day. Ask this converter for it and it says so, then shows you the moment one hour later that a calendar would have silently used instead.

The hour that happens twice

When clocks go back, an hour repeats: 01:30 in New York on 1 November 2026 happens once at 05:30 UTC and again at 06:30 UTC. Both are real, and they are an hour apart. The converter tells you the time is ambiguous and lets you choose which of the two you meant, rather than picking one and not mentioning it.

“New York is five hours behind London” is true for most of the year and false for about three weeks of it, because the two places change their clocks on different dates.

The United States moves its clocks on the second Sunday in March and back on the first Sunday in November. The European Union moves on the last Sunday in March and back on the last Sunday in October. Between those dates a US-to-Europe pair sits one hour closer than usual — twice a year, for about three weeks in spring and one week in autumn. Australia and New Zealand open a similar window against the northern hemisphere in their own spring. The converter lists those windows with their exact dates, because a single year-round number is the shape of a missed meeting.

UTC is the reference every other zone is described against. It never changes, has no daylight saving, and is what you should store a timestamp in.

GMT and UTC name the same clock reading for everyday purposes, but they are not interchangeable as labels: GMT is also the winter time of the United Kingdom, which switches to BST in summer. A file stamped “GMT” in July is ambiguous in a way one stamped “UTC” never is.

Offsets are not always whole hours

India is UTC+05:30, Nepal is UTC+05:45, the Chatham Islands are UTC+12:45 and go to +13:45 in summer, and Lord Howe Island shifts its clocks by thirty minutes rather than an hour. A converter that works in whole hours is wrong for around two billion people, so every number on this page is carried in minutes.

Abbreviations are convenient and unreliable. They are not standardised, several are used by more than one place, and most of them name only half of a zone's year.

• IST is India Standard Time, Irish Standard Time and Israel Standard Time.
• CST is used for US Central, China and Cuba.
• EST strictly means UTC−05:00 all year, but almost everybody who writes it means the Eastern Time of New York, which is EDT (UTC−04:00) for eight months of the year.
• BST is British Summer Time, and also Bangladesh Standard Time.

This is why the pair pages on this site are titled with a place as well as an abbreviation — “EST/EDT (New York)” rather than “EST” — and why the converter works in IANA identifiers such as America/New_York underneath. If you are writing a timestamp for a machine to read, use an offset or UTC, never an abbreviation.

The question behind most time zone conversions is not “what time is it there” but “when can we both talk”. The converter answers that directly.

Under the answer it maps a 09:00–17:00 working day in the source zone onto the destination clock, and names the hours when both sides are inside working hours. When there are none — UTC and Auckland share no working hour at all — it says so rather than suggesting the least-bad option, because a 3am call proposed by a tool is worse than no suggestion. Switch to Compare to put several places on one board and see the shared window shaded across the day.

A column of times pasted out of a spreadsheet, a log file or a schedule is converted in one pass, between the same two zones.

Rows can be mixed: a bare time of day is read against the date you chose, a full date and time is read as local in the source zone, and anything carrying its own offset, a Z, or a Unix timestamp is read as an absolute instant and converted from there. A row that cannot be read is refused with a reason and kept in place, so the output lines up with the input row for row.

Three ways to take a conversion out of the page.

• Calendar file (.ics): a one-hour event at the converted moment, which opens in Outlook, Apple Calendar or Google Calendar and lands at the right local time for whoever opens it.
• CSV: the hour-by-hour table, or the results of a converted list, as a spreadsheet.
• Shareable link: reopens this exact view — both zones, the date, the time and the clock format. The view is stored after the # in the URL, which browsers never send to a server, so the places you were comparing stay on your machine.

Pick a source and a destination, enter a time, and read the answer and the hour-by-hour table.

1. Choose the two places

   Search for a city, country or abbreviation on either side. Swap direction with one button.

2. Enter the date and time

   Type a time in the source zone, or press Now. Enter one that a clock change removed and the tool says so instead of guessing.

3. Read the answer and the table

   The converted time, the day it lands on and the difference appear at the top; the table below maps every hour of the day.

4. Take it with you

   Copy the conversion, or export a calendar file, a CSV of the table or a link that reopens this exact view.

These pairs have their own page, with the same converter, table and warnings set up for that direction. The converter at the top of this page handles every other combination of over four hundred zones.

Pairs with their own page. The converter above handles every other combination.

Whenever you coordinate people or systems in different regions.

Ideal Use Cases

• International Meetings: Schedule across zones
• Business Operations: Global coordination
• Travel Planning: Local arrival times
• Communication: Calls and messages
• Event Scheduling: Multi-region events

Context for better scheduling.

Key Statistics

• Roughly 24 primary longitudinal zones worldwide
• DST changes relative offsets during the year
• UTC is the standard reference
• Some regions use fractional-hour offsets
• Live conversion respects current DST rules

Improve accuracy when it matters.

Quality Considerations

• Confirm DST for both locations
• Check differences before invites
• Remember spring/fall transitions
• Use live conversion when possible
• Verify critical events twice

When Not to Use

• Historical instants without checking old DST rules
• Far-future rules that may change
• When legally binding time is required without authority
• Do not use as sole legal time proof

Our free time zone converter supports conversion between 419 time zones worldwide (second-accurate, IANA-based, DST-aware) including UTC, EST, PST, GMT, JST, Singapore, Mumbai, and more.

Supported Time Zones:

UTC, US zones, GMT/BST, CET/CEST, JST (Tokyo), China, SGT, Dubai, IST (Mumbai), Sydney, Auckland, and many more cities.

Pick a conversion from the grid, or use the All-in-One Timezone Converter for a visual timeline.

What is free, what is Pro, and what nothing can do.

• Free: converting between any two zones, the full hour-by-hour table, comparing four places at once, converting 100 rows in a list, and copying any result.
• Pro: comparing as many places as your device can lay out, converting lists as long as your device can hold, and calendar, CSV and link export.
• Neither: time zone rules more than a few years ahead. Governments change them at short notice, and no tool can know a rule that has not been announced.
• Neither: leap seconds. A clock reading of 23:59:60 cannot be represented and is refused rather than rounded.

No date, time, place or pasted list is uploaded. The conversion happens in the page you are looking at, using the time zone rules your device already carries for its own clock — which is also why the results agree with your operating system rather than with a server somewhere else. The shareable link puts its data in the URL fragment, the part after the # symbol, which browsers are specified never to send to a server.

• Time & date converters
• All-in-one timezone converter
• Current time in Tokyo
• Age calculator
• Date calculator
• Unix timestamp converter
• UTC to Mumbai