How to Convert Time Between Time Zones

UTC (Coordinated Universal Time) is the reference. Each zone is described as hours and minutes ahead of or behind UTC — for example UTC−5 or UTC+9.

Local time ≈ UTC + offset (offset can be negative). Going the other way: UTC ≈ local time − offset.

Worked example

Event at 16:00 UTC.

• UTC−5 (e.g. US Eastern standard): 16:00 − 5h = 11:00 local
• UTC+1 (e.g. many EU winter zones): 16:00 + 1h = 17:00 local
• UTC+5:30 (India): 16:00 + 5h30 = 21:30 local

Offsets are not always whole hours. India (UTC+5:30), Nepal (UTC+5:45), and Newfoundland (UTC−3:30) are common gotchas if your mental math only uses integers.

Use the free timezone converter instead of memorizing every offset — and remember DST can change the offset for the same city name between seasons.

“PST” and “EST” are abbreviations people overload. Pacific Time may be PST (UTC−8) or PDT (UTC−7). A message that says “3 PM PST” in July is often wrong if the sender meant “Pacific local time” during daylight saving.

• Better — America/Los_Angeles, Europe/Paris, Asia/Tokyo (IANA names)
• Acceptable — “3 PM Pacific (PDT)” with date included
• Risky — “3 PM PT” with no date, or “EST” year-round for New York

DST transitions

On spring-forward days, some local times do not exist (the clock skips an hour). On fall-back days, some local times occur twice. Scheduling “2:30 AM local” on those dates is fragile. For global launches, many teams publish the instant in UTC and let each region convert.

If you also store the event as a Unix stamp, convert with an epoch converter so engineers and humans share one source of truth.

Zone conversion does not care whether you display AM/PM or 00–23 — but humans mis-enter times constantly.

• 12-hour — 12:00 AM is midnight; 12:00 PM is noon; 11:00 PM = 23:00
• 24-hour — 00:00 midnight start; 12:00 noon; 18:00 = 6 PM

Classic mix-ups

• Reading 12 AM as noon (it is midnight)
• Treating 16:00 as 6 PM instead of 4 PM
• Dropping AM/PM in chat so “9:00” might be breakfast or dinner

When you convert, pick one display mode and stick to it for the whole message. Many converters let you toggle 12/24-hour output so you can paste the format your audience expects. If you need durations (meeting length, time until start) rather than zone labels, see the time calculator guide.

Start from one reference instant, then map every participant’s local clock. Do not chain “New York → London → Tokyo” with successive mental adds if you can avoid it — errors stack.

1. Pick the proposed local time for the host (or pick a UTC time).
2. Convert that instant into each attendee’s zone.
3. Check for early morning, late night, and weekend boundaries.
4. Offer 2–3 candidate slots if the first lands outside 09:00–17:00 for someone.
5. Send a calendar invite with timezone-aware start time (not only a Slack note).

Example

Host proposes 10:00 America/New_York on a winter day (UTC−5).

• UTC = 15:00
• London (UTC+0 winter) = 15:00
• Berlin (UTC+1 winter) = 16:00
• India (UTC+5:30) = 20:30
• Tokyo (UTC+9) = 00:00 next calendar day

Tokyo sees midnight — usually a bad slot. Shift the host to 08:00 Eastern and recalculate, or use an async update instead of a live call.

The International Date Line and large east/west spreads mean “same meeting” can sit on two dates. Always include the date with the time when you convert.

Patterns to watch

• US evening → already next morning in East Asia / Australia
• US early morning → still previous evening in Hawaii or Samoa-style offsets
• Friday 17:00 in California can be Saturday in Sydney

If someone says “let’s talk tomorrow,” clarify whose tomorrow. For date arithmetic (add days, difference between two calendar dates) after you settle the zone question, use a date calculator.

World-clock grids help you scan many cities at once: pick the row where most people land in daytime green-zone hours, not just where the host is comfortable.

Select source zone and time, choose target zones, and read the converted clocks — including whether the date moved.

1. Open the free timezone converter.
2. Set or detect your local timezone as the source if you are converting “my 3 PM.”
3. Enter the hour and minute; pick 12-hour or 24-hour display as needed.
4. Select the destination zone(s) for colleagues or travel destinations.
5. Check for a day change (+1 / −1 date) on the result.
6. Swap source and target when you are given their local time and need yours.
7. Copy the pair of times into the invite or chat with both zone labels.
8. For engineering logs, also convert the same instant via timestamp tools if you only have epoch numbers.

Travel day tip

Convert flight arrival local time into your home zone only if you care about body-clock overlap with family; for airport logistics, trust the destination local clock on the ticket.

These errors show up in support tickets and missed standups more than any other “simple” time issue.

• Using winter offsets in summer (or the reverse) for DST regions
• Omitting the date on cross-Pacific calls
• Assuming everyone knows what “EST” means in July
• Double-applying an offset (convert to UTC, then subtract again)
• Editing only the clock face in a calendar without checking the event’s timezone field

Related reading: time calculator, date calculator, epoch converter, and timestamp converter.

This guide is educational scheduling math. Authoritative zone rules change over time; rely on a maintained TZ database in software for production systems.