Unix timestamp to EDT converter
America/New_York · United States (Eastern)
Current Unix timestamp live
–
–
Epoch to America/New_York (EDT) converter
Timestamps below are shown in America/New_York (EDT). The unit is auto-detected from the input.
Seconds or milliseconds — the unit is auto-detected. Example: 1735689600
UTC ISO 8601
–
Local — auto
–
RFC 2822 / GMT
–
Seconds value
–
Relative time
–
UTC offset
UTC-04:00
Abbreviation: EDT
Daylight saving
Observed
Jan UTC-05:00 · Jul UTC-04:00
Region
United States (Eastern)
IANA: America/New_York
Next offset change
2026-11-01
→ UTC-05:00
Reference conversions for America/New_York (EDT)
The same Unix timestamps converted to America/New_York (EDT) time (UTC-04:00, EDT) — useful as a quick sanity-check table while you work.
| Unix timestamp (seconds) | UTC (ISO 8601) | America/New_York (EDT) (EDT) |
|---|---|---|
| 0 | 1970-01-01T00:00:00.000Z | 12/31/1969, 19:00:00 EST |
| 946,684,800 | 2000-01-01T00:00:00.000Z | 12/31/1999, 19:00:00 EST |
| 1,754,136,000 | 2025-08-02T12:00:00.000Z | 08/02/2025, 08:00:00 EDT |
| 2,147,483,647 | 2038-01-19T03:14:07.000Z | 01/18/2038, 22:14:07 EST |
| 2,524,608,000 | 2050-01-01T00:00:00.000Z | 12/31/2049, 19:00:00 EST |
| 1,787,458,619 | 2026-08-23T04:16:59.474Z | 08/23/2026, 00:16:59 EDT |
Using America/New_York (EDT) in real projects
United States (Eastern) runs on America/New_York, which is UTC-04:00 (with daylight saving moving it to UTC-04:00 part of the year).
Whenever your app stores a Unix timestamp and then displays it to a user in United States (Eastern), you should convert using an IANA
timezone identifier like America/New_York rather than a hard-coded offset — the OS keeps the DST rules up to date for you.
For example, an event logged at 2038-01-19T03:14:07.000Z UTC renders as 01/18/2038, 22:14:07 EST in America/New_York (EDT).
The same number means a different wall-clock time in London, Tokyo or New York — which is exactly why storing the epoch
value is the safe, portable choice. See how in the JavaScript timestamp guide or the
Python epoch converter guide.
Frequently asked questions
What is the current UTC offset for America/New_York (EDT)?
America/New_York (EDT) (America/New_York) is currently at UTC-04:00, usually written as EDT. Because a Unix timestamp counts seconds since 1970-01-01T00:00:00Z, converting it to America/New_York (EDT) means adding the offset shown above.
Does America/New_York (EDT) observe daylight saving time?
Yes. America/New_York (EDT) switches between UTC-05:00 in the standard part of the year and UTC-04:00 during daylight saving time, so the abbreviation changes too. The next scheduled change is 2026-11-01, when the offset becomes UTC-05:00.
How do I convert a Unix timestamp to America/New_York (EDT)?
Take the epoch seconds value and add -04:00 (EDT) to get the wall-clock time in America/New_York (EDT). The converter on this page does that instantly for any timestamp, and shows the UTC value alongside so you can compare.
Why is a Unix timestamp the same in America/New_York (EDT) as everywhere else?
The Unix epoch is an absolute instant, not a wall-clock reading. The number is identical no matter where you read it — only the human-readable date and time changes depending on the timezone. America/New_York (EDT) (America/New_York) is one of the IANA identifiers used to pick the right offset automatically.
What programming languages handle America/New_York (EDT) automatically?
Every modern language reads IANA timezones like America/New_York natively — from Date and Intl in JavaScript, to zoneinfo in Python, time in PHP, java.time in Java and time.Time in Go. Grab copy-paste code on the America/New_York (EDT) conversion snippets to get started.
Popular timezones
Convert epoch time in the most-used zones
Related zones in Americas
Nearby regions with similar offsets
About America/New_York (EDT)
America/New_York (EDT) (America/New_York) is one of the IANA timezones supported by the converter above. IANA identifiers are the standard way to refer to timezones in programming languages and databases — they handle daylight saving transitions automatically.
Convert epoch to America/New_York (EDT)
The Unix epoch is a single instant in time that looks the same in every timezone — only its wall-clock representation changes. The converter above shows the same timestamp formatted in America/New_York (EDT) (as well as UTC), so you can see exactly what a given epoch value means in this part of the world.
Looking for another zone? Browse the full list on the timezone index.