Developer · Browser tool
Convert a Unix timestamp to a readable date
Paste an epoch value in seconds, milliseconds or microseconds. The result updates as you type: UTC, ISO 8601, your local time and how long ago it was.
Free, no daily limitNo account, nothing uploaded
- The unit is read from the digit count: 10 digits for seconds, 13 for milliseconds, 16 for microseconds
- Every result line has its own Copy button
- Works the other way too: pick a date and time, get the epoch value
- Negative values work and give dates before 1970
Timestamp to date
Press Now to load the current epoch second.
Date back to epoch
Pick a date and time and choose whether it is meant as your local time or as UTC. You get the epoch value in seconds and milliseconds, the ISO 8601 string and the relative time.
Date to timestamp
What each result line means
- UTC
- The moment in Coordinated Universal Time, written as date and time.
- ISO 8601
- The standard string with a Z at the end, for example 2026-09-27T00:00:00.000Z. Safe to paste into code, SQL or a log filter.
- Local
- The same moment in your browser's time zone, with the UTC offset in the label.
- Relative
- How far the moment is from now, such as 3 days ago or in 2 hours.
- Seconds and milliseconds
- The epoch value in both units, so you can switch between a database column in seconds and a JavaScript value in milliseconds.
How epoch values are read
A Unix timestamp counts the time since 1 January 1970 at 00:00:00 UTC, without leap seconds. The same instant has one epoch value everywhere; only the displayed date changes with the time zone. That is why the converter shows the UTC reading next to the local one.
Seconds or milliseconds
The unit comes from the length of the number. Up to 11 digits is read as seconds, 12 to 14 as milliseconds and 15 to 17 as microseconds. The detected unit is shown above the result, so a value in milliseconds that was meant as seconds is easy to spot. Spaces, commas and underscores in the number are ignored.
The 2038 limit
Systems that store time as a signed 32-bit number overflow on 19 January 2038. This page uses the browser's own date handling and is not affected, but a system you are debugging may be. Values beyond the range a JavaScript date can hold, roughly the year 275,760, are reported as out of range.
Free, and why nothing expires
This is one of the 37 WoluTools tools that run entirely in your browser. The allowance of 3 free jobs a day applies to tools that process files on the server, not to this one. Nothing is sent to a server and nothing is stored, so there is no result to expire.
Questions before you run it
What input does the converter accept?
A Unix epoch value in seconds, milliseconds or microseconds, positive or negative. For the other direction, pick a date and time in the date field and choose local time or UTC.
How does it tell seconds from milliseconds?
By the number of digits. Up to 11 digits is read as seconds, 12 to 14 as milliseconds and 15 to 17 as microseconds. The detected unit is shown above the result.
Which time zone is used?
Every result shows UTC and ISO 8601, plus the same moment in your browser's local time zone with its UTC offset. When you convert a date back to epoch, you choose whether the date is local time or UTC.
Does it handle dates after 2038?
Yes. The page uses the browser's date handling, which is not limited to 32-bit values. Only values beyond roughly the year 275,760 are out of range.
Is it free, and is anything uploaded?
It is free with no daily limit and needs no account. The conversion runs in your browser, so the values you enter are not sent anywhere.