Epoch to Date Converter

Convert Unix timestamps to readable dates

Epoch time is compact and reliable for systems, but it is hard to inspect by eye. This page focuses on the timestamp-to-date direction: enter a 10-digit Unix timestamp in seconds or a 13-digit timestamp in milliseconds, choose a timezone, and read the same instant as a normal calendar date.

What the output formats mean

The converter returns several common date formats so you can copy the one your workflow needs.

• ISO 8601 includes the local UTC offset and is the safest format for APIs and logs
• UTC string shows the same instant in Coordinated Universal Time
• Friendly local output is useful for humans checking schedules or debugging events
• Relative time helps confirm whether the timestamp is in the past or future

Seconds vs milliseconds

Most backend languages use Unix seconds, while JavaScript and many browser APIs use milliseconds. The converter detects the unit from the size of the number, which prevents the common mistake of converting a modern timestamp into a date near 1970.

Debugging timestamp inputs

If a converted date looks far too old or far into the future, the timestamp unit is usually the problem. A modern Unix timestamp in seconds has 10 digits, while a modern millisecond timestamp has 13 digits. APIs sometimes label both simply as epoch time, so confirm the unit before copying values into logs, SQL queries, or test fixtures.

• A value such as 1700000000 is seconds and should convert to a date in 2023
• A value such as 1700000000000 is milliseconds and can be passed directly to JavaScript Date
• If a date lands in January 1970, you probably used seconds where milliseconds were expected
• If a date lands tens of thousands of years away, you probably multiplied milliseconds again