Unix Timestamp Converter
Convert a Unix epoch timestamp (seconds or milliseconds, auto-detected) into a human-readable UTC date, ISO 8601, RFC 7231 and a named timezone — and convert a date/time back into a Unix timestamp. Leave the input blank to read the current time.
Input
Seconds vs milliseconds is auto-detected (11+ digits = milliseconds). Leave blank to use the current time.
Adds a DST-aware wall-clock row for this timezone. All other rows are UTC.
Output
| Property | Value |
|---|---|
| No data yet | |
Guides
The Unix Timestamp Converter turns a Unix epoch timestamp into a readable date and turns a date back into a timestamp — in one place, with no timezone guesswork. A Unix timestamp counts the number of seconds (or milliseconds) that have elapsed since 00:00:00 UTC on 1 January 1970, so it shows up everywhere: server logs, databases, JWT exp claims, API responses, cron output and cookie expiry values.
How to use it
Pick a direction at the top:
- Timestamp → Date — paste a Unix timestamp and read back the full breakdown: ISO 8601, an RFC 7231 UTC string, the plain UTC date and time, the day of the week, and both the seconds and milliseconds forms. The tool auto-detects whether your number is in seconds or milliseconds (11 or more digits is treated as milliseconds), and you can force either interpretation with the Interpret as dropdown.
- Date → Timestamp — type a date or date-time and read back the Unix timestamp in seconds and milliseconds, plus its canonical ISO and UTC strings.
Leave the input blank to convert the current time — handy when you just need "what is the Unix timestamp right now".
Timezones and UTC
Every core field is computed in UTC, so the result is identical no matter where you or the server running it happen to be. When converting a timestamp to a date, the Show time in dropdown adds one extra row with the wall-clock time in a named zone (New York, London, Tokyo and more). That row is daylight-saving aware: the same zone correctly reads UTC-5 in winter and UTC-4 in summer for US Eastern, for example.
When converting a date to a timestamp, a value without an explicit offset is read as UTC. Add a Z or an offset such as +02:00 to the end of your input if it represents a different zone, and a date on its own (like 2024-01-01) is treated as midnight UTC.
What input formats are accepted?
For Date → Timestamp, the converter accepts ISO-style values: a bare date (2024-01-01), a date and time separated by a space or a T (2024-01-01 13:45:30 or 2024-01-01T13:45:30), optional fractional seconds, and an optional trailing Z or ±HH:MM offset.
Seconds or milliseconds — how is it decided?
By digit count. Ten digits or fewer is read as seconds; eleven or more as milliseconds. Because a seconds timestamp only reaches ten digits until the year 2286, this heuristic is reliable for present-day values — and you can always override it explicitly.
Is my data sent anywhere?
No. The conversion runs entirely in your browser, so nothing you paste leaves your device.