Time zone conversion is one of those tasks that seems easy until you get it wrong — and getting it wrong means someone misses a meeting, a deadline, or a call. The math isn't complicated, but the edge cases are numerous: daylight saving time transitions, half-hour offsets, countries that don't observe DST, and the international date line.

Here's a systematic approach that works for any combination of time zones.

The Core Conversion: UTC as the Common Reference

The reliable method for converting between any two time zones is to go through UTC (Coordinated Universal Time) as a common reference. Every time zone in the world is expressed as an offset from UTC — UTC+2, UTC-5, UTC+5:30, and so on.

Step 1: Convert the source time to UTC by subtracting the source zone's offset. Step 2: Convert UTC to the target time by adding the target zone's offset.

Example: It's 3:00 PM in New York (UTC-5 in winter). What time is it in Berlin (UTC+1 in winter)?

1. New York → UTC: 3:00 PM − (−5) = 3:00 PM + 5 = 8:00 PM UTC 2. UTC → Berlin: 8:00 PM UTC + 1 = 9:00 PM Berlin

Or directly: 3:00 PM + 6 hours (the difference between UTC-5 and UTC+1) = 9:00 PM.

The time converter handles the arithmetic for hours and minutes. For the time zone offset addition, the key is knowing the current UTC offsets for both locations — which is where daylight saving time complicates things.

Daylight Saving Time: The Source of Most Errors

The majority of time zone conversion errors come from not accounting for whether daylight saving time (DST) is currently in effect. DST shifts clocks forward by one hour in spring and back one hour in autumn — but not every country does this, and the dates vary by country.

Countries that observe DST:

• United States and Canada: clocks spring forward on the second Sunday of March, fall back the first Sunday of November
• Most of Europe: clocks spring forward the last Sunday of March, fall back the last Sunday of October
• Australia: clocks spring forward the first Sunday of October (Southern Hemisphere — their spring is Northern Hemisphere autumn)

Countries that do NOT observe DST:

• Most of Asia (China, Japan, India, Southeast Asia)
• Most of Africa
• Most of the Middle East (some exceptions, e.g., Israel, Jordan observe DST)
• Iceland, Russia (Russia abolished DST in 2014)
• Arizona in the US (with the exception of the Navajo Nation)

This means the offset between, say, London and Tokyo changes twice a year — when the UK adjusts for DST but Japan doesn't. The difference is 8 hours in winter (UTC+0 vs UTC+9) and 9 hours in summer (UTC+1 vs UTC+9).

Always check the current UTC offset for both locations, not the standard offset, before converting.

Common UTC Offsets Reference

These are standard (non-DST) offsets. Add 1 hour during DST where applicable.

Scheduling Across the Date Line

The International Date Line runs roughly along the 180° meridian in the Pacific. When you cross it westward, you gain a day; eastward, you lose a day. This causes scheduling confusion when, for example, scheduling a call between New York and Tokyo.

New York is UTC-5 (winter). Tokyo is UTC+9. The difference is 14 hours — but because Tokyo is ahead, when it's Monday 9am in New York, it's Tuesday 11pm in Tokyo.

The day change catches people off guard. "Let's meet Monday afternoon your time" means Tuesday morning for the Tokyo participant. Always confirm the date in both locations, not just the time.

Half-Hour and 45-Minute Offsets

Most time zones are offset by whole hours, but several are not:

• India (IST): UTC+5:30 — half hour offset
• Nepal: UTC+5:45 — 45-minute offset, unique in the world
• Iran (IRST): UTC+3:30 standard, UTC+4:30 during DST
• Afghanistan: UTC+4:30
• Australia's Northern Territory: UTC+9:30
• Lord Howe Island (Australia): UTC+10:30, with a 30-minute DST shift to UTC+11

When scheduling with someone in India or Nepal, make sure your meeting time works at the half-hour boundary. A meeting at "10:00 UTC" means 3:30 PM in India, not 3:00 PM or 4:00 PM.

Practical Scheduling Tips for International Teams

Always specify time zones when sharing a meeting time. "3pm" means nothing internationally. "3pm New York time (UTC-4)" or "15:00 EST" leaves no room for error. Better still, share the UTC equivalent: "3pm New York / 20:00 UTC."

Use the UTC time as your anchor. When scheduling a recurring meeting across three or more time zones, pick a UTC time and work outward from it. "Weekly sync at 14:00 UTC" is unambiguous regardless of what DST is doing in each participant's country.

Check UTC offsets the week of DST transitions. The two or three weeks per year when some regions have shifted their clocks and others haven't create temporary offset changes. A recurring meeting that was New York (UTC-5) to London (UTC+0) = 5-hour difference becomes UTC-4 to UTC+1 = 5-hour difference when both adjust together, but 6-hour difference during the brief period when only one has adjusted.

For important calls, confirm 24 hours before. A quick "confirming our call tomorrow at [time] your time / [time] my time" message catches errors before they cost a missed connection.

The time converter is useful for converting between hours and fractions — for instance, working out that a 5:30 offset means a meeting at 10:00 UTC falls at 3:30 PM, not 3:00 PM or 4:00 PM.

Building Mental Anchors for Common Routes

If you regularly work between specific cities, it's worth memorizing the current offset and when it changes. A few useful reference points:

• New York ↔ London: 5 hours in winter, 4 hours in summer (one week out of sync during DST transitions)
• New York ↔ Paris/Berlin: 6 hours in winter, 5 in summer
• London ↔ Mumbai: 5.5 hours, year-round (India doesn't observe DST)
• New York ↔ Tokyo: 14 hours in winter, 13 in summer
• Los Angeles ↔ London: 8 hours in winter, 7 in summer
• Sydney ↔ London: 11 hours in winter (UK), but changes when Australia's DST applies

Knowing these makes quick mental scheduling possible without having to look up offsets every time. For anything outside these common pairs, check the current UTC offset directly.