How to Convert Time Zones Without Getting It Wrong: A Step-by-Step Guide With Examples
By Vclock · · 8 min read
Converting a time from one city to another sounds easy until a meeting lands an hour early or a friend calls you at 3:00 AM. Most mistakes come from three things: abbreviations that mean more than one thing, daylight saving time, and forgetting that the date can change too. The good news is that there is a simple method that avoids all three, and once you have used it a few times, it takes about ten seconds.
This guide walks through the method step by step, with worked examples for the most common pairs of places: New York and London, Los Angeles and Tokyo, New York and India, and Sydney and London. It also covers the traps to watch for and how to write invitations that nobody can misread. If you would rather not do the maths at all, our time zone converter does it for any date.
Step 1: name the city, not the abbreviation
Abbreviations are ambiguous. IST can mean India Standard Time, Irish Standard Time or Israel Standard Time. CST can mean Central Standard Time in the US, China Standard Time or Cuba Standard Time. BST can mean British Summer Time or Bangladesh Standard Time. Even EST is often used by people who really mean Eastern Time, which is EDT in summer. Saying New York time, London time or Kolkata time removes the doubt, and so does giving the UTC offset.
Step 2: find the UTC offset for that date
Every time zone is a number of hours, sometimes with 30 or 45 minutes, ahead of or behind UTC, the world time standard. Places east of the zero line are ahead and are written with a plus sign, and places to the west are behind and are written with a minus sign. In January New York is UTC-5 and London is UTC+0. In July, New York is UTC-4 and London is UTC+1. The offset depends on the date, so always check it for the day of the event, not for today.
Step 3: subtract the offsets to get the gap
The gap between two places is the difference between their offsets. New York in July is UTC-4 and London in July is UTC+1. The difference is 1 minus minus 4, which is 5 hours, and London is ahead.
Step 4: add or subtract the gap, then check the date
If the place you are converting to is ahead, add the gap. If it is behind, subtract it. Then check whether you have gone past midnight in either direction. If you have, the date has changed.
Worked examples
Here are four conversions that cover most of the cases you will meet.
- New York to London, in July: the gap is 5 hours. 9:00 AM in New York is 2:00 PM in London on the same day.
- Los Angeles to Tokyo: Tokyo is UTC+9 all year, and Los Angeles is UTC-8 in winter and UTC-7 in summer, so the gap is 17 hours in winter and 16 in summer. At 6:00 PM in Los Angeles in winter, it is 11:00 AM the next day in Tokyo. In summer the same moment is 10:00 AM the next day.
- New York to India, in July: New York is UTC-4 and India is UTC+5:30 all year, so the gap is 9 hours 30 minutes. 9:00 AM in New York is 6:30 PM in India. In winter the gap is 10 hours 30 minutes.
- Sydney to London, in July: Sydney is in winter and is on UTC+10, while London is in summer on UTC+1, so the gap is 9 hours. 8:00 AM in Sydney is 11:00 PM the previous day in London.
The last example shows a trap. The southern hemisphere changes its clocks in the opposite season to the northern one, so the gap between Sydney and London changes by two hours over the year, from 9 hours in July to 11 hours in January.
Daylight saving time traps
Daylight saving time is the biggest source of mistakes, because countries do not change on the same dates. The United States and Canada change on the second Sunday in March and the first Sunday in November. The United Kingdom and the European Union change on the last Sunday in March and the last Sunday in October. As a result, for about three weeks in spring and one week in autumn, the gap between New York and London is 4 hours instead of the usual 5.
Other things to remember are that Arizona and Hawaii do not change their clocks, that India, Japan and China do not use daylight saving time at all, and that some places use half-hour or 45 minute offsets. India is UTC+5:30, Iran is UTC+3:30 and Nepal is UTC+5:45. If you are scheduling something that falls near a clock change, check the exact date. Our daylight saving time page lists the change dates for the US, UK, Europe, Australia and New Zealand, and our guide to daylight saving time explains why they differ.
When the date changes
Whenever you add or subtract and cross midnight, the date changes with it. Converting 9:00 PM in Los Angeles in winter to London, which is 8 hours ahead, gives 5:00 AM the next day. Many missed calls happen because someone forgot that the other person was already in tomorrow. When you write times for people far away, always include the weekday and the date.
Finding a time that works for everyone
When more than two places are involved, work out who has the hardest time and look for the overlap in working hours. Here is a classic example for a team in New York, London and India in summer. A call at 9:00 AM in New York is 2:00 PM in London and 6:30 PM in India. It is the start of the day for one person, the middle for another and the end of the day for the third, and that is often the best compromise available.
If there is no good overlap, rotate the inconvenient times so that the same people do not always stay up late, and consider sharing a recording or a written update instead of a live call. A meeting planner, like the one on our time zone converter, shows the hours in every place side by side and highlights the ones that fall inside normal working hours.
How to write an invitation nobody can misread
- Give the weekday, the date and the time: Thursday 16 July, 9:00 AM.
- Name the city and the zone: New York (EDT), London (BST), Kolkata (IST).
- Add the UTC time or the offset, for example 13:00 UTC.
- Use 24 hour time for international teams, so that 2:00 PM is never confused with 2:00 AM.
- Use a calendar invitation, which adjusts to each person time zone automatically.
- For software, store and exchange times in a standard format such as 2026-07-16T09:00-04:00.
Developers know this problem well. The usual rule is to store times in UTC and convert only when showing them to a person. A Unix timestamp is a simple example, because it has no time zone at all.
Mental shortcuts
- Within North America, remember the sequence Pacific, Mountain, Central, Eastern: each step east is one hour ahead. For example, 9:00 AM EST is 6:00 AM PST, and our [EST to PST page](/timezone-converter/est-to-pst/) shows the table.
- London and Western Europe are usually 5 to 6 hours ahead of the US East Coast, and 8 to 9 hours ahead of the West Coast.
- India is 9.5 to 10.5 hours ahead of the US East Coast, and 12.5 to 13.5 hours ahead of the West Coast.
- Think of 24 as a wheel. If the result goes above 24 hours, subtract 24 and add a day. If it goes below zero, add 24 and subtract a day.
Common mistakes
- Using an abbreviation instead of a city.
- Using today offset for a date months away, after a clock change.
- Forgetting that the southern hemisphere changes in the other direction.
- Forgetting the date change near midnight.
- Assuming every time zone is a whole number of hours.
- Setting a recurring meeting in one time zone without checking what happens when clocks change.
Tools that make it easy
You do not need to do the maths in your head. The time zone converter turns one date and time into up to eight other places at once. The world clock shows the live time in every country. For the pairs people ask about most, there are ready-made pages such as EST to PST. And when you have your answer, you can set the online alarm clock for the converted time so that you do not miss the call.
The bottom line
Converting time zones comes down to four steps: name the city, find the offset for the date, subtract to get the gap, and add or subtract it while watching the date. Be careful around the clock change dates, remember that the southern hemisphere does the opposite, and write invitations with the city, the weekday and the UTC time. Do that, and the 3:00 AM phone calls become a thing of the past.
Frequently asked questions
How do I convert time zones manually?+
Find the UTC offset of each place for the date, subtract them to get the gap, then add the gap if the other place is ahead or subtract it if it is behind. Check whether the result has crossed midnight, because then the date changes too.
How do I convert EST to PST?+
Pacific Time is 3 hours behind Eastern Time, so subtract 3 hours. 9:00 AM Eastern is 6:00 AM Pacific. The gap stays at 3 hours all year, because both places change their clocks on the same dates.
What is the time difference between New York and London?+
London is 5 hours ahead of New York for most of the year. For about three weeks in spring and one week in autumn it is 4 hours, because the US and the UK change their clocks on different dates.
Does daylight saving time affect time zone conversion?+
Yes. Offsets change when clocks go forward or back, and countries change on different dates. Always use the offset for the date of the event, not for today.
How do I find a meeting time across several countries?+
Convert the proposed time to every place and look for the hours that fall inside normal working time for most people. A meeting planner shows this side by side. If there is no good overlap, rotate the inconvenient times fairly.
What is the easiest way to avoid mistakes?+
Name the city instead of the abbreviation, give the weekday and the date, add the UTC time, and use a converter or a calendar invitation that adjusts to each time zone automatically.