Unix Timestamp Converter
Convert a Unix epoch timestamp into a human-readable date and time.
Seconds or milliseconds: how the converter decides
Paste a timestamp and the tool looks at its length after trimming spaces. Up to 11 characters are read as seconds. Twelve or more are read as milliseconds. A 10-digit value from a Unix shell or a database and a 13-digit value from JavaScript's Date.now() or a Java log both land on the right date:
| Input | Read as | UTC result |
|---|---|---|
1792368000 | seconds | Mon, 19 Oct 2026 00:00:00 GMT |
1792368000000 | milliseconds | Mon, 19 Oct 2026 00:00:00 GMT |
The cut-off is about characters, not size. 99999999999 (11 digits) is taken as seconds and gives a date in the year 5138. 100000000000 (12 digits) is taken as milliseconds and gives 3 March 1973.
Inputs that give a wrong date or a dash
Because the decision rests on length, a few formats trip it up:
| Input | What you see | Fix |
|---|---|---|
1792368000.5 | 21 Jan 1970: twelve characters, so it is read as milliseconds | Delete the fraction |
1792368000123456 (microseconds) | A date in the year 58767 | Delete the last three digits |
| 19-digit nanoseconds | — | Delete the last six digits |
1,792,368,000 | — | Remove the commas |
17923680 (truncated) | 27 Jul 1970 | Check you copied every digit |
Scientific notation such as 1.79e9 is accepted and read as seconds. Negative numbers are accepted too and give earlier dates. Very long negative values count as milliseconds, because the minus sign adds to the length.
Reading the UTC part and the local part
The result shows two versions of the same instant, separated by / local:. The first is UTC in a fixed format. The second uses your browser's time zone and date format, so two people looking at the same timestamp see different local text.
For 1792411200 the UTC part is Mon, 19 Oct 2026 12:00:00 GMT. A US-English browser set to India time shows 10/19/2026, 5:30:00 PM, while a UK browser in London shows 19/10/2026, 13:00:00. When you compare log lines from servers in different regions, or paste a time into a bug report, use the UTC part.
The current timestamp, and going the other way
The number at the top is the current Unix time in seconds, captured when the page loaded. It doesn't tick, so reload the page for a fresh value. It is shown with thousands separators for reading; remove the commas before you paste it into code or back into the box, or you'll get a dash.
This page converts timestamps to dates only. To turn a date into a timestamp, open your browser's developer console and run Math.floor(Date.parse("2026-10-19T00:00:00Z") / 1000), which returns 1792368000. Keep the Z to mean UTC; without it, the date is read in your local time zone.
Frequently asked questions
Can I convert the exp and iat values from a JWT?+
Yes. Those claims are whole seconds, so paste the number as it appears in the decoded payload and the date shows up immediately.
Does daylight saving time change the result?+
Not the UTC part. The local part follows your device's time-zone rules, so the same timestamp can show a different local hour in summer and winter.
Why does a timestamp from my database show the wrong hour?+
The timestamp is probably right and the stored value was created from a local time treated as UTC, or the other way round. Compare the UTC part with what the application meant to save.
Is my input sent anywhere?+
No. The conversion uses your browser's built-in date functions and happens as you type, with nothing uploaded.
Embed this tool on your website
Free to use on blogs, school sites and intranets. Paste this code into your page's HTML; please keep the credit line.
<iframe src="https://utilityapp.lat/embed/dev/unix-timestamp-converter" title="Unix Timestamp Converter" width="100%" height="600" style="border:0;max-width:760px" loading="lazy"></iframe> <p style="font-size:13px"><a href="https://utilityapp.lat/dev/unix-timestamp-converter">Unix Timestamp Converter</a> by UtilityApp</p>