Scheduling a call across time zones goes wrong in two very specific ways: assuming every time zone offset is a whole number of hours, and forgetting that daylight saving time doesn't change on the same date everywhere — or at all, in some places.

UTC: The Common Reference Point

Every time zone is defined as an offset from Coordinated Universal Time (UTC) — "UTC+5" means 5 hours ahead of UTC, "UTC−8" means 8 hours behind. Converting between any two time zones is really just converting each to UTC first, then to the target zone.

Why Some Offsets Aren't Whole Hours

Not every zone is a clean hour offset: India Standard Time is UTC+5:30, and Newfoundland is UTC−3:30 — half-hour (and even 45-minute, in a couple of places) offsets exist and are easy to miscalculate if you assume every zone lines up on the hour.

Daylight Saving Time Complicates Everything

Many regions shift their clocks forward or back for part of the year, but not on the same dates as each other, and some regions don't observe daylight saving time at all. This means the effective offset between two cities can change twice a year, and the change dates don't line up globally — a meeting time that works in March might be an hour off by July.

Why "Same Local Time" Isn't the Same Moment

3:00 PM in New York and 3:00 PM in Tokyo are not the same moment — they're the same clock reading in two different frames of reference. Scheduling across time zones always requires picking one shared reference point (often UTC) and converting everyone's local time from there.

Step-by-Step: Convert a Time

  1. Enter the time and date in the source time zone
  2. Select the source and target time zones
  3. Get the converted time, automatically accounting for any daylight saving offset

Try It Yourself

Use our free Time Zone Converter — accounts for daylight saving automatically

Open Time Zone Converter →