Unix Time Converter

Convert Unix Timestamps (sec/ms) to Human Readable Dates.

Decode an epoch number into a real date

Unix time counts the seconds since 00:00:00 UTC on 1 January 1970. It is compact and easy for machines to compare, but a value like 1704067200 tells a person nothing at a glance. Paste that number here and the tool shows what moment it represents, in three forms, so you can read logs, database rows and API responses without a calculator.

Converting a timestamp

Put the number in the Input Data box. Sample loads 1704067200.
Click Process Now.
Read the table: UTC Time, Local Time and ISO 8601.
Choose Copy to copy the text, or Download for a result.txt file. Clear empties the box for the next value.

Seconds or milliseconds, decided for you

There is no unit selector. The tool assumes any number below 10,000,000,000 is in seconds and multiplies it by 1000, while larger numbers are treated as milliseconds. A typical 10-digit value therefore reads as seconds and a 13-digit value as milliseconds. In practice this covers seconds through the year 2286, and milliseconds from late April 1970 onward.

The three outputs serve different needs. UTC is a neutral reference to compare between servers. Local Time uses your own device's time zone and includes its zone name, which helps when the event happened on your machine. ISO 8601, ending in Z, is the format most APIs and JSON payloads use.

Typical situations

Reading the created_at or exp value inside a token or API reply.
Working out when a cron job or log line actually fired.
Checking whether a cache entry has expired.
Sorting out a support ticket where two systems show the same event at different times.

Watch for these edge cases

Only whole-number input is read: the value is parsed as an integer, so anything after a decimal point is dropped. A 16-digit microsecond or 19-digit nanosecond timestamp is not recognised and will show a date far in the future; trim it to seconds or milliseconds first. A very small millisecond value from before late April 1970 would be misread as seconds. Negative numbers do work and give dates before 1970. Non-numeric text returns an error message instead of a date. If the box is empty when you click Process Now, you are prompted to enter a timestamp, so copy the whole number without spaces or commas.

Related Tools

Related Tools

Frequently Asked Questions

How does it know if my number is in seconds or milliseconds?

It uses a size cutoff. Values below 10,000,000,000 are treated as seconds and converted, and larger ones are read as milliseconds. So 1704067200 is seconds and 1704067200000 is milliseconds, with no setting required.

What time zone is the Local Time row in?

Your device's own zone, as reported by your browser. The row includes the offset and zone name. If you need a specific zone, use the UTC row or ISO 8601 row, which are the same for everyone.

Why does my long timestamp show a date thousands of years away?

Numbers with 16 or 19 digits are usually microseconds or nanoseconds, which this tool does not detect. It treats them as milliseconds and the result is a far-future date. Divide the value down to seconds or milliseconds first.

Does it accept decimals such as 1704067200.75?

The number is parsed as a whole integer, so the fractional part is ignored and you get the date for 1704067200. For sub-second precision, enter the value in milliseconds instead, for example 1704067200750.

Can I convert a date back to a timestamp here?

Not on this page. It only goes from timestamp to date. For the reverse direction use the Timestamp Converter, where you type a date and receive seconds and milliseconds.