Unix timestamp converter

Paste a Unix timestamp to see the date it stands for, in UTC and in your local time, or pick a date to get its timestamp. Seconds, milliseconds, microseconds and nanoseconds are detected.

  • Free
  • No sign-up
  • Runs in your browser
unix-timestamp-converter

Fill in the values above to see the result.

100% private — the calculation is done in your browser and nothing is sent to any server.

How it works

Paste a timestamp or pick a date

From a log, a database, an API or your code.

Check the unit

It is detected from the length, or you can set it.

Read the conversions

UTC, ISO 8601, your local time, RFC 2822 and how long ago it was.

What date is 1700000000?

A Unix timestamp is the number of seconds that have passed since midnight UTC on 1 January 1970, known as the epoch. It is how a huge amount of software stores and exchanges moments in time: databases, log files, APIs, tokens, file systems and programming languages. It is compact and unambiguous, but impossible for a person to read. This converter translates it into a date you can understand, and back.

Seconds, milliseconds and beyond

The classic timestamp counts seconds and has 10 digits today, but many systems count in milliseconds, which gives 13 digits, and some in microseconds or nanoseconds, with 16 and 19 digits. JavaScript and Java use milliseconds, while most databases and shell tools use seconds. Getting the unit wrong gives a date in 1970 or thousands of years in the future, so the tool guesses the unit from the number of digits and you can override it. It always shows both the seconds and the milliseconds for the moment.

What you get from a timestamp

  • UTC in ISO 8601, the format used by APIs, such as 2026-09-21T10:30:00Z.
  • Local time in your own time zone, with the zone named.
  • RFC 2822, the format used in email and HTTP headers.
  • A relative description such as "3 days ago" or "in 2 hours".

From a date to a timestamp

Switch the mode, pick a date and time, and say whether it is in your local time zone or in UTC. The tool returns the timestamp in seconds and milliseconds, ready to paste into a query or a test. The distinction between local time and UTC matters: the same wall-clock time is a different timestamp in different zones.

The year 2038 and negative values

Timestamps before 1970 are negative numbers and work fine. Systems that store the value in a 32-bit signed integer will run out on 19 January 2038, the "year 2038 problem". This tool uses 64-bit arithmetic and is not affected, and it can show dates well beyond that.

What it does not do

Timestamps carry no time zone and no leap seconds, and this converter follows the same convention, in which every day has exactly 86,400 seconds. Dates before the adoption of the Gregorian calendar use the same proleptic calendar as your browser. For other date formats, see the ISO 8601 converter.

Frequently asked questions

What is a Unix timestamp?
The number of seconds since 1 January 1970 at 00:00:00 UTC. It is a compact way for software to represent a moment in time.
How do I convert a Unix timestamp to a date?
Paste it into the box. The tool shows the date in UTC, in your local time and in other standard formats.
How do I know if my timestamp is in seconds or milliseconds?
By its length: 10 digits is seconds, 13 is milliseconds. The tool detects it, and you can set the unit yourself.
How do I get the current timestamp?
Press "Use the current time" and the present moment is loaded.
What is the year 2038 problem?
Systems that keep the timestamp in a 32-bit signed integer overflow on 19 January 2038. This tool is not limited that way.
Is my data sent anywhere?
No. The conversion is done in your browser.