Free Unix timestamp converter. Convert epoch time to date and date to timestamp in seconds or milliseconds, with UTC, local and ISO 8601 output, runs locally.
Convert Unix timestamps to human-readable dates and back, in seconds or milliseconds, with live current time and UTC, local and ISO 8601 output.
A Unix timestamp counts the seconds since 1 January 1970 UTC, compact for computers but meaningless to humans. Paste a timestamp and this converter shows the exact UTC time, your local time and the ISO 8601 string. It auto-detects whether you entered seconds or milliseconds, so logs and API responses in either format just work.
Paste a Unix time in seconds or milliseconds.
See UTC, local and ISO 8601 output.
Choose a date to convert back to a timestamp.
Copy any value with one click.
Going the other way, pick any date and time and instantly get the Unix value in both seconds and milliseconds plus the ISO string. A live clock shows the current epoch time, which you can copy directly. Every field has a copy button, and all conversions happen locally, nothing is uploaded.
A Unix timestamp counts time since 00:00:00 UTC on 1 January 1970. Most servers, databases and APIs use seconds, which is a 10-digit number today, while JavaScript's Date.now() and many logging tools use milliseconds, a 13-digit number. If a converted date lands in 1970 or thousands of years in the future, you've probably mixed the two up. A timestamp is always in UTC and has no time zone of its own; the time zone only matters when you display it, which is why the converter shows both UTC and your local time.
Unix time ignores leap seconds, so every day is treated as exactly 86,400 seconds, which keeps date arithmetic simple. A bigger issue is the year 2038 problem: systems that store timestamps as signed 32-bit integers overflow at 03:14:07 UTC on 19 January 2038, when the count passes 2,147,483,647 and wraps to a date in 1901. Modern 64-bit systems are safe, but old embedded devices, file formats and database columns declared as 32-bit integers may still be affected. If you store timestamps, use 64-bit integers or a proper date-time type.
It's the number of seconds elapsed since 00:00:00 UTC on 1 January 1970 (the Unix epoch), used widely in programming to represent a point in time compactly.
It uses the length of the number: about 10 digits is treated as seconds and about 13 digits as milliseconds, which covers current dates in both formats.
You get UTC, your browser's local time zone, and the timezone-aware ISO 8601 string, so you can read the moment however you need.
Yes: completely free, no signup, and all conversions run locally in your browser.
Paste the epoch value and the converter shows the human-readable date in both UTC and your local time. It auto-detects seconds vs milliseconds and also converts a date back to a timestamp.
The tool displays the live current epoch time (updating each second), which you can copy in one click, along with fields to convert any timestamp both ways.
A 10-digit value is seconds and a 13-digit value is milliseconds; the converter detects the length automatically and shows the correct date, with a note on the timezone used.
Tool GuidesPhotos carry hidden data like GPS location and camera details. Here's why that matters for privacy and how to strip it before sharing.
Tool GuidesCPS means clicks per second. Here's how it's measured, what a good score looks like, and how to test your own click speed for free.
Tool GuidesCombine several PDFs into one document, reorder the pages, and keep everything private — no software and no server upload.