Unix Timestamp Converter
Timestamp → date
Date → timestamp
Why timestamps look like that
Storing a date as text invites trouble: is 03/04/2026 in March or April, and in which timezone? A Unix timestamp sidesteps all of it by counting seconds from one fixed moment in 1970, the same number everywhere on earth. The formatting only happens when a human needs to read it.
Formats you will see
- Seconds — ten digits, the classic Unix form used by most databases and APIs.
- Milliseconds — thirteen digits, what JavaScript's
Date.now()returns. - ISO 8601 —
2026-01-01T00:00:00Z, readable and still unambiguous.
Share this tool with friends
Free to use, no sign-up, works on any phone.
Frequently Asked Questions
The number of seconds since 1 January 1970 at 00:00 UTC. Because it is a plain count with no timezone attached, it is unambiguous everywhere in the world, which is why systems store it.
By length. A ten-digit number is seconds; thirteen digits is milliseconds. This tool detects it for you, so pasting either works.
Almost always daylight saving. The timestamp itself is fixed; what changes is the local offset on that particular date. Switch to UTC to see the underlying value.
Systems that store the timestamp as a signed 32-bit integer run out of room on 19 January 2038 and wrap to a negative number. Anything modern uses 64 bits, but old embedded systems and databases can still be caught by it.
Yes. Timestamps before the epoch are simply negative, and both directions handle them.