Convert Unix epoch timestamps to human-readable dates and back. Auto-detects seconds vs milliseconds. Free and runs in your browser.
Paste a Unix epoch timestamp to see it as a human-readable date and time, or enter a date to get the epoch value back. The converter detects whether your number is in seconds or milliseconds automatically, so you don't have to remember which one an API used.
Both directions update as you type, making it quick to sanity-check a timestamp from a log line, a database column or an API response.
Systems store time as an epoch number because it is compact and unambiguous, but that number means nothing to a human reading a log or debugging a bug report. Converting it to a real date tells you when an event actually happened, and converting the other way lets you build queries or fixtures around a specific moment.
The seconds-versus-milliseconds ambiguity trips people up constantly; automatic detection removes that guesswork.
A Unix timestamp counts the seconds (or milliseconds) elapsed since January 1, 1970 UTC. The converter reads your value, decides its scale by magnitude, and uses the browser's date handling to render it in a readable format — and to run the conversion in reverse. All of it happens locally in your browser with no server involved.
Because it uses your browser's own clock and locale, the readable output reflects standard date handling on your device.
It is the number of seconds (or milliseconds) since January 1, 1970 UTC, a standard way to represent a point in time.
It infers the scale from the size of the number, since millisecond timestamps are about a thousand times larger.
Yes. Enter a date and time and the converter returns the matching Unix timestamp.
No. The conversion runs entirely in your browser.