Timestamp Converter
Convert Unix timestamps to dates.
CONVERSION RESULTS
- Timestamp:
- —
- ISO 8601:
- —
- RFC 2822:
- —
- UTC:
- —
- Local:
- —
- Relative:
- —
- Timezone:
- —
Every row is the same instant. Timestamps count seconds since 1970-01-01 UTC, and both directions run in this tab.
// What each row means
- >Timestamp — Seconds since 1970-01-01 UTC — the ten-digit number logs and databases store.
- >ISO 8601 — The same instant ending in Z, the form JSON APIs and date libraries expect.
- >RFC 2822 — The mail and HTTP header format: day, date, month, year, time and GMT.
- >UTC — The same GMT string kept as its own row, so a reader comparing zones has a fixed reference.
- >Local — Your device’s rendering of that instant, including its zone label — what someone next to you would see.
- >Relative — How far the moment sits from now, counted in seconds, minutes, hours, days, months or years.
- >Timezone — The UTC offset and IANA zone name behind the local row, taken from the instant itself so daylight saving is respected.
// One timestamp, seven readings
IN
1700000000
OUT
2023-11-14T22:13:20.000Z
The ISO 8601 row for that timestamp. The local, RFC 2822 and relative rows describe the same moment from a different angle.
// Questions about this tool
Why are there two different times?
One is your local time zone and the other is UTC (time-zone independent). They describe the same instant.
Seconds or milliseconds?
This tool uses seconds, which is the standard Unix timestamp. If you have milliseconds, divide by 1000 first.
What does [now] do?
It fills that field with the current moment, so you can read "now" as a timestamp or as a date instantly.
What does [COPY] copy?
Every row of the results panel, one label per line, so the whole reading can be pasted into a ticket, a note or a message.
Why does my date input ignore seconds?
The datetime picker stops at minutes for simplicity; the result still reports whole seconds.