Reading a time zone result when clocks change

A time-zone result is always tied to a date. The Time Zone Converter treats the clock you type as wall time in the first IANA zone, then writes that same instant in the second zone. The hour gap is the difference between those two offsets on that day, not a slogan such as “the East Coast is always plus three.”

In the United States, New York and Los Angeles usually stay three hours apart after both clocks spring forward. People see EST become EDT and PST become PDT, and they assume the meeting jumped. The labels moved. The gap often did not. Check January 15 and July 15 in the converter if you want a pair of dates where that pattern is easy to see.

The mix-up is different when only one place changes. Phoenix stays on mountain standard time. A New York morning that is two hours ahead in January is three hours ahead in July. If you reuse last winter’s offset in June, the call starts an hour late for someone.

Read the short zone name on the result (EST, EDT, MST) as a label for that date, not as a permanent rule. If your browser cannot read IANA names, the converter says so. It will not invent UTC−5 for every New York date.

When you send an invitation, write the local clock in each place and keep the date next to it. “Noon in New York on July 15” is clearer than “noon Eastern,” because Eastern is two different offsets in one year.