4 min read
EST, EDT, and ET explained
Understand EST, EDT, and ET before writing Eastern Time in an invite, log, public event, or converter result, with rules for offsets and city timezones.
EST is standard time
EST refers to Eastern Standard Time, which is UTC-5. It does not describe the daylight-saving period, even though many people casually write EST when they mean the Eastern timezone.
EDT is daylight time
EDT refers to Eastern Daylight Time, which is UTC-4. Many people casually write EST all year, which creates ambiguity.
ET is safer for humans
ET lets the calendar system apply the correct seasonal offset for places such as New York. For exact conversions, use a date and city.
Why search results can look inconsistent
A page titled EST to PST may show EDT and PDT on summer dates if it uses New York and Los Angeles timezone rules. That is date-aware behavior, not a math error.
What to write in an invite
For people, write ET with the date or use a city. For fixed offsets, write EST UTC-5 or EDT UTC-4 so the meaning is not left to interpretation.
Recommended starting point
Use ET or a city when humans are attending. Use EST or EDT only when the fixed offset is intentional.
Common failure
The common failure is writing EST all year, then wondering why a calendar shows EDT in summer.
Use useChrono for the exact date
Use EST/EDT converter pages for quick checks, but read the abbreviation note when the displayed city offset changes seasonally.
Decision notes
- When the date matters, a city-based timezone is easier to verify than a bare abbreviation.
- When the offset matters more than the city, write the UTC offset next to the abbreviation.
- For public webinars, avoid EST in the title unless the event is specifically UTC-5.
- For internal meetings, use ET or New York so the calendar follows the seasonal Eastern offset.
- If someone sends only EST, ask whether they mean Eastern Time before creating the event.
- For API payloads or logs, store UTC and display local Eastern time only in the user-facing layer.