Timestamp Converter
Convert Unix timestamps, ISO 8601 dates, and timezones instantly.
0Conversions
001970-01-01T00:00:00.000ZThu, 01 Jan 1970 00:00:00 GMTThursday, January 1, 1970 at 12:00:00 AM UTC0 seconds agoThursdayWeek 1 of 1970About the Unix Timestamp Converter
This Unix timestamp converter turns epoch seconds or milliseconds into a readable date in both UTC and your local time, and converts a date back to a timestamp. Seconds and milliseconds are detected automatically.
A Unix timestamp converter translates the number of seconds since 1 January 1970 into something a person can read. Timestamps appear constantly in logs, API responses, JWT claims and database columns, and none of them mean anything at a glance.
The seconds-versus-milliseconds confusion causes most timestamp bugs. Unix time is defined in seconds, but JavaScript works in milliseconds, so a value passed between the two without conversion lands in 1970 or in the year 55000. The scale is detected here by magnitude.
Both UTC and local time are shown, because a timestamp has no timezone of its own — it is an absolute instant, and the timezone only appears when it is formatted. Seeing both makes off-by-hours discrepancies obvious rather than mysterious.
How to use the Unix Timestamp Converter
- Paste a timestamp. Enter epoch seconds or milliseconds; the scale is detected.
- Read the date. See the instant in both UTC and your local timezone.
- Or enter a date. Convert the other way to get a timestamp.
- Copy the value. Take the timestamp or the formatted date.
Unix Timestamp Converter features
- Epoch seconds or milliseconds, detected automatically
- Readable date in both UTC and your local time
- Converts a date back to a timestamp
- ISO 8601, UTC string, relative time, day of week and week number
- Selectable timezone
- A button for the current timestamp
- Copy any value
Frequently asked questions
What is a Unix timestamp?
The number of seconds since 1 January 1970 UTC. Because it is a single number with no timezone attached, it is unambiguous — which is why nearly every system stores time this way.
Seconds or milliseconds?
Unix uses seconds; JavaScript uses milliseconds. Both are accepted here and detected by magnitude, since a ten-digit value is seconds and a thirteen-digit one is milliseconds. Mixing them up produces dates in 1970 or the year 50,000.
Why show UTC and local time?
Because the difference is where the bugs are. A timestamp is a fixed instant; how it is displayed depends on the zone, and comparing a UTC log entry against a local-time screenshot is a common source of confusion.
Can I convert a list of timestamps at once?
No, this handles one at a time. For a column of them, a spreadsheet formula or a short script is the right tool.
What is the 2038 problem?
A signed 32-bit timestamp overflows in January 2038. Modern systems use 64-bit values and are unaffected, but embedded devices and old file formats can still be caught by it.