Time Zone Converter
Last reviewed: 20 November 2026. Reviewed every 180 days; next review due 19 May 2027.
How to use the Time Zone Converter
This time zone converter turns a time you enter in one place into the same moment in another place. It covers 40 major cities and regions, and it already includes daylight saving time, so the offsets it shows are the ones in force on the date you pick. It converts only the times you enter. It never shows the current time anywhere, and it makes no live lookup: every rule it uses is built into the tool.
There are two ways to use it. Convert a time moves one moment between two places. Meeting planner shows that moment in up to four other places at once and flags any place where it lands outside working hours.
To convert a time between two places:
- Pick the date of the time you want to convert. Dates run from 2023 to 2099, because time zone rules change by law and older dates may follow different rules.
- Enter the time on the 24-hour clock. 15:00 is 3 PM and 09:00 is 9 AM.
- Pick the place where that time is read in the From list, and the place you want it shown in the To list. The Swap button reverses the two places, and the quick chips below the To list fill in popular pairs such as New York to London.
- Press Convert. The result shows the converted time in large type, the same moment in UTC, the time difference between the two places, and whether the date changes.
To plan a meeting across time zones:
- Open the Meeting planner tab and enter the meeting date and time in your own time zone.
- Pick your time zone, then pick 1 to 4 other places. Leave the places you do not need on None.
- Press Convert. Each place gets a row with its local time, its date, and a badge that says Working hours or Outside working hours. A bar under each row shows where the local time falls in the day, with the 8:00 AM to 6:00 PM working window shaded.
- If a place falls outside working hours, change the meeting time and convert again until every place is inside the window.
If the tool shows an error instead of a result, read the message: it names the exact problem. The most common errors are a date that does not exist, such as 30 February, a time outside the 24-hour clock, and a time that falls inside a daylight saving gap, when the clocks jump forward and an hour of the day never happens. The Common mistakes section below explains the daylight saving traps in full.
How it works
Every conversion goes through UTC, the world reference time. The tool takes the time you enter, works out the offset in force in the starting place on that date, and turns the time into UTC. Then it works out the offset in force in the destination place at that same UTC moment and turns the UTC time into local time there. Because both offsets are read for the exact date and moment you entered, daylight saving time is handled automatically. You never have to know whether a place is on daylight time on your date. The tool knows.
An offset is the difference between local time and UTC, written as UTC plus or minus hours and minutes. New York is UTC-5 in winter, which means its clocks read 5 hours behind UTC. Tokyo is UTC+9 all year, which means its clocks read 9 hours ahead of UTC. Most offsets are whole hours, but 13 of the 40 offsets in use around the world in 2026 are not: they run 30 or 45 minutes off the hour. India is UTC+5:30, Nepal is UTC+5:45, and the Chatham Islands are UTC+12:45 in winter and UTC+13:45 in summer. This tool keeps those half-hour and 45-minute offsets exact, so a conversion to Mumbai or Kathmandu never lands 30 or 45 minutes out.
Daylight saving time moves the clocks forward, usually by one hour, for part of the year. The tool computes the changeover dates from the rule for each region, for the year you entered, rather than looking them up in a table of fixed dates. The rules it uses are: the United States and most of Canada, from the second Sunday in March to the first Sunday in November; the European Union and the United Kingdom, from the last Sunday in March to the last Sunday in October, both changes at 01:00 UTC; Australia, from the first Sunday in October to the first Sunday in April; New Zealand, from the last Sunday in September to the first Sunday in April; Egypt, from the last Friday in April to the last Thursday in October; Lord Howe Island, which shifts by only 30 minutes; and the Chatham Islands, which change at 2:45 AM because they sit 45 minutes ahead of mainland New Zealand. Vancouver followed the United States rule through 2026 and then stopped changing its clocks, as the daylight saving section below explains.
Here is a worked example. Take 3:00 PM on Friday 20 November 2026 in New York. New York is on Eastern Standard Time that day, UTC-5, so 3:00 PM there is 20:00 UTC. London is on Greenwich Mean Time in November, UTC+0, so 20:00 UTC is 8:00 PM in London. The tool shows 8:00 PM on Friday 20 November 2026 in London, a difference of 5 hours, and no date change.
A second example crosses the date line. Take 9:00 AM on Monday 20 July 2026 in Los Angeles. Los Angeles is on Pacific Daylight Time in July, UTC-7, so 9:00 AM there is 16:00 UTC. Sydney is on Australian Eastern Standard Time in July, UTC+10, so 16:00 UTC is 2:00 AM the next day, Tuesday 21 July 2026, in Sydney. The tool shows the 2:00 AM result with a Next day label, because the date in Sydney is one day ahead of the date in Los Angeles.
The meeting planner adds one more idea: the working window. It treats 8:00 AM to 6:00 PM local time as working hours. A time at 8:00 AM counts as inside the window, and a time at 6:00 PM counts as outside it, because a meeting that starts at 6:00 PM runs into the evening. The window is a planning guide, not a rule about any country: working days differ around the world, and in some places the working week does not run Monday to Friday. If your colleagues keep different hours, read the local times in the rows and judge for yourself. If you need to work out how long a meeting or shift lasts once you have picked its start and end times, the Hours Calculator does that arithmetic.
What your result means
In Convert mode the big line is the converted time in the destination place, on the 24-hour clock in the details and in 12-hour form in the headline, with its date and weekday underneath. Under that, the summary sentence repeats the whole conversion in words, naming both places, both time zone abbreviations, and both offsets, so you can read the answer without doing any arithmetic. Below the summary, the details list shows five lines: your time, the converted time, the same moment in UTC, the time difference, and the day change.
The UTC line is the check on everything else. UTC never observes daylight saving time, so the same moment always has one UTC reading. If you want to verify a result against another source, compare the UTC time: any correct converter must agree on it, whatever it says about local times.
The time difference line says how far ahead or behind the destination is, in hours and minutes, for example "London is 5 hours ahead of New York" or "Los Angeles is 3 hours behind New York". When the two places keep the same time, it says so. Note that the difference is the one in force on your date. It is not a fixed property of the two places: the same pair can sit 4 hours apart in one month and 5 hours apart in another, because their daylight saving seasons start and end on different dates. The daylight saving section gives the New York to London example in full.
The day change line says Same day, Next day, or Previous day. It compares the calendar date of the result with the calendar date you entered. A conversion from the Americas to Asia usually lands on the next day, and a conversion from Asia to the Americas usually lands on the previous day. The date can also change by a year: 12:30 AM on 1 January in Tokyo is 7:30 AM on 31 December the year before in Los Angeles.
Two special messages can appear. If the time you entered happens twice in the starting place, because the clocks went back that morning, the tool shows a warning and uses the first occurrence, in daylight time. If the time you entered does not exist in the starting place, because the clocks jumped forward over it, the tool shows an error instead of a result and names the jump, for example "2:30 AM on Sunday 8 March 2026 does not exist in New York: clocks jump forward from 2:00 AM to 3:00 AM when daylight saving time begins." Both messages are explained with examples in the Common mistakes section.
In Meeting planner mode each row shows one place: its local time in large type, its date and weekday, its time zone abbreviation and offset, and a badge. The badge is green and says Working hours when the local time falls between 8:00 AM and 6:00 PM, and red and says Outside working hours when it does not. The bar under the row marks the local time on a 24-hour line, with the working window shaded, so you can see at a glance how far a time sits from working hours. The summary above the rows counts how many places fall outside the window. A meeting where every place is inside the window is the goal; where that is impossible, the rows show which places take the early morning or the late evening, so the awkward slot can be shared around instead of landing on the same people every week.
Time zones explained
A time zone is a region that keeps the same standard time. The world is divided into zones so that noon roughly matches the middle of the day in each place, but the boundaries follow borders, not lines of longitude: whole countries often keep one time even when they span several zones, and some zones bend around provinces and states. China keeps a single time, UTC+8, from its eastern seaboard to its western border, a span that covers five geographic zones. The United States mainland uses four. Russia uses eleven.
Offsets are counted from UTC, Coordinated Universal Time, which is the modern form of Greenwich Mean Time and the reference every zone is measured against. In 2026 there were 40 distinct UTC offsets in use around the world, running from UTC-12 to UTC+14, a spread of 26 hours. Thirteen of those 40 offsets are not whole hours: they sit 30 or 45 minutes off the hour. The counts come from the IANA time zone database, the same data that phones, computers, and calendar software use. The 13 non-whole-hour offsets in use in 2026 were UTC-9:30, UTC-3:30, UTC-2:30, UTC+3:30, UTC+4:30, UTC+5:30, UTC+5:45, UTC+6:30, UTC+8:45, UTC+9:30, UTC+10:30, UTC+12:45, and UTC+13:45.
The table below lists every place this tool covers, with its standard offset, its daylight offset, and its daylight saving rule. Standard time is the winter offset in the northern hemisphere and the summer offset in the southern hemisphere, where the seasons run the other way round. Where a place does not observe daylight saving time, the two offsets are the same.
| Place | Standard time | Daylight time | Daylight saving |
|---|---|---|---|
| New York, USA | UTC-5 (EST) | UTC-4 (EDT) | Second Sunday in March to first Sunday in November |
| Chicago, USA | UTC-6 (CST) | UTC-5 (CDT) | Second Sunday in March to first Sunday in November |
| Denver, USA | UTC-7 (MST) | UTC-6 (MDT) | Second Sunday in March to first Sunday in November |
| Los Angeles, USA | UTC-8 (PST) | UTC-7 (PDT) | Second Sunday in March to first Sunday in November |
| Anchorage, USA | UTC-9 (AKST) | UTC-8 (AKDT) | Second Sunday in March to first Sunday in November |
| Honolulu, USA | UTC-10 (HST) | UTC-10 (HST) | No daylight saving time |
| Phoenix, USA | UTC-7 (MST) | UTC-7 (MST) | No daylight saving time |
| Toronto, Canada | UTC-5 (EST) | UTC-4 (EDT) | Second Sunday in March to first Sunday in November |
| Vancouver, Canada | UTC-8 (PST) | UTC-7 (PDT) | Through 2026 only. Permanent UTC-7 (PCT) from 1 November 2026 |
| Halifax, Canada | UTC-4 (AST) | UTC-3 (ADT) | Second Sunday in March to first Sunday in November |
| St. John's, Canada | UTC-3:30 (NST) | UTC-2:30 (NDT) | Second Sunday in March to first Sunday in November |
| Mexico City, Mexico | UTC-6 (CST) | UTC-6 (CST) | No daylight saving time since 2022 |
| Bogota, Colombia | UTC-5 (COT) | UTC-5 (COT) | No daylight saving time |
| Sao Paulo, Brazil | UTC-3 (BRT) | UTC-3 (BRT) | No daylight saving time since 2019 |
| Buenos Aires, Argentina | UTC-3 (ART) | UTC-3 (ART) | No daylight saving time |
| London, UK | UTC+0 (GMT) | UTC+1 (BST) | Last Sunday in March to last Sunday in October |
| Paris, France | UTC+1 (CET) | UTC+2 (CEST) | Last Sunday in March to last Sunday in October |
| Berlin, Germany | UTC+1 (CET) | UTC+2 (CEST) | Last Sunday in March to last Sunday in October |
| Athens, Greece | UTC+2 (EET) | UTC+3 (EEST) | Last Sunday in March to last Sunday in October |
| Moscow, Russia | UTC+3 (MSK) | UTC+3 (MSK) | No daylight saving time |
| Istanbul, Turkey | UTC+3 (TRT) | UTC+3 (TRT) | No daylight saving time |
| Reykjavik, Iceland | UTC+0 (GMT) | UTC+0 (GMT) | No daylight saving time |
| Cairo, Egypt | UTC+2 (EET) | UTC+3 (EEST) | Last Friday in April to last Thursday in October |
| Johannesburg, South Africa | UTC+2 (SAST) | UTC+2 (SAST) | No daylight saving time |
| Dubai, UAE | UTC+4 (GST) | UTC+4 (GST) | No daylight saving time |
| Mumbai, India | UTC+5:30 (IST) | UTC+5:30 (IST) | No daylight saving time |
| Karachi, Pakistan | UTC+5 (PKT) | UTC+5 (PKT) | No daylight saving time |
| Dhaka, Bangladesh | UTC+6 (BST) | UTC+6 (BST) | No daylight saving time |
| Kathmandu, Nepal | UTC+5:45 (NPT) | UTC+5:45 (NPT) | No daylight saving time |
| Bangkok, Thailand | UTC+7 (ICT) | UTC+7 (ICT) | No daylight saving time |
| Singapore | UTC+8 (SGT) | UTC+8 (SGT) | No daylight saving time |
| Shanghai, China | UTC+8 (CST) | UTC+8 (CST) | No daylight saving time |
| Tokyo, Japan | UTC+9 (JST) | UTC+9 (JST) | No daylight saving time |
| Perth, Australia | UTC+8 (AWST) | UTC+8 (AWST) | No daylight saving time |
| Adelaide, Australia | UTC+9:30 (ACST) | UTC+10:30 (ACDT) | First Sunday in October to first Sunday in April |
| Brisbane, Australia | UTC+10 (AEST) | UTC+10 (AEST) | No daylight saving time |
| Sydney, Australia | UTC+10 (AEST) | UTC+11 (AEDT) | First Sunday in October to first Sunday in April |
| Auckland, New Zealand | UTC+12 (NZST) | UTC+13 (NZDT) | Last Sunday in September to first Sunday in April |
| Chatham Islands, New Zealand | UTC+12:45 (CHAST) | UTC+13:45 (CHADT) | Last Sunday in September to first Sunday in April, changing at 2:45 AM |
| Lord Howe Island, Australia | UTC+10:30 (LHST) | UTC+11 (LHDT) | First Sunday in October to first Sunday in April, 30 minute shift |
The half-hour and 45-minute zones deserve a closer look, because they are where rough converters go wrong. St. John's in Newfoundland is UTC-3:30 in winter, the only half-hour zone in North America. Adelaide is UTC+9:30 in winter and UTC+10:30 in summer. Mumbai is UTC+5:30 all year, and Kathmandu is UTC+5:45 all year, the only 45-minute offset on the Asian mainland. The Chatham Islands are UTC+12:45 in winter and UTC+13:45 in summer, which makes them 45 minutes ahead of mainland New Zealand all year and one of the first inhabited places on Earth to see each new day. Lord Howe Island shifts by only 30 minutes for daylight saving, from UTC+10:30 to UTC+11, so in summer it keeps exactly the same time as Sydney.
Time zone abbreviations are not unique, and that causes real confusion. BST means British Summer Time, UTC+1, in London, and it also means Bangladesh Standard Time, UTC+6, in Dhaka: the same three letters, five hours apart. CST means Central Standard Time, UTC-6, in Chicago and Mexico City, and it also means China Standard Time, UTC+8, in Shanghai: a 14-hour difference hiding behind identical letters. IST is India Standard Time, UTC+5:30, and it is also Irish Standard Time, UTC+1, in Dublin in summer. When a time matters, always check the offset, not just the letters. This tool shows both, on every result.
A few major cities are not listed because they keep exactly the same time as a listed city all year. Seoul keeps the same time as Tokyo, UTC+9, all year. Hong Kong keeps the same time as Shanghai and Singapore, UTC+8, all year. Melbourne keeps the same time as Sydney, including daylight saving. Dublin keeps the same time as London. Madrid keeps the same time as Paris and Berlin. Jakarta keeps the same time as Bangkok. Lima keeps the same time as Bogota. Lagos keeps the same time as Paris and Berlin in winter, UTC+1, with no daylight saving. If the city you want is missing, convert with its twin and the answer is the same.
Daylight saving time around the world
Daylight saving time moves the clocks forward, usually by one hour, during the brighter months, so that an hour of daylight shifts from the early morning, when most people are asleep, to the evening. The idea is old: it was first used widely during the First World War to save lighting fuel. Today it is used mainly in North America, Europe, and parts of Australia and New Zealand, plus a few other countries. Most of the world, including all of Asia except a few places, most of Africa, and most of South America, does not observe it at all.
The rules differ by region, and the tool computes each changeover from the rule for the year you enter. The table below gives the 2026 dates for each rule family. Every date is a Sunday except in Egypt, where the changes fall on a Friday.
| Region | Daylight saving starts in 2026 | Daylight saving ends in 2026 |
|---|---|---|
| United States and Canada (most places) | Sunday 8 March, 2:00 AM local time | Sunday 1 November, 2:00 AM local time |
| European Union and United Kingdom | Sunday 29 March, 01:00 UTC | Sunday 25 October, 01:00 UTC |
| Australia (New South Wales, Victoria, South Australia, Tasmania, ACT) | Sunday 4 October, 2:00 AM local time | Sunday 5 April, 3:00 AM local time |
| New Zealand | Sunday 27 September, 2:00 AM local time | Sunday 5 April, 3:00 AM local time |
| Chatham Islands | Sunday 27 September, 2:45 AM local time | Sunday 5 April, 3:45 AM local time |
| Egypt | Friday 24 April, midnight | Friday 30 October, midnight |
| Lord Howe Island | Sunday 4 October, 2:00 AM local time (30 minute shift) | Sunday 5 April, 2:00 AM local time (30 minute shift) |
The dates in the table are the ones in force for 2026. The 2027 dates follow from the same rules: the United States and Canada start on Sunday 14 March 2027 and end on Sunday 7 November 2027, and the European Union and the United Kingdom start on Sunday 28 March 2027 and end on Sunday 31 October 2027. The tool computes all of these from the rules, so it stays correct for any year in its range without a table of dates.
The southern hemisphere runs the seasons the other way round, so its daylight saving runs the other way round too. Sydney and Auckland move their clocks forward in October and September and back in April, which is their autumn. That has a consequence people miss: the time difference between a northern city and a southern city changes by two hours over the year, not one. Sydney is 11 hours ahead of London in January, when Sydney is on daylight time and London is on standard time, and 9 hours ahead in July, when Sydney is on standard time and London is on daylight time. A weekly call fixed at a Sydney time drifts two hours against London across the year if nobody adjusts it.
The gap between two northern cities changes too, because their seasons start and end on different weekends. New York and London are 5 hours apart for most of the year, but for three weeks each spring and one week each autumn they are 4 hours apart. In 2026 the United States moved its clocks forward on 8 March while Europe waited until 29 March, so from 8 to 29 March the gap was 4 hours. Then Europe moved its clocks back on 25 October while the United States waited until 1 November, so from 25 October to 1 November the gap was 4 hours again. Anyone who books a regular New York to London call on a fixed 5-hour gap will be an hour out for a month of the year.
Daylight saving rules change by law, and the changes are not rare. Mexico abolished daylight saving time in most of the country with effect from 30 October 2022, so Mexico City now stays on UTC-6 all year; only the state of Baja California and a few municipalities on the northern border still follow the United States dates. Brazil abolished it in 2019 by Decree No. 9,772 of 25 April 2019, after a final season that ended on 17 February 2019, so Sao Paulo now stays on UTC-3 all year. Egypt went the other way: it brought daylight saving back in 2023 under Law No. 24 of 2023, from the last Friday in April to the last Thursday in October, changing at midnight, so the spring jump happens at 12:00 AM and the autumn repeat hour is 11:00 PM.
The newest change in this tool's coverage is in Canada. British Columbia sprang forward for the last time on 8 March 2026 and then never fell back: on 1 November 2026 the clocks stayed where they were, and Vancouver now keeps UTC-7 all year. The province calls the year-round time Pacific Time, abbreviated PCT. Time zone databases label the same UTC-7 offset as MST, which is why some clocks and calendars show Vancouver as MST. The practical effect is that Vancouver is one hour ahead of Seattle and Los Angeles in winter, from November to March, and on the same time as them in summer. Alberta and Manitoba made the same move on the same day: Edmonton now keeps UTC-6 all year and Winnipeg keeps UTC-5 all year, each holding the offset it used to reach only in summer. This tool models the Vancouver change exactly, including the fact that 1:30 AM on 1 November 2026 happened only once in Vancouver, in daylight time, because the fall-back that would have repeated it never took place.
The Chatham Islands are a smaller curiosity with the same lesson. They change their clocks at the same instant as mainland New Zealand, 14:00 UTC on the Saturday, but because they sit 45 minutes ahead of the mainland, the change falls at 2:45 AM local time instead of 2:00 AM. Their spring gap runs from 2:45 AM to 3:45 AM, and their autumn repeat hour is 2:45 AM to 3:45 AM. A converter that assumes every place changes at 2:00 AM gets Chatham wrong by 45 minutes on two mornings a year.
Because rules change by law, no time zone database is ever final. The United States National Institute of Standards and Technology puts it plainly: "There is no single body that regulates time zones or daylight saving time around the world. Some countries provide little or no notice when they change their DST status and/or date rules." This tool is built on the IANA time zone database, release 2026e, and its rules are reviewed every 180 days. For a legally binding time, a flight, or a deadline, check the official source for the place concerned as well.
The international date line
The international date line is the boundary where one calendar day ends and the next begins. It runs roughly along the 180th meridian, through the middle of the Pacific Ocean, but it is not a straight line and it is not defined by international law: countries choose which side of it they sit on, and the line bends around them. Crossing it westward moves the calendar forward a day; crossing it eastward moves it back a day. The time of day does not change at the line, only the date.
The line has moved within living memory. Kiribati moved the line eastward in 1995 so that its whole island nation would share one day, creating the UTC+14 zone, the furthest ahead of UTC anywhere on Earth. Samoa moved across the line in 2011: the country skipped Friday 30 December 2011 entirely, going to sleep on Thursday 29 December and waking up on Saturday 31 December, so that its working week would line up with Australia and New Zealand instead of the United States. The result of these choices is that the widest spread of local times on Earth is 26 hours, from UTC-12 to UTC+14, and at some hours of the day three different calendar dates are in use at once: every day between 10:00 and 10:59 UTC, parts of the world are on yesterday, today, and tomorrow at the same time.
For scheduling, the date line is the reason a conversion can land on a different day from the one you entered, and the reason the meeting planner shows a date on every row instead of only a time. A 9:00 AM call set in Los Angeles on a Monday is a 2:00 AM call in Sydney on Tuesday, and a 9:00 AM call set in Sydney on a Monday is a 4:00 PM call in Los Angeles on Sunday, the day before. The day change labels on the result, Same day, Next day, and Previous day, exist so that the date is never left to guesswork. When you send a meeting invite across the date line, always include the date in the invite, not only the time: "2:00 AM Tuesday" is unambiguous where "2:00 AM" is not.
The date line also explains why the time difference between two places is not always the number you would get by subtracting their offsets in your head. The Chatham Islands at UTC+13:45 and Los Angeles at UTC-8 are 21 hours and 45 minutes apart by the clock, and a noon call in the Chathams lands at 2:15 PM the day before in Los Angeles. The size of the gap is real, but the direction matters as much as the size: ahead and behind are not interchangeable, and this tool always states the direction in words.
Common mistakes to avoid
The most common mistake is treating a time difference as fixed. It is not. The gap between New York and London is 5 hours for most of the year and 4 hours for four weeks of it. The gap between Sydney and London swings by two hours across the year. The gap between Phoenix and Denver is zero in winter and one hour in summer, because Denver observes daylight saving and Phoenix does not. If you keep a regular call across zones, check the gap every time the clocks change in either place, and check it again a few weeks later, because the two places rarely change on the same weekend.
The second mistake is booking a meeting in an hour that does not exist. On the morning the clocks go forward, one hour of the day is skipped: in New York on Sunday 8 March 2026 the clocks jumped from 2:00 AM to 3:00 AM, so 2:30 AM never happened. A meeting, a flight, or a deadline set for 2:30 AM that morning has no meaning, and calendar software will either move it or fail. This tool refuses such a time and names the jump, so you can pick a real time instead. The trap is not limited to 2:00 AM: in Cairo the spring jump happens at midnight, so 12:30 AM on Friday 24 April 2026 does not exist, and in the Chatham Islands the jump runs from 2:45 AM to 3:45 AM.
The third mistake is the mirror image: booking in an hour that happens twice. On the morning the clocks go back, one hour repeats: in New York on Sunday 1 November 2026 the clocks fell back from 2:00 AM to 1:00 AM, so 1:30 AM happened twice, once in daylight time and once in standard time, an hour apart. A meeting set for 1:30 AM that morning is ambiguous unless you say which occurrence you mean. This tool uses the first occurrence, in daylight time, and warns you. If the exact occurrence matters, for a shift handover or a timed log entry, say so in words: "1:30 AM daylight time" or "1:30 AM standard time". Note that Vancouver had no repeated hour on 1 November 2026, because British Columbia never fell back that day.
The fourth mistake is trusting a time zone abbreviation. BST is British Summer Time in London and Bangladesh Standard Time in Dhaka. CST is Central Standard Time in Chicago and China Standard Time in Shanghai. IST is India Standard Time in Mumbai and Irish Standard Time in Dublin. The letters alone do not identify a zone, and a meeting invite that says only "3 PM CST" could mean 3 PM in Chicago, Mexico City, or Shanghai, three times 14 hours apart. Always give the city or the offset with the abbreviation, and check the offset on the result this tool shows.
The fifth mistake is assuming that places in the same country change their clocks together. They often do not. In the United States, Arizona and Hawaii do not observe daylight saving time while the rest of the country does, so Phoenix is on the same time as Denver in winter and an hour behind it in summer. In Australia, Queensland, Western Australia, and the Northern Territory do not observe it while the south-eastern states do, so Brisbane is on the same time as Sydney in winter and an hour behind it in summer. In Canada, most of the country still changes its clocks, but British Columbia, Alberta, and Manitoba stopped in 2026. In Brazil, daylight saving ended nationwide in 2019. Always check the place, not the country.
The sixth mistake is forgetting that the date can change, and with it the weekday. A call at 9:00 AM Monday in Los Angeles is 2:00 AM Tuesday in Sydney: the Sydney side is not only up in the middle of the night, it is up on a different day. A deadline of Friday in New York can already be Saturday in Tokyo. This tool prints the weekday and the date on both sides of every conversion for exactly this reason. To count the days between two dates, for example between a deadline and today, use the Date Calculator.
The seventh mistake is relying on rules learned years ago. Time zone rules change by law, and the changes keep coming: Mexico in 2022, Egypt in 2023, three Canadian provinces in 2026. A converter built on a fixed table of offsets from a few years ago will give the wrong answer for Vancouver in winter, for Mexico City in summer, and for Cairo in either season. This tool is reviewed every 180 days against the IANA time zone database, and its year range stops at 2099 because rules that far ahead are predictions, not promises. If a date matters legally, check the official source for the place as well.
The eighth mistake is scheduling by your own working hours alone. The working day in New York and the working day in Mumbai barely touch: in winter their 8:00 AM to 6:00 PM windows do not overlap at all, and in summer the only shared window is 30 minutes, 8:00 to 8:30 AM in New York, which is 5:30 to 6:00 PM in Mumbai. A meeting that suits one side will often fall outside working hours on the other, and the fair answer is to share the awkward slot around the team rather than fixing a time that always punishes the same people. The meeting planner exists for exactly this check: run it before you send the invite, not after.
Frequently asked questions
How do I convert a time between two time zones?
Enter the date and time in the starting place, pick the starting place and the destination place from the lists, and press Convert. The tool turns your time into UTC using the offset in force in the starting place on that date, then turns that UTC time into local time in the destination place using the offset in force there at the same moment. Daylight saving time is included automatically, and the result shows the converted time, the same moment in UTC, the time difference, and whether the date changes.
What is the time difference between New York and London?
London is 5 hours ahead of New York for most of the year, and 4 hours ahead for four weeks of it. In 2026 the United States moved its clocks forward on 8 March while Europe waited until 29 March, so the gap was 4 hours from 8 to 29 March, and Europe moved its clocks back on 25 October while the United States waited until 1 November, so the gap was 4 hours again from 25 October to 1 November. Enter your exact date in the converter to get the gap in force on that day.
Why does the time difference between two cities change during the year?
It changes because the two places start and end daylight saving time on different dates, or because only one of them observes it at all. New York and London are 5 hours apart most of the year and 4 hours apart when one has changed its clocks and the other has not. Sydney and London swing by two hours across the year, from 11 hours apart in January to 9 hours apart in July, because their daylight saving seasons run in opposite halves of the year. Phoenix and Denver are on the same time in winter and an hour apart in summer, because Denver observes daylight saving and Phoenix does not.
What happens if I pick a time that does not exist because of daylight saving time?
The tool shows an error and names the jump instead of guessing. When clocks go forward in spring, one hour of the day is skipped: in New York on Sunday 8 March 2026 the clocks jumped from 2:00 AM to 3:00 AM, so 2:30 AM never happened. In Cairo the spring jump happens at midnight, so 12:30 AM on Friday 24 April 2026 does not exist. In the Chatham Islands the jump runs from 2:45 AM to 3:45 AM. Pick a time outside the skipped hour and convert again.
Why does 1:30 AM happen twice on the day clocks go back?
When clocks go back in autumn, one hour repeats. In New York on Sunday 1 November 2026 the clocks fell back from 2:00 AM to 1:00 AM, so 1:30 AM happened twice, once in daylight time and once in standard time, an hour apart in real time. This tool uses the first occurrence, in daylight time, and shows a warning. If the exact occurrence matters, say which one you mean in words, for example 1:30 AM daylight time or 1:30 AM standard time.
What are the best hours for a meeting across time zones?
The best hours are the ones inside working hours everywhere at once, which the meeting planner checks for you against an 8:00 AM to 6:00 PM window. For New York and London, 9:00 AM in New York gives 2:00 PM in London, inside the window on both sides. Some pairs have almost no shared window: New York and Mumbai share only 30 minutes in summer, 8:00 to 8:30 AM in New York, and nothing at all in winter. Where no time suits everyone, share the early morning or late evening around the team instead of fixing one slot that always punishes the same people.
Does Vancouver still observe daylight saving time?
No. British Columbia sprang forward for the last time on 8 March 2026 and never fell back: on 1 November 2026 the clocks stayed where they were, and Vancouver now keeps UTC-7 all year. The province calls the year-round time Pacific Time, abbreviated PCT, while time zone databases label the same UTC-7 offset as MST. Vancouver is one hour ahead of Seattle and Los Angeles in winter and on the same time as them in summer. Alberta and Manitoba made the same move on the same day, keeping UTC-6 and UTC-5 all year.
How far apart can two places be in time?
The widest spread of local times on Earth is 26 hours, from UTC-12 to UTC+14. The UTC+14 zone was created when Kiribati moved the date line eastward in 1995. Among the places this tool covers, the widest gap is between the Chatham Islands at UTC+13:45 in summer and Honolulu at UTC-10, 23 hours and 45 minutes apart, so noon in the Chathams is 12:15 PM the day before in Honolulu. Every day between 10:00 and 10:59 UTC, three different calendar dates are in use at once around the world.
Sources
Every rule, date, and figure in this article comes from one of the sources below, each checked on 20 November 2026. The conversion rules were also cross-checked against the IANA time zone database, release 2026e, by comparing this tool against it on 36,960 monthly probes and 882 changeover cases, with no differences.
- NIST, Local Time FAQs — United States daylight saving dates and rules, United States zone offsets, and the places that do not observe daylight saving time. Accessed 20 November 2026.
- timeanddate, DST Around the World 2026 — 2026 daylight saving dates by country, used to check every rule family. Accessed 20 November 2026.
- EUR-Lex, Directive 2000/84/EC — European Union summer time: last Sunday in March to last Sunday in October, changing at 01:00 UTC. Accessed 20 November 2026.
- Wikipedia, Summer time in Europe — European summer time practice and the status of Directive 2000/84/EC. Accessed 20 November 2026.
- Business Victoria, Daylight saving — Australian daylight saving rule and dates. Accessed 20 November 2026.
- New Zealand Government, Daylight saving in NZ — New Zealand daylight saving rule and dates. Accessed 20 November 2026.
- IANA, Theory and pragmatics of the tz code and data — How the time zone database records civil time, and why zones change by law. Accessed 20 November 2026.
- IANA Time Zone Database — Release 2026e, used to cross-check every offset and changeover in this tool. Accessed 20 November 2026.
- timeanddate, DST Changes 2026 in Lord Howe Island — The 30 minute daylight saving shift, changing at 2:00 AM. Accessed 20 November 2026.
- timeanddate, DST Changes 2026 in Chatham Islands — Chatham Islands changes at 2:45 AM and 3:45 AM, offsets UTC+12:45 and UTC+13:45. Accessed 20 November 2026.
- Ahram Online, Egypt turns clocks back one hour at midnight Thursday — Egypt daylight saving restored in 2023 under Law No. 24 of 2023, last Friday in April to the end of the last Thursday in October. Accessed 20 November 2026.
- timeanddate, DST Changes 2023 in Cairo — Egypt transitions at midnight, 2023 table. Accessed 20 November 2026.
- Wikipedia, Daylight saving time in Mexico — Mexico abolished daylight saving time in most of the country with effect from 30 October 2022. Accessed 20 November 2026.
- Wikipedia, Daylight saving time in Brazil — Brazil abolished daylight saving time in 2019 by Decree No. 9,772. Accessed 20 November 2026.
- timeanddate, The International Date Line — The date line, the Samoa 2011 move, the Kiribati 1995 move, and the three dates in use at once. Accessed 20 November 2026.
- worldtimeconverter, How Many Time Zones Are There in the World? — The count of non-whole-hour offsets, recomputed here from the IANA database as 13 of 40 offsets. Accessed 20 November 2026.
- timeanddate, DST Changes 2026 in Metro Vancouver — British Columbia adopted permanent daylight time: last change 8 March 2026, no fall-back on 1 November 2026. Accessed 20 November 2026.
- Norton Rose Fulbright, BC transition to permanent daylight saving time — British Columbia Interpretation Amendment Act 2019 and Regulation 20/2026, Pacific Time (PCT) at UTC-7 year-round, and Alberta Time from 1 November 2026. Accessed 20 November 2026.