Convert Unix timestamps to human-readable dates and times.
The Unix Timestamp Converter translates epoch time (seconds or milliseconds since January 1, 1970) into a readable date and time, and converts a chosen date back into its Unix timestamp. It's a staple for reading raw timestamps out of log files, API responses, or database records without doing the math by hand — all calculated instantly in your browser.
Made for everyone. Typical uses:
Converting the timestamp 1704067200 returns 2024-01-01 00:00:00 UTC. Typing the date 2026-10-05 returns 1791158400, and the millisecond value 1704067200000 returns the same date as 1704067200.
The result is always shown in UTC, so apply your own offset or use the Timezone Converter for a local time. A date typed with a time but no zone is read in your browser's local time, so add Z or an offset for a result that does not depend on where you are. Unix time ignores leap seconds, and microsecond or nanosecond values must be divided down to seconds or milliseconds first.
Accuracy: Conversions use well-known methods and are tested with real sample inputs. Check the output before you send or publish it.
Expert Tip
If a converted date looks impossibly far in the future, you're probably reading a millisecond timestamp as if it were seconds — that's an accidental factor-of-1000 error, and it throws the date thousands of years off, which makes the mistake easy to spot once you know to look for it.
A Unix timestamp is a count of the seconds that have passed since 00:00:00 UTC on 1 January 1970, a moment called the epoch. It contains no time zone, which makes it a convenient way for databases, logs and APIs to store an exact moment. A few anchors help you read them: 0 is the epoch itself, 1704067200 is 00:00:00 UTC on 1 January 2024, 1767225600 is the start of 2026, and a negative number such as -86400 is a date before 1970, in this case 31 December 1969. The Unix Timestamp Converter shows what any of these numbers means in plain language.
There is a single box and a Convert button, and pressing Enter does the same thing. What you type decides the direction.
When you type a date, the browser decides which time zone to use, and the rule is subtle. A date on its own, such as 2024-01-01, is read as midnight UTC. A date with a time but no zone, such as 2024-01-01 12:00 or 2024-01-01T12:00:00, is read in your own local time zone, so the same text gives different timestamps for people in different places. To get an answer that does not depend on your location, add a Z or an explicit offset, as in 2024-01-01T12:00:00Z or 2024-01-01T12:00:00+05:00.
Current timestamps in seconds have ten digits, and JavaScript, Java and many web APIs use milliseconds, which have thirteen. The tool handles both. A sixteen-digit microsecond value or a nineteen-digit nanosecond value from some databases is not recognised: the first shows a date tens of thousands of years away and the second returns an out-of-range message, so divide by 1,000 or 1,000,000 first. That distance is a useful warning sign: a date that looks absurd almost always means a unit mix-up. The automatic rule also has one edge. A millisecond value from before early March 1973 is smaller than 100 billion, so it would be read as seconds.
1700000000 is 22:13:20 UTC on 14 November 2023, a round number people like to mark. 2147483647 is 03:14:07 UTC on 19 January 2038, the largest value that fits in a signed 32-bit integer. One second later, systems that still store time in 32 bits overflow, which is known as the year 2038 problem. This browser tool is not affected, and 2147483648 simply converts to 03:14:08 on the same day.
Timestamps appear in server logs, database columns, API responses, cookies and the expiry claims of login tokens. The JWT Decoder already prints the issued and expiry times of a token as dates, while this tool is for the raw numbers you find elsewhere. To see the same moment on a wall clock in another city, use the Timezone Converter, and to check when a scheduled job fires, use the Cron Parser. The Days Between Dates calculator counts the days between two calendar dates.
Unix time ignores leap seconds, so every day is exactly 86,400 seconds long. The output is always in UTC, so a log line from a local machine needs its offset applied separately. JavaScript dates cover roughly 275,000 years either side of 1970, and a number outside that range returns an out-of-range message. Everything is calculated in your browser.
Explore more in Converters, read the guides and articles, or see how we test our tools.
Convert time between different time zones worldwide.
Best for scheduling meetings across different time zones
Parse and understand cron expressions with human-readable descriptions.
Best for confirming a scheduled job in a server crontab actually runs when you think it does before deploying it
Decode and inspect JSON Web Tokens (JWT) in your browser.
Best for debugging JWT authentication tokens
Calculate the exact number of days, months, and years between any two dates.
Best for counting the days until a holiday, exam or deadline
Validate date strings for correct format, leap years, and logical validity.
Best for validating a user-submitted birthdate in a signup form before saving it