The epoch itself
- Input
- 0
- Output
- 1970-01-01T00:00:00.000Z
Zero is the start of the Unix epoch. Seeing it in a database usually means a date field was never set rather than that something happened in 1970.
A Unix timestamp counts the seconds since the start of 1970 in UTC, which makes it unambiguous to store and unreadable to humans. Two things go wrong in practice: a timestamp in seconds and one in milliseconds look alike but are a thousand-fold apart, and a value read in one timezone means a different local moment than the same value read in another. Both are handled explicitly here.
Runs entirely in your browser — nothing you paste is uploaded.
Right now
1787415209
1787415209 seconds · 1787415209490 milliseconds
How to
Enter the number from your log or database. Whether it is in seconds or milliseconds is detected from its magnitude, and can be overridden.
ISO 8601, the UTC string, your local time with its zone, and a plain description like two hours ago are all shown together.
Enter a date and get its timestamp. A date without a time is treated explicitly as local or UTC rather than being guessed.
Copy any representation directly. The current timestamp is always shown, updating each second.
Examples
Zero is the start of the Unix epoch. Seeing it in a database usually means a date field was never set rather than that something happened in 1970.
The largest value a signed 32-bit integer can hold. Systems still storing timestamps that way will overflow at this moment, which is the Year 2038 problem.
Read as seconds this would be a date over fifty thousand years away. Thirteen digits means milliseconds, which JavaScript uses natively while most other languages use seconds.
Why use it
Seconds and milliseconds are distinguished by magnitude, so pasting a JavaScript timestamp into a tool expecting seconds no longer produces a date in the far future.
UTC and your local time are shown together with the zone named, which is what you need to reconcile a log entry with a user's report.
A relative description makes it immediately obvious whether a timestamp is recent, ancient, or wrongly in the future.
Timestamps come from logs and databases. Nothing is uploaded.
Good to know
Summary
FAQ
Discover