Unix Timestamp Converter
Convert epoch timestamps to readable dates and back. The unit is detected for you, so seconds and milliseconds never get mixed up.
Read as Unix seconds
Current Unix time
—
1700000000
1700000000000
2023-11-14T22:13:20.000Z
2023-11-14 22:13:20 UTC
—
Tuesday
318
What the Unix Timestamp Converter does
- Converts Unix timestamps to readable dates and back, in both directions.
- Detects automatically whether you pasted seconds, milliseconds or microseconds, and tells you which it assumed.
- Shows ISO 8601, UTC, your local time, day of week and day of year together.
- Runs a live clock of the current Unix time.
What it doesn't do
- It doesn't convert between arbitrary named time zones — it shows UTC and your own local time.
- It doesn't handle leap seconds, which Unix time ignores by definition.
- It doesn't parse every possible date format; unusual ones may need rewriting as ISO 8601.
Frequently asked questions
Is my timestamp in seconds or milliseconds?
Count the digits. Ten digits is seconds and thirteen is milliseconds for any date in the current era. Mixing them up is the classic bug — a value in seconds read as milliseconds lands in January 1970. This tool states which unit it assumed so you can catch the mistake.
What is the year 2038 problem?
Systems storing Unix time in a signed 32-bit integer overflow on 19 January 2038, wrapping to a negative number and jumping to 1901. Anything modern uses 64-bit timestamps, but embedded and legacy systems can still be affected.
Why does the date differ from what my database shows?
Nearly always a time zone difference. Unix timestamps have no time zone — they're an absolute count of seconds since 1 January 1970 UTC. A database displaying local time will show a different wall-clock reading for the same instant.