How to use Timestamp Converter
- Enter a Unix timestamp (in seconds or milliseconds) and click "Convert to date", or click "Use current time".
- Or pick a date and time and click "Convert to timestamp".
- Results show both your local time and UTC.
Key benefits
- Auto-detects seconds vs. milliseconds.
- Shows both local time and UTC side by side.
- One click to grab the current timestamp.
- Runs entirely in your browser using your device's clock.
Privacy
Timestamp Converter runs entirely in your browser using local JavaScript. Your files and text are processed on your own device and are never uploaded to QuickTiny's servers.
Frequently asked questions
How does it know if my timestamp is in seconds or milliseconds?
Timestamps larger than 20,000,000,000 are treated as milliseconds; smaller values are treated as seconds. This covers all realistic dates.
What time zone is used?
Your input date is interpreted in your browser's local time zone. The UTC value is shown alongside it for reference.
Why does my timestamp show the "wrong" time or timezone?
A Unix timestamp itself has no timezone — it's a single, fixed instant (seconds since 1970-01-01 UTC). What looks "wrong" is almost always a display or conversion step elsewhere silently using the wrong timezone — for example, formatting it with the server's local timezone when UTC was intended, or vice versa. Compare against both values shown above: if Local looks right but UTC looks off (or the reverse), that confirms the timestamp itself is correct and the mismatch is happening somewhere else in your code.
Can I convert dates before 1970?
Yes — negative Unix timestamps representing dates before January 1, 1970 are supported.
How do I get a Unix timestamp in my code, not just here?
See the Unix Timestamp Cheat Sheet for the exact call in JavaScript, Python, Java, PHP, Go, Ruby, SQL, C#, and the shell — including which ones use seconds vs. milliseconds.