Unix Timestamp Converter
Epoch (Unix time) ↔ ISO 8601, UTC and your local timezone.
Epoch timestamp
Unit
iso 8601
local
Date and time
Timezone
About Unix timestamps
A Unix timestamp counts the seconds since 1970-01-01 00:00:00 UTC (theepoch), ignoring leap seconds. It is the native time representation in most databases, logs, and APIs, and the whole ecosystem stores times as integers — but a number like 1700000000 means nothing until you convert it. This tool converts in both directions, entirely in your browser.
Seconds, milliseconds, or microseconds?
Language conventions differ: Go and PHP count seconds (~10 digits today), JavaScript's Date.now() countsmilliseconds (~13 digits), and Rust's SystemTimeand some traces use microseconds (~16 digits). The tool auto-detects the unit from the magnitude and labels it in the status line, so pasting a value from any ecosystem just works. You can still force a unit if you know better.
Edge cases
Values outside ±8.64e15 milliseconds exceed JavaScript's safe date range and are rejected. Negative epochs (before 1970) are supported. Times are shown both as UTC ISO 8601 and in your local timezone via theIntl API, so a value you read at 3:00 a.m. local is unambiguous about which instant it refers to.
Related tools
Turn a converted date into a record in the JSON formatter, or encode an epoch-adjacent value as a URL-safe string with the Base64 encoder.
FAQ
Why does my timestamp look wrong?
The most common cause is unit mismatch: a value like 1700000000 is seconds, 1700000000000 is milliseconds, and 1700000000000000 is microseconds. This tool auto-detects the unit from the magnitude.
Is my date sent to a server?
No. All conversion happens locally in your browser with JavaScript Date and Intl APIs — nothing is uploaded.