Convert between Unix timestamps and dates
A Unix timestamp is just a count of seconds since January 1, 1970 (UTC) — it's how computers, databases, and APIs quietly track time behind the scenes. The problem is that a number like 1752537600 means nothing to a human until you convert it, and doing that math by hand (accounting for time zones, leap years, and whether the value is in seconds or milliseconds) is tedious and error-prone. This tool exists for the moment you're staring at a log file, a JSON payload, or a database row and need to know exactly what date and time that number represents, or the reverse: turning a date you have in mind into the epoch value your code expects.
The page opens with a live current Unix timestamp that ticks upward in real time, so you always have a correct reference value on hand without looking it up elsewhere. Below that, you can paste in any epoch timestamp and it converts instantly to a readable date and time, or go the other direction by entering a date and getting back the corresponding timestamp. It handles both standard second-based timestamps and millisecond-precision values, which matters because JavaScript's Date.now() and many logging systems use milliseconds while Unix cron and most server tools use seconds — mixing the two up is a classic source of off-by-1000x bugs.
Because the conversion runs entirely in your browser, nothing you paste in — timestamps, dates, or anything else — is sent to a server, which makes it safe to use with values pulled from private logs or internal systems. A practical habit: if a timestamp you're converting looks wildly wrong (like landing in the year 1970 or 50000+), you're probably reading a millisecond value as seconds or vice versa — check the digit count first, since ten digits is typically seconds and thirteen digits is typically milliseconds.
Convert between Unix epoch timestamps and human-readable dates directly in your browser.
View the current Unix timestamp updating live at the top of the page for a quick, always-accurate reference.
Enter the epoch value you want to decode into the input field, whether it's in seconds or milliseconds.
The tool instantly displays the corresponding human-readable date and time — no button click or page reload needed.
In the Date to Timestamp panel, set the date and time (read in your local time zone) and click Convert to Timestamp.
Use the Seconds / Milliseconds buttons to say how your input should be read. The results list the value in both units plus ISO 8601, UTC and local strings, each with a copy button.
The Local String line shows the same instant in your own time zone — in New York that is Wed Dec 31 2025 19:00:00 GMT-0500, which is why a "New Year" timestamp can land on the previous day on your screen.
A year in the tens of thousands means the number is milliseconds. Click Milliseconds and the same input becomes 2023-11-14T22:13:20.000Z.
The date and time are read in your browser's time zone. Toronto had already switched to daylight time (UTC−4) on 8 March, so 09:30 local is 13:30 UTC.
Negative values count backwards from the epoch; one day is 86,400 seconds.