Current epoch time in Etc/UTC
Etc/UTC · Coordinated Universal Time
Current Unix timestamp live
–
–
Epoch to Etc/UTC converter
Timestamps below are shown in Etc/UTC. 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+00:00
Abbreviation: UTC
Daylight saving
Not observed
Fixed UTC+00:00 all year
Region
Coordinated Universal Time
IANA: Etc/UTC
Next offset change
None
No DST transitions scheduled
Reference conversions for Etc/UTC
The same Unix timestamps converted to Etc/UTC time (UTC+00:00, UTC) — useful as a quick sanity-check table while you work.
| Unix timestamp (seconds) | UTC (ISO 8601) | Etc/UTC (UTC) |
|---|---|---|
| 0 | 1970-01-01T00:00:00.000Z | 01/01/1970, 00:00:00 UTC |
| 946,684,800 | 2000-01-01T00:00:00.000Z | 01/01/2000, 00:00:00 UTC |
| 1,754,136,000 | 2025-08-02T12:00:00.000Z | 08/02/2025, 12:00:00 UTC |
| 2,147,483,647 | 2038-01-19T03:14:07.000Z | 01/19/2038, 03:14:07 UTC |
| 2,524,608,000 | 2050-01-01T00:00:00.000Z | 01/01/2050, 00:00:00 UTC |
| 1,787,458,619 | 2026-08-23T04:16:59.578Z | 08/23/2026, 04:16:59 UTC |
Using Etc/UTC in real projects
Coordinated Universal Time runs on Etc/UTC, which is UTC+00:00.
Whenever your app stores a Unix timestamp and then displays it to a user in Coordinated Universal Time, you should convert using an IANA
timezone identifier like Etc/UTC 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/19/2038, 03:14:07 UTC in Etc/UTC.
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 Etc/UTC?
Etc/UTC (Etc/UTC) is currently at UTC+00:00, usually written as UTC. Because a Unix timestamp counts seconds since 1970-01-01T00:00:00Z, converting it to Etc/UTC means adding the offset shown above.
Does Etc/UTC observe daylight saving time?
No. Etc/UTC keeps the same UTC+00:00 offset all year round, so timestamps in this zone never shift for daylight saving time.
How do I convert a Unix timestamp to Etc/UTC?
Take the epoch seconds value and add +00:00 (UTC) to get the wall-clock time in Etc/UTC. 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 Etc/UTC as everywhere else?
The Unix epoch is an absolute instant, not a wall-clock reading. The number does not change no matter where you read it — only the human-readable date and time changes depending on the timezone. Etc/UTC (Etc/UTC) is one of the IANA identifiers used to pick the right offset automatically.
What programming languages handle Etc/UTC automatically?
Every modern language reads IANA timezones like Etc/UTC 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 Etc/UTC conversion snippets to get started.
Popular timezones
Convert epoch time in the most-used zones
About Etc/UTC
Etc/UTC (Etc/UTC) 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 Etc/UTC
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 Etc/UTC (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.