Unix Timestamp Converter – Epoch Time to Date and Back
About Timestamp Converter
Paste a Unix timestamp to see it as a readable date, or pick a date to get its timestamp. Works with both seconds and milliseconds, and shows the result in local time, UTC and ISO 8601.
A Unix timestamp counts the seconds since 1 January 1970 UTC. It is the standard way computers store an instant, because it is a single number with no timezone or formatting attached — but that also makes it unreadable to humans, which is where this converter comes in.
The most common source of confusion is seconds versus milliseconds. JavaScript works in milliseconds while most databases and APIs use seconds, so a timestamp interpreted with the wrong unit lands you in 1970 or in the year 56000. This tool handles both explicitly rather than guessing.
What you can use it for
- Turn a timestamp from a log file or database row into a readable date.
- Get the current epoch time for a test fixture or an API call.
- Convert a date into a timestamp for a query filter.
- Check whether a timestamp is in seconds or milliseconds.
- Compare a UTC timestamp against your own local time.
How it works, step by step
- 1
Choose a direction
Timestamp to date, or date to timestamp.
- 2
Choose seconds or milliseconds
Pick the unit your timestamp uses — this is the most common source of wrong results.
- 3
Enter your value
Paste the timestamp, or pick a date and time.
- 4
Read the output
The result is shown in local time, UTC and ISO 8601 format together.
Frequently asked questions
What is a Unix timestamp?
The number of seconds elapsed since 1 January 1970 at 00:00 UTC, known as the Unix epoch. It represents an exact instant with no timezone attached.
Is my timestamp in seconds or milliseconds?
A 10-digit number is almost certainly seconds; a 13-digit number is milliseconds. Reading one as the other is the usual cause of a date landing in 1970 or thousands of years in the future.
Why does the local time differ from UTC?
The timestamp itself is timezone-free. Local time applies your device's timezone and daylight saving offset, so the two readings describe the same instant differently.
What is ISO 8601?
A standard text format for dates and times, like 2026-09-05T14:30:00Z. It sorts correctly as plain text and is unambiguous internationally, which is why APIs prefer it.
What is the year 2038 problem?
Systems storing timestamps in a signed 32-bit integer overflow in January 2038. Modern systems use 64-bit values and are unaffected, but old data and embedded systems can still hit it.