How to Convert Between Time Zones

The Reliable Method: Always Go Through UTC

Coordinated Universal Time, or UTC, is the global reference that every time zone is defined against. Instead of trying to jump directly from one local time to another, you convert the source time to UTC first, then convert UTC to the destination time. This two-step path removes ambiguity because UTC never observes daylight saving time and never changes. Think of it as a neutral hub that every clock on Earth connects to.

Each zone is described by its offset from UTC, written as a plus or minus number of hours. New York in winter is UTC-5, while India is UTC+5:30 year round. To convert a local time to UTC you subtract a positive offset or add a negative one, and to go from UTC back to a local time you do the reverse. Writing the offset down explicitly, rather than holding it in your head, is the single most effective way to avoid mistakes.

A common misconception is that a city has one fixed offset. In reality many places shift their offset twice a year for daylight saving, so the same city can be UTC-5 in January and UTC-4 in July. This is exactly why anchoring to UTC matters: UTC itself does not move, so it gives you a stable starting point no matter the season.

A Worked Step-by-Step Example

Suppose a colleague in Los Angeles proposes a call at 4:00 PM on a day in July, and you need to know the time in London. First, identify the source offset. In July, Los Angeles observes Pacific Daylight Time, which is UTC-7. Converting 4:00 PM (16:00) to UTC means adding 7 hours, giving 23:00 UTC.

Next, apply the destination offset. London in July is on British Summer Time, which is UTC+1. Adding 1 hour to 23:00 UTC gives 00:00, which is midnight. Because the addition pushed the clock past 24:00, the result lands on the following calendar day, so the call is at midnight at the start of the next day in London.

Notice how the two-step path made the date rollover obvious. If you had tried to compute the eight-hour difference in one mental leap, it would be easy to land on the right time but the wrong date. Always carry the date alongside the time through every step, and check whether your final figure crossed midnight in either direction.

Why Mental Math Often Fails

The biggest source of error is daylight saving time. Not every country observes it, those that do switch on different dates, and the Southern Hemisphere shifts in the opposite direction from the Northern Hemisphere. This means the difference between two cities can be, say, eight hours for most of the year but seven or nine hours for a few weeks during the transition windows. A fixed difference you memorized last month may simply be wrong today.

Half-hour and even quarter-hour offsets break the assumption that all conversions involve whole hours. India is UTC+5:30, Iran has used UTC+3:30, and parts of Australia sit at UTC+9:30. Nepal famously uses UTC+5:45. If you forget these fractional offsets, every calculation involving those regions will be off by a stubborn thirty or forty-five minutes.

Finally, date rollovers across midnight trip people up constantly. When the time difference is large, the destination can easily be on the previous or next calendar day. A meeting that feels like 'Tuesday afternoon' to one person can genuinely be 'Wednesday morning' to another. Treating the date as part of the answer, not an afterthought, prevents people from showing up a full day off.

Watch the AM/PM and Next-Day Pitfalls

The twelve-hour clock is a frequent culprit. It is easy to convert 9:00 PM as if it were 9:00 in the morning, which throws the result off by twelve hours. Converting to 24-hour time before you start the math removes this risk entirely: 9:00 PM becomes 21:00, and there is no longer anything to confuse. Switch back to AM/PM only at the very end if your audience prefers it.

Midnight and noon deserve special caution. 12:00 AM means midnight, the very start of the day, while 12:00 PM means noon. Many people instinctively read '12 AM' as midday, which produces a twelve-hour error that also drags the date with it. When in doubt, write 00:00 for midnight and 12:00 for noon so there is no room for interpretation.

After any conversion, sanity-check the date. If you added hours and the total passed 24:00, advance the date by one day and subtract 24. If you subtracted hours and the total dropped below 00:00, move the date back one day and add 24. This small bookkeeping habit catches the majority of next-day and previous-day mistakes.

Tips for Scheduling International Meetings

When you invite people, state the time zone explicitly and ideally include the UTC equivalent. Saying '3:00 PM Eastern (19:00 UTC)' leaves nothing to guesswork and survives forwarding across teams in different regions. Avoid vague labels like 'EST' during summer, since the zone may actually be on daylight time and the abbreviation will mislead.

Look for overlap windows rather than a single magic hour. If one team is in San Francisco and another is in Berlin, the comfortable shared working hours are narrow, so identifying that band in advance saves a lot of back-and-forth. A meeting planner that shows several zones side by side makes these overlaps visible at a glance and helps you find a slot that is not the middle of the night for anyone.

Be mindful of the transition weeks when clocks change. The gap between two regions can shift for a short period because they spring forward or fall back on different dates. Scheduling recurring meetings during those weeks is risky, so it helps to re-confirm the local time around late March, early November, and the corresponding Southern Hemisphere dates.

When to Use a Tool Versus Doing It by Hand

Doing conversions by hand is a useful skill for quick, low-stakes estimates and for understanding what is actually happening. If you only need a rough sense of whether a city is awake, the UTC method in your head is perfectly adequate. The mental exercise also builds intuition that makes you better at catching errors in automated results.

For anything important, a dedicated converter is faster and far less error prone. A good timezone converter applies the correct daylight saving rules automatically, handles fractional offsets, and shows the date alongside the time so rollovers are never a surprise. This matters most for one-off conversions involving unfamiliar regions whose offset and DST behavior you do not have memorized.

For coordinating across several locations at once, reach for a meeting planner instead of converting each pair by hand. Seeing every participant's local time in one view eliminates the compounding errors that creep in when you chain conversions manually. As a rule of thumb: estimate by hand, but confirm with a tool whenever a real commitment or another person's calendar is on the line.