Time Zone Converter

Scheduling across borders takes three inputs.

1. Set Date and time. It opens with the current time, and the date matters because many zones change their offset part way through the year.
2. Choose From time zone. It starts as the zone your device uses, and the dropdown lists every IANA zone your browser knows, such as Europe/London, America/New_York or Asia/Kolkata. Click the list and type the first letters of a city to jump to it.
3. Choose To time zone, which starts as UTC.
4. Read the large converted time, then the rows below it.

The rows show each zone's local time with its UTC offset and a daylight saving label where it applies, the difference in hours, the same moment in UTC and a Unix timestamp. The weekday and date are included, so a change of day is obvious.

Each zone is defined by its offset from Coordinated Universal Time. The tool reads your input as local time in the From zone, finds the matching instant in UTC by removing that zone's offset on that date, then adds the offset of the To zone: target = source - source offset + target offset. It takes offsets from the time zone database built into your browser, so it follows daylight saving rules for the date you choose, and no rule table is stored on this site.

Worked examples:

• 3:00 pm on Wednesday 15 July 2026 in New York (UTC-04:00) is 8:00 pm in London (UTC+01:00), a difference of 5 hours.
• 12:00 noon on 10 March 2026 in London is 5:30 pm in Kolkata, a difference of 5.5 hours.
• 9:00 am on Tuesday 20 January 2026 in Sydney (UTC+11:00) is 2:00 pm on Monday 19 January in Los Angeles, 19 hours behind.

The last example shows why the weekday matters: the date in one place can be the previous day in another.

Treat the table as a reminder, not a source: rules change, and the tool reads the current rules from your browser for the exact date. The Unix timestamp row is the same for everyone, wherever they are, which makes it handy for developers comparing log entries. The tool converts a single moment, so for a recurring meeting check the conversion again after either side changes its clocks, because the gap between the two cities may shift by an hour.

A few habits avoid the usual mix-ups.

• Use city names, not abbreviations. CST can mean Central Standard Time or China Standard Time, and IST is used in India, Ireland and Israel. Names such as America/Chicago are unambiguous.
• Check the date, not just the time. The US and Europe change clocks on different weekends, so New York and London are usually five hours apart but four for a short spell in March and again in late October or early November.
• Remember odd offsets. India is UTC+5:30, Nepal is UTC+5:45 and parts of Australia use UTC+9:30.
• Avoid the changeover hour. When clocks go forward, one local hour does not exist. For 2:30 am on 8 March 2026 in New York, the tool returned a time one hour earlier on the clock. Pick a time outside that hour when it matters.

If a deadline is in another zone, convert it first and then use the date difference calculator to see what remains. The Unix timestamp converter turns the timestamp row into a readable date, and the time converter changes hours into minutes or days. For meetings, the countdown timer can run to the start time.