- 100% free
- No sign-up
- Runs in your browser
Unix Timestamp Converter
Convert epoch timestamps to readable dates and back. Seconds, milliseconds, microseconds and nanoseconds are detected automatically.
Current timestamp (seconds)
…
Current timestamp (milliseconds)
…
Timestamp → date
Date → timestamp
Interpreted in your local time zone.
About Timestamp Converter
Unix Timestamp Converter turns an epoch timestamp into a readable date — in UTC, your local time and ISO 8601 — and turns any date and time back into a timestamp. It also shows the current timestamp, updating every second.
A Unix timestamp counts the time elapsed since 00:00:00 UTC on 1 January 1970. Databases, APIs, log files and analytics exports store dates this way because a single number is compact, unambiguous and easy to sort and compare. The catch is that 1735689600 means nothing at a glance — this tool makes it readable.
Different systems use different units, which is a constant source of bugs. Unix tools and many APIs use seconds (10 digits for current dates), JavaScript and Java use milliseconds (13 digits), and some databases and Go use microseconds or nanoseconds. The converter detects the unit from the number of digits and lets you override it, so a millisecond value is never read as a date fifty thousand years away.
Going the other way is useful when writing a query or testing an API: pick a date and time and copy the timestamp in seconds or milliseconds. Date input is read in your local time zone, and the UTC equivalent is always shown so you can tell exactly which instant you mean.
How to convert a Unix timestamp
- Paste a timestamp into the Timestamp → date box.
- Leave the unit on Auto-detect, or choose seconds, milliseconds, microseconds or nanoseconds.
- Read the date in UTC, your local time and ISO 8601, and copy whichever you need.
- To go the other way, pick a date and time under Date → timestamp.
- Copy the result in seconds or milliseconds.
Tips & common problems
Count the digits
For present-day dates, 10 digits is seconds, 13 milliseconds, 16 microseconds and 19 nanoseconds. A date in 1970 or the far future usually means the unit is wrong.
Timestamps have no time zone
The number identifies one instant everywhere in the world. Only the readable form changes by zone — which is why UTC and local time are shown side by side.
Prefer ISO 8601 in text
When writing a date into JSON, logs or a spreadsheet, the ISO format (2026-01-01T00:00:00.000Z) is both readable and sortable.
Frequently asked questions
What is a Unix timestamp?
The number of seconds since 1 January 1970 at 00:00:00 UTC, known as the Unix epoch. It is the standard way computers store points in time.
Is the timestamp in seconds or milliseconds?
It depends on the system. Count the digits — 10 for seconds, 13 for milliseconds for current dates. The converter detects this automatically.
Why does my converted date show 1970?
The value was probably read in the wrong unit — for example milliseconds treated as microseconds. Choose the correct unit from the menu.
What time zone is used?
Timestamps are always UTC. Results are shown in UTC and in your device’s local time zone.
What is the year 2038 problem?
Systems that store seconds in a signed 32-bit integer overflow on 19 January 2038. Modern systems use 64-bit values, which this converter supports.