Unix Timestamp Converter Converter
Read epoch timestamps as dates, and dates as timestamps.
Timestamp or date
Breakdown
About the Unix Timestamp Converter converter
A Unix timestamp counts the seconds since 1 January 1970 UTC. It is compact and unambiguous, and completely unreadable, which is why this converter exists.
Paste a number and get every representation you might need. Paste a date instead and get the timestamp back.
Seconds, milliseconds or microseconds?
The unit is inferred from the magnitude. Ten digits is seconds, thirteen is milliseconds, sixteen is microseconds. That covers Unix tooling, JavaScript `Date.now()` and database microsecond precision respectively.
Getting this wrong is the classic bug: interpreting milliseconds as seconds lands you in the year 56,000.
Time zones
UTC is shown in both ISO 8601 and RFC 1123 form. Local time uses your device time zone, so it will differ for a colleague in another region — always share the UTC value when reporting a bug.
The 2038 problem
Systems storing timestamps as a signed 32-bit integer overflow on 19 January 2038. Anything modern uses 64 bits, but the limit still surfaces in old embedded code and legacy database columns.
Frequently asked questions
What formats can I paste as a date?
Anything your browser can parse, which includes ISO 8601, RFC 2822 and most common written forms. ISO 8601 with an explicit offset is the only form that is unambiguous everywhere.
Are negative timestamps supported?
Yes, they represent dates before 1970.
Does it account for leap seconds?
No. Unix time deliberately ignores leap seconds, so a leap second repeats the same timestamp value.