The one-hour mistake almost everyone makes
Someone writes “10 PM EST” in July. Strictly, EST does not exist in July — the eastern United States is on EDT then, an hour ahead at UTC−4. Read the message literally and you arrive an hour late. Read what they meant and you arrive on time. Nearly everyone means Eastern local time whatever the season, so this page follows local time by default and tells you plainly which abbreviation is really in force on the date you picked. If you genuinely need strict, never-shifting EST, it is in the list under fixed offsets, kept deliberately separate.
Why the gap between two cities is not a constant
London is five hours ahead of New York for most of the year, four hours ahead for about three weeks in March, and five again from late October. The two regions change their clocks on different Sundays, so any rule you memorise is wrong several weeks a year. Sydney is worse: it moves in the opposite direction, so the gap to Los Angeles swings across a four-hour range. The only reliable method is to resolve the offset for the specific calendar date, which is what happens here — not for today, for the date in the field.
Twice a year a clock time is a trick question
On the spring-forward Sunday, clocks jump from 2:00 to 3:00 and 2:30 AM simply never happens. On the autumn Sunday, 1:30 AM happens twice, an hour apart, and the two are different instants that convert to different times everywhere else. Most converters answer these silently and confidently, and one of the two answers is wrong. This one flags both cases and tells you which instant it chose, so you can go back and ask.
How the arithmetic is done
Every browser ships the IANA time zone database, the same dataset used by Linux, macOS and most servers, covering every zone rule change back to 1970 and scheduled changes going forward. The page asks the browser for the exact offset in force at the instant you specified, then reverses the calculation to find the single moment in absolute time your wall clock refers to, then re-expresses that moment in every other zone. Nothing is approximated, no table of offsets is hardcoded, and nothing is sent to a server — the entire conversion runs on your device. If your operating system is current, so is the zone data.
Writing a time that cannot be misread
The safest form names a city or a UTC offset alongside the abbreviation: “Thu 3 Sep, 10:00 PM New York (UTC−4)”. Better still, send a UTC time and let each calendar render it. Calendar applications handle the standard-to-daylight switch correctly when you pick a named zone such as Eastern Time rather than typing letters into the subject line; almost every scheduling error traces back to a time that was written as prose instead of stored as a zone.