EST Time Converter

The model, stated exactly

The US Eastern zone is America/New_York in the IANA time-zone database. It observes Eastern Standard Time (EST, UTC−5) from the end of daylight saving until daylight saving resumes, and Eastern Daylight Time (EDT, UTC−4) the rest of the year. For the current cycle: EST runs from November 1, 2026 to March 14, 2027, and EDT runs from March 14, 2027 onward (in the previous cycle, EDT ran from March 8, 2026 to November 1, 2026). The converter never assumes the offset from the month: it tries each candidate offset (UTC−4, then UTC−5) for the entered wall time and keeps the one whose New York rendering reproduces the entered date and time exactly, reading the abbreviation from the database itself. Every output zone is then rendered from that UTC instant with Intl.DateTimeFormat. That is why the converter stays correct across the transitions, including the two awkward hours: 1 a.m. on a fall-back day occurs twice (the converter takes the first, daylight occurrence), and 2:30 a.m. on a spring-forward day does not exist at all (the converter reports it as an error instead of silently shifting it).

The worked example, line by line

Setup: Eastern date January 15, 2027, Eastern time 12:00.

Line 1 — the abbreviation. January is in the standard-time half, so the zone is EST (UTC−5).

Line 2 — the UTC instant. 12:00 plus 5 hours = 17:00 UTC on January 15, 2027.

Line 3 — New York. The entered time itself: 12:00 EST on January 15.

Line 4 — Chicago. CST (UTC−6): 17:00 UTC = 11:00 CST on January 15.

Line 5 — Denver. MST (UTC−7): 17:00 UTC = 10:00 MST on January 15.

Line 6 — Los Angeles. PST (UTC−8): 17:00 UTC = 09:00 PST on January 15.

Line 7 — Anchorage. AKST (UTC−9): 17:00 UTC = 08:00 AKST on January 15.

Line 8 — Honolulu. HST (UTC−10, no DST): 17:00 UTC = 07:00 HST on January 15.

Try these

Summer: noon on October 24, 2026. This is EDT (UTC−4), not EST, so the UTC instant is 16:00 UTC on October 24: 12:00 EDT in New York, 11:00 CDT in Chicago, 10:00 MDT in Denver, 09:00 PDT in Los Angeles, 08:00 AKDT in Anchorage, and 06:00 HST in Honolulu. Saying "noon EST" for this date would put the conversion an hour out — the single most common Eastern time error, stated plainly so it can be avoided.

The boundary days. Noon on October 31, 2026 is still EDT (16:00 UTC), and noon on November 1, 2026 is already EST (17:00 UTC), because daylight saving ended at 2 a.m. that morning; noon on March 13, 2027 is still EST, and noon on March 14, 2027 is EDT again. EST season dates for 2026-27 are therefore November 1, 2026 through March 14, 2027.

Disambiguation: Australia also uses EST

The letters EST are reused in Australia, and they mean a different clock there. Australian Eastern Standard Time (AEST) is UTC+10 for most of the year, and Australian Eastern Daylight Time (AEDT) is UTC+11 in the southern summer — and, confusingly, Australians often shorten those to EST and EDT in casual writing. So a message saying "noon EST" from Sydney means 02:00 UTC, while "noon EST" from New York means 17:00 UTC: a 15-hour gap hidden behind the same three letters. The southern seasons are also reversed — Australian daylight time runs roughly October to April, while US daylight time runs March to November — so the two ESTs are almost never in step. When a message says only "EST" with no place attached, ask which continent before converting: the same letters can mean clocks 15 hours apart. Other EST uses exist too — EST is also a common abbreviation in other contexts, from "established" to various organisations — but for time, the US-vs-Australia collision is the one that causes missed meetings.

Output · formula · meaning

Who uses this

• The scheduler writing "noon EST" in January: enters January 15, 2027 and confirms noon EST is 17:00 UTC, 11 a.m. in Chicago, and 9 a.m. in Los Angeles — and that the abbreviation is actually correct for that date.
• The manager who wrote "EST" for a July meeting: enters the July date, sees the converter label it EDT, and fixes the invitation before anyone joins an hour late.
• The traveler landing in New York in January: enters January 15, 2027 and learns noon local is EST, 17:00 UTC — not the 16:00 UTC a summer EDT conversion would give.
• The remote worker across three US zones: enters one Eastern time and reads off every US zone at once, including whether Honolulu (which never shifts) has drifted an hour relative to the mainland since the last meeting.

Accuracy & limitations

The conversion is exact for the IANA time-zone database in your browser, which is the same database operating systems and airlines use. Two caveats deserve daylight. First, the converter assumes the time you enter is an Eastern wall-clock time in America/New_York — if a contact quotes you a time labeled only "EST" or "EDT" with no place, check the disambiguation section first, because Australia uses the same letters for UTC+10 / UTC+11 clocks. Second, US daylight-saving rules have changed before (the current March-to-November pattern dates from 2007) and could change again by law; the converter follows whatever rules your browser's database currently carries, which is correct for scheduling today but may differ for far-future dates if the law changes. The fall-back hour (1 a.m. occurring twice) is resolved to its first, daylight occurrence, and the spring-forward gap hour is reported as an error rather than silently shifted. Error policy: empty, malformed, or impossible dates (such as February 30) and nonexistent Eastern times are reported as errors rather than calculated, so no result ever shows a rolled-over date.