Skip to content

Time zones and daylight saving traps

Why a fixed time zone offset breaks twice a year, what happens to times that are skipped or repeated, and how to schedule a meeting across zones safely.

· 4 min read

Social card of the Time Zone Converter tool on this site

To convert a time between zones safely, store the IANA zone name and the date, then work out the offset for that exact date. A fixed offset such as "New York is UTC-5" is wrong for most of the year.

I built a Time Zone Converter on this site, and the dates below come from the zone data in my browser for 2026. Three cases cause most of the bugs: the offset between two cities changes, some local times never happen, and some happen twice.

The gap between two cities is not constant#

The US and Europe change their clocks on different dates. In 2026 New York moved forward on 8 March and London on 29 March. For those three weeks a 09:00 call in New York lands an hour earlier in London:

DateNew YorkLondonDifference
2 March 202609:0014:005 hours
16 March 202609:0013:004 hours
30 March 202609:0014:005 hours

The same thing happens in autumn: London went back on 25 October and New York goes back on 1 November. If you use a 5 hour rule, every recurring meeting is an hour off for that week.

The southern hemisphere makes it worse, because its clocks move the other way. Sydney is 11 hours ahead of London in January and 9 hours ahead in June, with 10 hours in the short periods between the changes.

Some local times do not exist#

When clocks go forward, an hour is skipped. On 8 March 2026 New York went from 01:59 straight to 03:00, so 02:30 never happened. A form will still let someone type it, and your code has to decide what it means.

My converter reads it with the offset from before the jump, so 02:30 becomes 03:30, and it shows a note saying so. A silent answer here is the bug, since the person may have meant something else.

Some local times happen twice#

When clocks go back, an hour repeats. On 1 November 2026, 01:30 in New York happens at UTC-4 and again one hour later at UTC-5. The wall-clock time alone cannot tell you which. My code tries each offset in force around that time and keeps those that read back as the time requested:

const before = offsetMinutes(new Date(wanted - 86_400_000), zone);
const after = offsetMinutes(new Date(wanted + 86_400_000), zone);
const hits = [...new Set([before, after])]
  .map((off) => new Date(wanted - off * 60_000))
  .filter((t) => wallOf(t, zone) === wanted)
  .sort((a, b) => a.getTime() - b.getTime());

Two hits mean the time repeats, one is a normal time, and none means it falls in the gap. For a repeat I use the earlier instant and say so on the page.

These are the same choices as the default compatible mode in JavaScript's Temporal.ZonedDateTime, which also offers earlier, later and reject. For a booking system, I would use reject and ask the person to choose.

Offsets are not always whole hours#

Do not store offsets as whole hours. Kolkata is UTC+5:30 and Kathmandu is UTC+5:45. Lord Howe Island, off Australia, changes its clocks by only 30 minutes, between UTC+10:30 and UTC+11. That is why the converter reports clock changes in minutes.

What to store#

  • Past events: a UTC timestamp. The instant is settled, so the offset no longer matters. The Unix Timestamp Converter reads these in any zone.
  • Future events people attend: the local time and the IANA zone name, such as Europe/Kyiv, and work out the instant when you need it. Governments change their clock rules, and the IANA time zone database gets updated when they do. A UTC timestamp saved today would keep the old answer.
  • Recurring events: the same, per occurrence. A weekly 09:00 meeting in New York sits at a different UTC time in summer and winter.

Abbreviations are no substitute for the zone name. IST can mean India, Ireland or Israel, and EST is often written in July when New York is on EDT.

Finding a meeting time#

For a meeting, work out the overlap for the actual date. With a 09:00 to 17:00 day, New York and London share 3 hours for most of the year and 4 during the mismatch weeks.

The converter draws an hour strip for each zone and marks the hours that are working time in all of them, with up to eight zones. It also flags a clock change on that day and gives you a share link, so the other person sees the same date and zones. One limit: the strip always has 24 slots from midnight in the base zone, so on a 23 or 25 hour day its last slot does not line up with midnight. The clock-change note tells you when that applies.

Everything runs in the browser using the zone rules in Intl, which fits a site with no server: the static export limits rule out anything else here. It also means the results depend on how recent the visitor's browser data is.