Unix Timestamp Converter

How to Use

To decode a timestamp, paste the number into 'Timestamp → date' — the tool detects seconds vs milliseconds and shows all three formats. To go the other way, pick a date and time in 'Date → timestamp' and copy the Unix seconds or milliseconds. The current epoch time updates live at the top.

Why This Tool Is Useful

Unix time — the number of seconds since January 1, 1970 UTC — is how computers store time almost everywhere: in databases, logs, APIs, and JWTs. But a number like 1716239022 means nothing to a human. Developers constantly need to translate between epoch values and real dates while debugging. This converter does it instantly, handles both seconds and milliseconds, and makes the UTC-vs-local distinction explicit so you don't misread a log.

Seconds vs Milliseconds

Unix timestamps come in two common resolutions. Classic Unix time counts whole seconds (10 digits for current dates). JavaScript's Date.now() and many APIs use milliseconds (13 digits). This tool counts the digits to guess the unit: 13 or more digits is treated as milliseconds, fewer as seconds. If a value looks wrong, check whether it should be multiplied or divided by 1000.

UTC vs Local Time

A timestamp itself has no time zone — it's an absolute instant. The confusion comes when you display it. This tool shows both the UTC form (what's usually stored) and your local time (what your machine's zone produces), so you can match whichever your system uses. ISO 8601 is shown too, since it's the safest format to store and share.

The Year 2038 Problem

Systems that store Unix time in a signed 32-bit integer can only count up to 03:14:07 UTC on 19 January 2038, after which the value overflows. Modern systems use 64-bit integers and are unaffected for billions of years, but the '2038 problem' is why you'll still see migrations away from 32-bit time fields.

Common Intervals in Seconds