Every time zone is defined as an offset from UTC (Coordinated Universal Time), a single global reference time that doesn't change with the seasons. Converting a time from one zone to another is, at its core, just adding or subtracting the difference between two offsets. The complication is that a region's offset from UTC isn't always constant throughout the year, which is where most manual time zone conversions go wrong.
Fixed offsets vs. daylight saving offsets
Some regions use a single, unchanging UTC offset all year (India's UTC+5:30 is a well-known example, and it never shifts). Others observe daylight saving time (DST), moving their clocks forward by an hour in spring and back in autumn, which means their effective UTC offset is different in summer than in winter. New York, for instance, is UTC−5:00 in winter (Eastern Standard Time) but UTC−4:00 in summer (Eastern Daylight Time), a full hour of difference depending on the time of year you're converting for.
This is why a conversion that was correct in January can be wrong by an hour in July, if either the source or destination region observes DST and you don't account for which offset currently applies. It's also why some cross-region gaps that are normally, say, 9.5 hours can temporarily become 8.5 or 10.5 hours during the weeks when one region has already switched its clocks and the other hasn't yet.
Why the switch dates aren't the same everywhere
Countries that observe daylight saving time don't all switch on the same calendar date, and the Northern and Southern Hemispheres switch in opposite directions (one is moving clocks forward for spring while the other is moving them back for autumn, at the same point on the calendar). This means the true offset gap between two specific cities isn't a single constant you can memorize, it can take up to four different values across a year depending on each region's individual DST schedule. Rather than tracking this manually, the Timezone Calculator applies the correct offset for the actual date you're converting, not just a generic yearly average.
Where time zone math gets used in practice
Beyond simple conversions, timezone offsets underpin scheduling across distributed teams, flight arrival-time calculations, and international deadlines. If you're specifically trying to find a workable meeting slot across several regions rather than converting one single time, our guide on planning a meeting across multiple time zones walks through that related but slightly different problem.