Timestamp Converter
This free timestamp converter turns Unix timestamps into readable dates and back, entirely in your browser.
Timestamp → date
Date → timestamp
How to use
- Paste a Unix timestamp (seconds or milliseconds — the unit is auto-detected, with a manual override) or pick a date and time.
- Read the result: ISO 8601 in UTC plus your local timezone, or Unix seconds and milliseconds for a chosen date.
- Use the Now button to capture the current moment; copy what you need.
Frequently asked questions
How does the tool decide whether my value is seconds or milliseconds?
Automatically: any value whose absolute magnitude is greater than 100,000,000,000 (1e11) is treated as milliseconds, anything else as seconds. The threshold works because 1e11 seconds is around the year 5138 — no real second-based timestamp gets there — while 1e11 milliseconds is March 1973, which real millisecond timestamps have been past since the beginning. A manual override switch lets you force either interpretation.
Which timezone does the "local time" line use?
The timezone your device is set to at the moment of conversion, shown with its UTC offset. A Unix timestamp itself has no timezone — it is a pure count of time since 1970-01-01T00:00:00 UTC — so the same value maps to different wall-clock times in different places, and the UTC column is the unambiguous reference.
What exactly is a Unix timestamp?
The number of seconds (or milliseconds, depending on convention) elapsed since 1970-01-01T00:00:00 UTC, not counting leap seconds. Most logging systems, databases and APIs use this form; the seconds convention dominates in Unix tooling while JavaScript, Java and C# defaults use milliseconds.
Why does my code show 1970 or a far-future date for this value?
Almost always a seconds-versus-milliseconds mix-up. Interpreting a millisecond value as seconds lands in January 1970; interpreting seconds as milliseconds lands tens of thousands of years out. Convert the value here, check the two readings, and you will spot the wrong unit immediately.
Does it handle dates before 1970 or unusual magnitudes?
Yes. Negative timestamps (before 1970) convert correctly, and anything outside what a JavaScript Date can represent — roughly 275,000 years each way — fails with an explicit error rather than a silently wrong result.
Is anything I paste sent to a server?
No. The conversion is arithmetic performed by your browser on your device; timestamps from production logs, tokens or API responses never leave the page.
Related tools
About this tool
This free timestamp converter turns Unix timestamps into readable dates and back, entirely in your browser. Paste a timestamp and the tool decides whether it is seconds or milliseconds automatically — values whose absolute magnitude exceeds 100,000,000,000 are treated as milliseconds, a threshold every real millisecond timestamp is far above and no second timestamp will reach for millennia — with a manual override when you want to force an interpretation. You get the ISO 8601 UTC form and your device local time side by side, so a log line from another continent reads correctly at a glance. Going the other way, pick a date and time and receive both the seconds and milliseconds forms, computed against your own timezone and shown with its UTC offset. A one-click Now button fills in the current moment for quick sanity checks. Negative values before 1970, sub-second precision and far-future dates all work; out-of-range or malformed input fails loudly instead of quietly producing a wrong year. The conversion is plain arithmetic on your device: nothing you paste is sent anywhere, which makes it safe for timestamps that appear in production logs, signed tokens or API responses.