# Time Zone Converter

Convert one moment into as many time zones as you need — with daylight saving gaps and repeats flagged, each zone's next clock change, working-hours labels and the UTC arithmetic shown.

- Runs in your browser
- Shows every step
- DST gaps and overlaps flagged
- IANA zone names

## Quick answer

When it is **9:00 on October 8, 2026 in New York** (UTC-04:00, daylight saving time), it is **14:00 in London** (UTC+01:00), 22:00 in Tokyo (UTC+09:00) and 00:00 on October 9 in Sydney (UTC+11:00). Offsets and clock-change dates come from the IANA time zone database that browsers ship.

## About the Time Zone Converter

This converter takes one moment — a date and time on the wall clock in one place — and shows what the clocks read everywhere else you list: local time, day of the week, UTC offset, the zone's abbreviation, and whether that hour falls inside a normal working day. Every conversion goes through Coordinated Universal Time (UTC), and the arithmetic is printed under the results so you can check each line yourself.

It is built for the part that usually goes wrong: daylight saving time. If the time you enter is skipped when clocks spring forward, or happens twice when they fall back, the result says so and explains which instant it used. It also lists the next clock change in every zone, so you can see when a recurring meeting is about to shift for part of the team. Zone rules come from the IANA time zone database built into your browser, and nothing you type is sent to a server.

## How to use it

Enter the date and time as `2026-10-08T09:00`: year, month and day, then the 24-hour time after the `T`. It is read as a wall-clock time in the **From time zone**. You can also type `now`, or paste a timestamp that already carries its offset, such as `2026-10-08T13:00Z` or `2026-10-08T09:00-04:00`. In that case the offset in the timestamp decides the instant, and the From zone only supplies the first row of the table. Forms common in log files are tidied up first: a space in place of the `T`, fractions of a second (kept to the millisecond), offsets written as `+0000`, a trailing `UTC` or `GMT`, and Unix time in seconds. So `2026-10-08 13:00:00.123456 +0000` is read as `2026-10-08T13:00:00.123Z`, and `1791464400` is `2026-10-08T13:00:00Z`. A date that doesn't exist, such as February 30, is refused rather than rolled over into March.

Zones use IANA names in Region/City form, such as `America/Chicago` or `Asia/Singapore`. Each zone is named after one city in the area that shares its clock history, so most cities have no zone of their own: Mumbai is under `Asia/Kolkata`, Beijing under `Asia/Shanghai` and San Francisco under `America/Los_Angeles`. Start typing a city in either zone box and pick a suggestion. When a zone is named after the city you typed, such as Chicago or Singapore, leaving the From box or pressing Enter in the **Add a time zone** box fills in the full name, and the Add box appends it to the target list. The list takes up to 20 zones, one per line or separated by commas. **Use my time zone** fills in the zone your device reports, and **Use the current time** fills in the time right now on the From clock.

In the results, a **+1 day** or **−1 day** marker means the date in that zone differs from the date in the From zone. Zones on opposite sides of the date line can even be two days apart: 12:30 AM on Thursday, October 8 in Kiritimati (UTC+14:00) is 11:30 PM on Tuesday, October 6 in Pago Pago (UTC−11:00), marked **−2 days**. The label under each local time sorts it into Working (8 AM to 6 PM on a weekday), Early (6 to 8 AM), Evening (6 to 10 PM), Night or Weekend. Switch between 12-hour and 24-hour clocks at any time. The text block under the table is ready to paste into a calendar invite or a chat message, and _Copy link to these numbers_ saves the whole plan — time, zones and clock format — in the page address.

## Use cases

- **Scheduling a meeting across offices.** List every team's zone and use the working-hours labels to find a slot inside working hours for the most people — or to see exactly who is being asked to join at night.
- **Checking a recurring meeting around clock changes.** The next-change table shows when each zone moves its clocks, so you can warn people before a standing call shifts by an hour for some of them.
- **Announcing a launch, webinar or livestream.** Convert one start time into your audience's zones and paste the text block into the post or email.
- **Reading logs and incident timelines.** Paste a timestamp from a log line — ISO 8601, the space-separated form with an offset or UTC, or Unix seconds — to see what time it was for the on-call engineer, or turn local times from a report into UTC. A log time with no zone marker, such as `2026-10-08 13:00:00`, is read on the From clock, so set From to the zone the log was written in.
- **Calls while traveling.** Check whether a 9 AM call at home is before dawn or after midnight where you are going, and which day it falls on there.

## How the conversion works

A time zone is a set of rules for one region: which offset from UTC its clocks use, and on which dates that offset changes. Converting between two zones takes two steps through UTC:

UTC = local time − offset of the From zone

target time = UTC + offset of the target zone

In the example above, New York is on Eastern Daylight Time on October 8, 2026, which is UTC−04:00\. So 09:00 − (−04:00) = 13:00 UTC. Tokyo is UTC+09:00 all year, giving 10:00 PM there. Sydney is UTC+11:00 that week because its daylight saving started on October 4, so 13:00 UTC + 11:00 = 24:00 → 00:00 next day — midnight at the start of Friday, October 9, one calendar day ahead of New York. Kolkata shows that offsets are not always whole hours: India is UTC+05:30, so the call lands at 6:30 PM there.

The hard part is the offset itself. It depends on the date, because daylight saving moves it, and the rules differ by country and change over the years. That is why this tool asks for IANA names such as `America/New_York` rather than abbreviations: the name points at the region's whole history of rules, so the right offset can be picked for any date, past or future.

## Why 2:30 AM on March 8, 2026 doesn't exist in New York

In the United States, daylight saving time starts on the second Sunday of March at 2:00 AM local time. On March 8, 2026, New York clocks go from 1:59:59 AM straight to 3:00 AM. Every wall time from 2:00 to 2:59 that morning is skipped, so no clock in the city ever shows 2:30.

What should "2:30 AM" mean, then? This converter follows RFC 5545, the standard behind calendar invitations: a time that falls in the gap is read with the offset in force before the gap. Entered as `2026-03-08T02:30`, it becomes 02:30 − (−05:00) = 07:30 UTC, which New York clocks show as **3:30 AM EDT**. In effect the time moves forward by the length of the gap, and the result carries a note saying so.

The opposite happens on the first Sunday of November. On November 1, 2026, New York clocks reach 2:00 AM daylight time and fall back to 1:00 AM standard time, so every minute from 1:00 to 1:59 happens twice. `2026-11-01T01:30` could be 05:30 UTC (the first pass, still on daylight time) or 06:30 UTC (an hour later, on standard time). The same standard says to take the first occurrence, and the converter does; the note gives the second instant as well, and you can convert it by entering `2026-11-01T06:30Z`.

Scheduled jobs are where this bites hardest: depending on the scheduler, a task set for 2:30 AM local time may be skipped on the spring date, and one set for 1:30 AM may run twice on the autumn date. The [cron expression tool](https://17x7.com/tools/cron-expression/) lists a schedule's upcoming run times in any time zone — check the nights around a clock change before trusting a local-time schedule.

## Planning meetings when clocks change on different dates

The US and Europe both observe daylight saving time but switch on different Sundays. In 2026 the US moves forward on March 8 and back on November 1; the UK and the European Union move forward on March 29 and back on October 25\. For those few weeks the usual gap between New York and London is an hour smaller than normal. The Southern Hemisphere runs the opposite season: Sydney's daylight saving ended on April 5, 2026 and started again on October 4\. This table shows how far ahead of New York each city is on dates through 2026, worked out with the same code as the converter:

| Date (2026) | London | Kolkata     | Tokyo | Sydney |
| ----------- | ------ | ----------- | ----- | ------ |
| January 15  | 5 h    | 10 h 30 min | 14 h  | 16 h   |
| March 15    | 4 h    | 9 h 30 min  | 13 h  | 15 h   |
| April 15    | 5 h    | 9 h 30 min  | 13 h  | 14 h   |
| July 15     | 5 h    | 9 h 30 min  | 13 h  | 14 h   |
| October 28  | 4 h    | 9 h 30 min  | 13 h  | 15 h   |
| November 15 | 5 h    | 10 h 30 min | 14 h  | 16 h   |

New York to Sydney alone takes three different values in one year. A weekly call fixed at 5:00 PM in New York lands in Sydney at 9:00 AM in January, 8:00 AM in mid-March and 7:00 AM in July — always on the next calendar day. A few habits keep cross-zone meetings manageable:

- **Anchor a recurring meeting to one zone** and name that zone in the invite. Calendar software keeps a repeating event on its own zone's clock, so the local time moves for everyone else whenever either side changes clocks.
- **Re-check the weeks between clock changes**: mid-March and the last week of October into early November for US–Europe meetings. With Australia or New Zealand, check early April, when both end daylight saving (April 5 in 2026), and the turn of September into October, when New Zealand starts it on September 27 and the Australian states that observe it follow on October 4.
- **Use UTC for anything machines read** — logs, database timestamps, API payloads, deadlines shared across many zones. UTC never skips or repeats an hour.
- **Remember the places that don't change.** Arizona, apart from the Navajo Nation, stays on UTC−07:00 all year, so it matches California in summer and is an hour ahead of it in winter. India, China and Japan use one offset year-round, and Queensland skips the daylight saving the rest of eastern Australia observes.

## Limits of this converter

- It uses the time zone rules your browser ships. Governments sometimes change their rules at short notice; a future date in an affected zone can be wrong until your browser updates its data.
- Abbreviations come from the locale data your browser ships. US English has short names mostly for North American zones, so any other zone is looked up again in the English of its own region — CET and BST from British English, AEST from Australian, IST from Indian, WIB from Indonesian — or, where only the local language has one, in that language: JST in Japanese, BRT for São Paulo in Brazilian Portuguese, ART, COT and PET in the Spanish of Argentina, Colombia and Peru. Zones with no short name in either, such as Shanghai and Kathmandu, appear as `GMT+8`\-style labels, so the long name under each zone is the better guide. Abbreviations are labels only and are not accepted as input — `IST` alone could mean India, Israel or Irish Standard Time, so typing one gets you a suggested region name instead of a guess.
- Dates from 1900 to 2200 are accepted. Before a country adopted standard time its clocks ran on local mean time, set by the sun, and those offsets are shown to the second: Liberia used UTC−00:44:30 until 1972, so noon in Monrovia on June 1, 1960 was 12:44:30 UTC.
- The "Working" label means 8 AM to 6 PM, Monday to Friday, local time. Workweeks differ — in several Middle Eastern countries the weekend is Friday and Saturday — so treat the labels as a first filter.
- The next-change table looks 12 months ahead from the converted time. Leap seconds are ignored, as they are by nearly all computer clocks.

A JSON version of the core conversion — IANA zone names and a time in; the UTC instant and each zone's local time, offset and abbreviation out — is available to scripts and AI agents as the `convert_time` tool on the [developer page](https://17x7.com/developers/). It checks zone names with the same rules as this page, so abbreviations such as `BST` are refused there too. Log-style timestamps and Unix seconds, the working-hours labels, the clock-change table and the written-out math are features of this page only.

## Sources

- [IANA — Time Zone Database](https://www.iana.org/time-zones) — checked 2026-10-10

## Frequently asked questions

How do I convert a time between time zones by hand?

Subtract the From zone's UTC offset to get UTC, then add the target zone's offset. 9:00 AM in New York in October (UTC−04:00) is 13:00 UTC; add Tokyo's +09:00 and you get 10:00 PM. The catch is knowing the right offset for that date, which depends on daylight saving rules — that is the part this tool looks up for you.

Why does it use names like America/New\_York instead of EST?

Abbreviations are ambiguous and incomplete. CST can mean US Central, China Standard or Cuba Standard Time, and IST can mean India, Israel or Irish Standard Time. EST also names only New York's winter offset; from March to November the city is on EDT. An IANA zone name identifies a region and its full set of daylight saving rules, so the offset comes out right on any date. If you type an abbreviation such as BST, the converter refuses it and suggests a region name, Europe/London in that case, rather than guessing which one you meant.

What happens if I enter a time that daylight saving skips?

The time moves forward by the length of the gap and a note explains it. 2:30 AM on March 8, 2026 in New York doesn't exist; it is read with the offset from before the gap (UTC−05:00) and comes out as 3:30 AM EDT, or 07:30 UTC. Calendar software that follows RFC 5545 does the same.

What about a time that happens twice when clocks fall back?

The converter uses the first occurrence. 1:30 AM on November 1, 2026 in New York is taken as 1:30 AM EDT, which is 05:30 UTC, and the note gives the second one, 06:30 UTC. To convert the later one, enter that UTC time with a Z on the end.

Is GMT the same as UTC?

For converting clock times, yes: both have a zero offset. UTC is the atomic-clock standard that computers, aviation and science use, while GMT is also the name of the UK's winter time. Note that the Europe/London zone is on GMT only in winter — in summer it is British Summer Time, UTC+01:00.

Why is Etc/GMT+5 five hours behind UTC?

The Etc/GMT zones follow an old POSIX convention with the sign inverted: Etc/GMT+5 means UTC−05:00, and Etc/GMT-9 means UTC+09:00\. They never observe daylight saving, which suits ships at sea or servers pinned to a fixed offset. For a city, use its regional name instead.

Does it handle half-hour and 45-minute offsets?

Yes. India is UTC+05:30, Nepal is UTC+05:45 and Newfoundland is UTC−03:30 in winter. Lord Howe Island even moves its clocks by only 30 minutes for daylight saving. The arithmetic is done in minutes, so these come out exactly.

Can I convert the current time?

Yes. Type now in the date and time field, or press Use the current time. The difference matters when you share a link: a link saved with now converts whatever moment it is opened, while the button fills in a fixed time, so the link keeps showing the same moment.

**Disclaimer.** Conversions use the IANA time zone rules built into your browser; if a government changes its clock rules after that data was published, future times for that zone can be off until your browser updates.

Last updated October 15, 2026. Found a mistake? [Tell us](https://17x7.com/contact/) — corrections ship the same week.

---

Source: https://17x7.com/tools/time-zone-converter/ · Last updated: 2026-10-15