Unix Timestamp Converter
Convert Unix timestamps (epoch time) to readable dates and back, in your local time zone or UTC. This epoch converter reads seconds, milliseconds, microseconds and nanoseconds, and everything is computed in your browser — nothing is sent anywhere.
Timestamp to date
No timestamp yet
Paste a Unix timestamp above, or press “Use now”.
Date to timestamp
No date yet
Pick a date and time above to get its Unix timestamp.
Add / subtract time
No calculation yet
Enter an amount to shift the starting time forward or back.
Unix time counts the seconds elapsed since 00:00:00 UTC on 1 January 1970, ignoring leap seconds. Negative values are valid and point at dates before 1970.
Auto-detect reads values under 1011 as seconds, under 1014 as milliseconds, under 1017 as microseconds, and anything larger as nanoseconds. A fraction after a dot or comma (1700000000.123) is kept to the nanosecond, and a unit suffix such as ms or ns overrides detection.
It also accepts hexadecimal (0x6553f100), scientific notation (1.7e9), grouped digits (1,700,000,000), .NET /Date(…)/ values, MongoDB ObjectIds and UUID v1, v6 and v7. Windows FILETIME, .NET ticks, Apple Cocoa time and Excel serial dates are in the unit list.
Frequently asked questions
What is a Unix timestamp?
The number of seconds elapsed since 1 January 1970 00:00:00 UTC, known as the epoch. Because it is a single integer in UTC with no time zone or formatting attached, it is what databases, log files and APIs store when they need a moment in time that cannot be misread.
Is my timestamp in seconds or milliseconds?
Count the digits. A present-day timestamp in seconds has 10; in milliseconds it has 13. If a date comes out in January 1970 you have fed seconds into a milliseconds field, and if it lands tens of thousands of years in the future you have fed milliseconds into a seconds field. Microseconds have 16 digits and nanoseconds 19, and a value with a decimal point such as 1700000000.123 is seconds with a fraction. All of them are detected here, so you can convert any of them without dividing by a thousand yourself.
How do I convert a timestamp to a readable date?
Paste the number into the timestamp field and the date is shown in your local time zone and in UTC together, along with the ISO 8601 form you would put in a JSON payload. Typing a date into the other field converts the other way.
Which time zone does the conversion use?
Both at once: your browser’s local zone and UTC are shown side by side, since a timestamp itself has no zone — it is an instant, and a zone only decides how that instant is written down. Seeing both is usually what settles an argument about whether a log entry is off by an hour or by a whole offset. Going the other way, a date you type is read in your local zone unless you tick "Interpret as UTC", which is what you want for a time copied out of a server log.
What is the year 2038 problem?
A timestamp stored in a signed 32-bit integer overflows on 19 January 2038, after which it wraps to a negative number and reads as 1901. Modern systems use 64-bit timestamps and are unaffected, but old file formats, embedded devices and some database columns are not, which is why the date is worth knowing about.
Can it convert a negative timestamp?
Yes. Negative values count backwards from the epoch, so they represent dates before 1970 — useful when a birth date or a historical record has been stored as an epoch value and comes back as a number that looks like an error.
Does anything get sent to a server?
No. The whole tool is JavaScript running in your own browser, so nothing you type or paste is sent over the network, written to a log or attached to an analytics event. You can confirm it by opening the network tab and watching it stay empty while you work.