Unix Timestamp Converter
Convert Unix epoch timestamps to human-readable dates and back. Auto-detects seconds vs. milliseconds.
Advertisement
…
Your converted date will appear here.
The date is interpreted in your browser's local timezone.
The timestamp will appear here.
What is a Unix timestamp?
A Unix timestamp (also called epoch time) counts the seconds elapsed since January 1, 1970 00:00:00 UTC. Because it's just a number, it's unambiguous across timezones — which is why databases, APIs, and log files love it, and why humans need a converter to read it.
Seconds vs. milliseconds
The most common gotcha: some systems emit seconds (10 digits, e.g. 1759272000) while others — notably JavaScript's Date.now() — emit milliseconds (13 digits). Paste either one above; the converter detects the unit automatically, or you can force it with the dropdown.
FAQ
What is a Unix timestamp?
A Unix timestamp is the number of seconds that have passed since January 1, 1970 00:00:00 UTC (the Unix epoch), not counting leap seconds. It is a compact, timezone-free way to store dates and times.
Why do some timestamps have 10 digits and others 13?
10-digit timestamps count seconds, while 13-digit ones count milliseconds. JavaScript's
Date.now(), for example, returns milliseconds. This converter auto-detects which unit you pasted.What timezone does the converter use?
Both. Every conversion shows the result in UTC and in your browser's local timezone, plus the ISO 8601 format, so there is no ambiguity.
What is the Year 2038 problem?
Systems that store timestamps as signed 32-bit integers max out at 2,147,483,647 (January 19, 2038). Modern systems use 64-bit integers, which pushes the limit billions of years out — this converter handles 64-bit values fine.
Advertisement