EST vs EDT: Eastern Time's Two Abbreviations and When Each Applies

EST and EDT are the same time zone wearing two different labels. Eastern Standard Time (EST) is UTC−5 and runs from the first Sunday in November to the second Sunday in March. Eastern Daylight Time (EDT) is UTC−4 and runs from the second Sunday in March to the first Sunday in November. ETis the generic label meaning "whichever one is in effect right now." That is the entire answer. The rest of this article covers the exact switch dates and the federal law behind them, the seventeen states plus the District of Columbia that live under those letters, the places on Eastern Time that never switch at all, the three-letter collision with Australia that quietly corrupts calendars, and how software should store any of this. For a one-off conversion, the timezone converter does the offset math directly.

The rule in one sentence

Eastern Standard Time (EST) is UTC−5 and is in force from the first Sunday in November to the second Sunday in March. Eastern Daylight Time (EDT) is UTC−4 and is in force from the second Sunday in March to the first Sunday in November. ET is the shorthand a broadcaster, a newsroom, or a press release uses when it does not want to commit to either.

The IANA time zone database represents the region with the identifier America/New_York, which carries the full history of every transition the zone has ever made — including the 2007 change that lengthened daylight time by roughly a month, and the county-by-county mess Indiana ran until 2006. Operating systems and programming languages all read those rules from tzdata, which is why a recurring 9:00 a.m. ET standup created in Outlook on a laptop in Bengaluru still lands on the right hour for the person in Boston, in January and in July.

What the abbreviations actually mean

The three-letter framework is consistent across every North American zone. The first letter is the region (Eastern, Central, Mountain, Pacific, Atlantic, Alaska, Hawaii). The second letter is either Standard or Daylight. The third letter is always Time. Drop the middle letter and you get the generic form. So:

• EST— Eastern Standard Time, UTC−5. The "winter" clock setting in the Eastern Time Zone.
• EDT— Eastern Daylight Time, UTC−4. The "summer" clock setting in the Eastern Time Zone.
• ET— Eastern Time, generic. This is what network television, the NYSE, and most wire services use. "Markets open at 9:30 a.m. ET" is correct all year; "markets open at 9:30 a.m. EST" is correct for about four months of it.

The same pattern gives you CST/CDT/CT, MST/MDT/MT, and PST/PDT/PT. Immediately east of the zone, Atlantic Standard Time (AST) and Atlantic Daylight Time (ADT) sit one hour ahead, and Newfoundland runs the continent's only half-hour civil offsets, NST (UTC−3:30) and NDT (UTC−2:30).

The important asymmetry: EST is notthe default. In 2026, daylight time on the US East Coast runs from March 8 to November 1 — 238 days, thirty-four weeks, about 65% of the calendar. EDT is the setting the Eastern seaboard spends most of the year in, and EST is the exception that covers a little over four months. Writers who reach for "EST" as a generic stand-in for "New York time" are wrong roughly two days out of three.

When each one applies: the transition dates

The U.S. Department of Transportation has jurisdiction over the country's time zones and over daylight saving time, an authority it inherited from the Uniform Time Act of 1966. That act set the national framework: a state may opt out of daylight saving time entirely, but a state that observes it must start and stop on the same dates as everyone else. The current dates come from Section 110 of the Energy Policy Act of 2005, which took effect in 2007 and added roughly four weeks to the US daylight saving window. Under those rules:

• Spring forward: the second Sunday in March, at 2:00 a.m. local time, clocks jump from 2:00 to 3:00. EST ends; EDT begins.
• Fall back: the first Sunday in November, at 2:00 a.m. local time, clocks fall from 2:00 back to 1:00. EDT ends; EST begins.

In 2026 that puts the switches on Sunday, March 8 (EST ends, EDT begins) and Sunday, November 1 (EDT ends, EST begins). In 2027 they fall on Sunday, March 14 and Sunday, November 7. Both transitions happen at 2:00 a.m. local time in each zone, not simultaneously across the country.

That last detail produces two genuinely strange hours a year, and both of them break the assumption that Eastern is always exactly one hour ahead of Central. On the March Sunday, Eastern springs forward at 07:00 UTC while Central waits until 08:00 UTC; for those sixty minutes New York is on UTC−4 and Chicago is still on UTC−6, so the gap is two hours. On the November Sunday it inverts: Eastern falls back at 06:00 UTC and Central not until 07:00 UTC, so for an hour both cities read 1:30 a.m. and the gap is zero. Anything with a fixed inter-zone offset baked into it — a replication window, a shift-handover script, an EST to CST lookup table pasted into a report — is wrong for exactly those hours. Canada matches the US schedule: Ontario and Quebec spring forward and fall back on the same Sundays, so Toronto and Montreal never drift from New York.

Where Eastern Time actually applies

Eastern is the most populous time zone in the United States — close to half the country's population lives in it — which is why its abbreviations show up in so much software that never travels. Seventeen states lie entirely inside it: Connecticut, Delaware, Georgia, Maine, Maryland, Massachusetts, New Hampshire, New Jersey, New York, North Carolina, Ohio, Pennsylvania, Rhode Island, South Carolina, Vermont, Virginia, and West Virginia, plus the District of Columbia. Five more are split:

• Florida — Eastern except the western panhandle, which is Central.
• Michigan — Eastern except four western Upper Peninsula counties (Gogebic, Iron, Dickinson, and Menominee) that stay on Central with neighboring Wisconsin.
• Indiana — 80 of 92 counties are Eastern; twelve are Central, six of them in the northwest near Chicago and six in the southwest near Evansville.
• Kentucky and Tennessee — the eastern halves are Eastern, the western halves Central. The line runs roughly between Louisville and Nashville.

Outside the United States, Eastern Time covers Ontario (excluding its western regions), Quebec, and eastern Nunavut — Toronto, Ottawa, Montreal, Quebec City, and Iqaluit — all of which observe EST and EDT on the US schedule. In the Caribbean, the Bahamas and Haiti observe Eastern Time with daylight saving. Cuba is a special case worth knowing: Havana's clocks match Eastern exactly, but tzdata labels them CST and CDT, for Cuba Standard Time — a third meaning for an abbreviation that already means both Central Standard Time and China Standard Time.

The places on Eastern Time that never switch

Pacific Time has Arizona; Eastern Time has no domestic equivalent. Every part of the United States inside the Eastern Time Zone observes daylight saving time. The year-round exceptions all lie outside US borders, and they are the ones that trip up scheduling:

• Quintana Roo, Mexico.Cancún, Playa del Carmen, and Cozumel moved to UTC−5 in 2015 and dropped daylight saving time at the same time. In winter Cancún matches New York exactly; in summer it falls an hour behind, because New York moves and Cancún does not. The tz identifier is America/Cancun.
• Jamaica, the Cayman Islands, and Panama.All three sit on UTC−5 all year with no daylight saving: America/Jamaica, America/Cayman, America/Panama. A Kingston counterparty is on your clock in January and an hour behind you in July.
• Atikokan, Ontario. Geographically inside the Central Time Zone, but on Eastern Standard Time year-round, which amounts to keeping Central daylighttime permanently: the town sits on UTC−5 in July like the rest of Central Canada, and stays there in January when its neighbors fall back. tzdata gives it its own identifier, America/Atikokan.
• Southampton Island, Nunavut. Coral Harbour does the same thing on the other side of Hudson Bay, hence America/Coral_Harbour.

Historically, the United States did have an Eastern-zone holdout. Most of Indiana refused daylight saving time for decades, sitting on EST year-round while counties near Chicago, Louisville, Cincinnati, and Evansville each did something different. The Indiana General Assembly ended it in 2005, and statewide daylight saving time began on April 2, 2006, making Indiana the forty-eighth state to observe it. The legacy survives in tzdata, which still ships eight separate Indiana zones — America/Indiana/Indianapolis, America/Indiana/Vincennes, America/Indiana/Knox, and five more — plus two for Kentucky. If you are converting an Indiana timestamp from before 2006, "EST" on that record may mean something no modern conversion table will reproduce.

EST is not AEST: the Australian ambiguity

This is the failure mode that produces the worst errors, because the result is not an hour off — it is fifteen hours off. Australian Eastern Standard Time (AEST) is UTC+10, and Australian Eastern Daylight Time (AEDT) is UTC+11. North American EST is UTC−5. The two are fifteen hours apart, and nothing about the letters warns you.

The confusion is not user error alone. Until tzdb release 2014f in August 2014, the IANA database itself printed the abbreviation EST for Australia/Sydneyin standard time; the release notes for that version record the change to AEST and AEDT explicitly. Every log file, CSV export, and database column written by an older system in Australia may carry a bare "EST" that means UTC+10. Some legacy Windows and Java stacks still surface it.

Two more details make Australian Eastern Time harder than it looks. First, the seasons are inverted: Sydney is on AEDT during the northern winter, when New York is on EST, and on AEST during the northern summer, when New York is on EDT. That means the New York-to-Sydney gap is sixteen hours in January and fourteen hoursin July — a two-hour swing across the year for a meeting nobody ever rescheduled. Second, Australia's daylight saving is partial: New South Wales, Victoria, Tasmania, the ACT, and South Australia observe it; Queensland, Western Australia, and the Northern Territory do not. Brisbane sits on AEST all year, so for the southern summer Brisbane and Sydney are an hour apart despite sharing a coastline.

The practical rule: never accept a bare "EST" from an Australian counterparty, an Australian vendor's API, or an old export. Ask for the IANA identifier — Australia/Sydney versus America/New_York — or for a UTC instant.

Quick reference: Eastern Time across major hubs

The table below shows what 9:00 a.m. on a Tuesday in New York looks like elsewhere, in both the EST (winter) and EDT (summer) windows. The receiving city's own daylight saving status decides whether its column entries match, which is why some rows move and some do not.

Worked examples

Example 1 — EST to UTC.A board call at 9:00 a.m. on Tuesday, January 13 in New York. Eastern is on EST that morning, so the offset is UTC−5. Add five hours: the call is 14:00 UTC on Tuesday, January 13 — one unambiguous instant, safe to store. Run it in reverse with the UTC to EST conversion.

Example 2 — EDT to CEST.A customer demo at 11:00 a.m. on Wednesday, July 8 in Atlanta. Eastern is on EDT, UTC−4, so the instant is 15:00 UTC. Frankfurt is on CEST, UTC+2, so the demo lands at 17:00 — five in the afternoon, right at the edge of a German working day. Six hours forward, not the seven you would get if you had reached for EST out of habit.

Example 3 — the Australia trap. A 4:00 p.m. ET meeting in New York, set up in January to catch a Sydney partner first thing. In northern winter New York is EST and Sydney is AEDT, a sixteen-hour gap: 16:00 becomes 08:00 Wednesday in Sydney. Perfect. Leave that same recurring invite running until July and both ends have moved in opposite directions — New York is EDT, Sydney is AEST, the gap is fourteen hours, and the meeting is now 06:00 Wednesday in Sydney. Nobody changed anything, and the Australian side lost two hours of sleep.

Example 4 — the spring-forward gap. A nightly job scheduled at 2:30 a.m. Eastern will never run on the second Sunday in March, because 2:00 a.m. skips straight to 3:00 a.m. and 2:30 does not exist that day. On the first Sunday in November the opposite happens: 1:30 a.m. occurs twice, and a wall-clock trigger may fire twice. Schedule in UTC, or pick a time of day the transition cannot touch.

Example 5 — the EDT and AST overlap.In summer, New York on EDT and San Juan on Atlantic Standard Time are both UTC−4, so 10:00 in one is 10:00 in the other. In winter, New York drops back to EST while Puerto Rico stays put, and San Juan is suddenly an hour ahead. A team split across those two cities discovers this every November.

Common mistakes

• Writing "EST" in July.The most common error in this entire zone. The wall-clock hour is unaffected, but the UTC offset is not (UTC−4 versus UTC−5), and a parser that takes the abbreviation literally resolves "9:00 a.m. EST" on a July date to 14:00 UTC instead of 13:00 UTC. Write ET, or write the offset.
• Assuming EST always means New York.Jamaica, the Cayman Islands, Panama, and Quintana Roo are on EST every day of the year and never become EDT. "EST" alone does not tell you whether the sender ever changes clocks.
• Reading a bare EST from an Australian system. Fifteen hours in the wrong direction. Anything written by tooling older than tzdb 2014f is suspect.
• Hard-coding UTC−5 for "Eastern." Wrong for about 65% of every year. Use America/New_York and let the library resolve the offset.
• Assuming the inter-zone gap is constant. For one hour each March, New York is two hours ahead of Chicago rather than one, because the zones transition at 2:00 a.m. in their own local time. Check the CST to EST conversion if a report ever looks an hour off on a transition Sunday.
• Treating pre-2006 Indiana timestamps as ordinary Eastern. Most of the state was on EST year-round until April 2, 2006. Those records need the county-specific IANA zone, not a blanket America/New_York.
• Scheduling anything at 2:30 a.m. Eastern. See the spring-forward gap. Once a year it silently does not happen.

How modern software handles this

A calendar app, a database, or a scheduler should never store "EST" or "EDT" as the time zone. Both are surface labels whose meaning depends on the date of the event and, as the Australian case shows, on who wrote them. Store the IANA identifier and let the runtime compute the offset: America/New_York for the US East Coast, America/Toronto for Ontario, America/Detroit for Michigan (whose pre-1970 history differs enough to earn its own zone), America/Indiana/Indianapolis and its siblings for Indiana, America/Cancun for Quintana Roo, and America/Atikokan for the Ontario holdout.

Storing the IANA name solves three problems at once. It preserves the meaning of historical timestamps across past rule changes, including 2007 and Indiana's 2006 switch. It removes the EST/EDT ambiguity at the point where it does the most damage, which is an event created on one side of a transition and read on the other. And it picks up future legislation automatically whenever tzdata is updated — which matters more this year than most. Florida passed its own Sunshine Protection Act in 2018, but a state cannot stay on daylight time without federal permission. At the federal level, the Senate passed a permanent-daylight-time bill by unanimous consent on March 15, 2022 and the House never took it up; this time the order reversed, and the House passed H.R. 139 on July 14, 2026 by 308 to 117. It is now with the Senate and is not law. If it ever passes, EST simply stops occurring in the United States, every calendar entry stamped "EST" for a future date becomes wrong, and every system storing America/New_York updates itself with the next tzdata release. Pair the zone name with a UTC instant and treat the abbreviation as a rendering detail — because that is all it has ever been. To see the two labels side by side, the EST to EDT conversion and the EDT to EST conversion lay out the hour in both directions.

Bottom line

Eastern Time has two abbreviations because the Uniform Time Act of 1966, as amended by the Energy Policy Act of 2005, splits the year into a standard stretch and a much longer daylight stretch: EST at UTC−5 for about four months, EDT at UTC−4 for the other thirty-four weeks, with the switches at 2:00 a.m. local time on the second Sunday in March and the first Sunday in November. ET is the honest way to avoid picking. Seventeen states and DC sit entirely inside the zone, five more are split, and Ontario and Quebec run the same schedule. The clean exceptions are all foreign — Quintana Roo, Jamaica, the Cayman Islands, Panama, and two Canadian holdouts that never move — and the dangerous one is Australian, where the same three letters can still mean UTC+10. Store America/New_York, convert through a library that reads current tzdata, and treat any bare "EST" you did not write yourself as a question rather than an answer.