Unix Timestamp Converter
Current Unix timestamp (live)
Timestamp to date
Date to timestamp
This free Unix Timestamp Converter works in both directions and keeps a live epoch clock running at the top of the page. Paste any Unix timestamp - in seconds or milliseconds - and it converts it instantly into a human-readable date, shown in UTC, in your own local time and in ISO 8601 format, along with how long ago (or how far ahead) that moment is. Or pick any date and time and it gives you the exact timestamp to use in your code, database or API call. The live counter at the top shows the current Unix time in seconds and milliseconds, updating every second, straight from your own clock.
A Unix timestamp is simply a count of seconds since midnight at the start of 1 January 1970, UTC - a moment programmers call "the epoch". Because it is just a number, computers can sort, compare and store times without worrying about time zones or date formats, which is why timestamps turn up everywhere: in API responses, database rows, log files, cookies and JWT tokens. The one trap is units. Most systems use seconds (a 10-digit number today), but JavaScript and many APIs use milliseconds (13 digits), and feeding one into a field expecting the other lands you in 1970 or the year 55000. This converter auto-detects which one you pasted by its size, and tells you which it assumed, so you are never left guessing. Everything runs in your browser; the values you enter are never uploaded or stored.
How to use
- Watch the live clock at the top if you just need the current Unix timestamp in seconds or milliseconds.
- To decode a timestamp, paste it into the "Timestamp to date" box - auto-detect handles seconds and milliseconds.
- Read the same moment in UTC, your local time and ISO 8601, plus a plain-English "how long ago".
- To create a timestamp, pick a date and time in the "Date to timestamp" card and click Convert.
- Copy the seconds value for most systems, or the milliseconds value for JavaScript and similar APIs.
Frequently asked questions
What is the Unix epoch?
The epoch is 00:00:00 UTC on 1 January 1970, the starting point from which Unix time counts. A timestamp of 0 means exactly that moment; negative timestamps describe earlier dates, and every second since adds one. Almost all modern software shares this reference point, which is what makes timestamps portable between systems.
Should I use seconds or milliseconds?
It depends on the system. Unix tools, most databases, PHP, Python and most APIs use seconds. JavaScript's Date.now() and some APIs use milliseconds. A quick check: current timestamps in seconds have 10 digits; in milliseconds they have 13. This converter auto-detects by length, and you can also force the unit from the dropdown.
Why does my timestamp convert to a date in 1970?
Almost always a unit mix-up: a milliseconds value was read as seconds, or the other way round, or the value was divided twice somewhere in your code. Paste the raw number here with auto-detect on and compare both readings - if the milliseconds reading gives a sensible recent date, that is the unit your system is using.
What happens in 2038?
Older systems that store timestamps in a signed 32-bit integer run out of room on 19 January 2038 and wrap around to 1901. Modern 64-bit systems are unaffected for practical purposes. This converter uses your browser's date engine, so it handles dates far beyond 2038 correctly.
Does the date-to-timestamp side use my time zone?
Yes. The date and time you pick is read as your local time, and the converter also shows that same moment in UTC so you can double-check. If you need a timestamp for a specific UTC moment, adjust for your offset or compare against the live UTC clock at the top of the page.
Related Tools
More free developer tools from ToolVora - every tool runs entirely in your browser, with no sign-up and no uploads: