Unix Timestamp Converter
Convert between Unix epoch time and human-readable dates
Current Unix time
Timestamp to date
Date to timestamp
Interpreted as your local time (UTC+09:00).
About this tool
This Unix timestamp converter turns epoch time into a readable date and converts any date back into a Unix timestamp. A Unix timestamp is the number of seconds elapsed since 1970-01-01 00:00:00 UTC (the Unix epoch), ignoring leap seconds. It is the time format used by databases, log files, APIs, and most programming languages, so converting it by hand is a daily task for developers. The tool shows both UTC and your local time, supports seconds and milliseconds, and lets you grab the current epoch with one click.
How to use
- 1 To decode a timestamp, choose seconds or milliseconds to match your value.
- 2 Paste the timestamp; the UTC, local, ISO 8601, and RFC 2822 dates appear instantly.
- 3 To encode, type a date as YYYY-MM-DD HH:MM:SS in the second box.
- 4 Read off the epoch in seconds and milliseconds, or press Now to use the current time.
How it works
Unix time counts the seconds since the epoch, 1970-01-01 00:00:00 UTC. A value of 0 is exactly that moment; 1000000000 is 2001-09-09; 1700000000 is 2023-11-14. Multiply by 1000 to get milliseconds, the unit used by JavaScript's Date and many JSON APIs. Because the count is in UTC, the same timestamp shows different wall-clock times depending on your time zone, which is why the tool renders UTC and local side by side. Note the classic Year 2038 problem: a signed 32-bit seconds counter overflows on 2038-01-19, so modern systems store the value in 64 bits.
Frequently asked questions
What is a Unix timestamp?
It is the number of seconds since 1970-01-01 00:00:00 UTC, the moment known as the Unix epoch. It gives every instant a single integer, independent of time zone.
Seconds or milliseconds — which do I have?
Ten digits is usually seconds (good until the year 2286); thirteen digits is milliseconds. JavaScript's Date.now() returns milliseconds, while most Unix tools use seconds.
Why does the local time differ from UTC?
A timestamp is an absolute instant in UTC. Your local time adds your time-zone offset, so the same number can read as a different clock time in different regions.
What is the Year 2038 problem?
Systems that store Unix time as a signed 32-bit integer can only count to 2038-01-19 03:14:07 UTC before overflowing. Using 64-bit storage removes the limit.
Related tools and uses
For time-zone conversions across cities, see the world clock and time-zone tools. To inspect a timestamp's bits, try the number base converter, and for encoding text payloads in APIs see the Base64 and URL encoders.