Unix Timestamp Converter
Convert between Unix timestamps, ISO 8601, UTC, and your local time — in both seconds and milliseconds. Runs entirely in your browser.
Paste a 10-digit (seconds) or 13-digit (milliseconds) Unix timestamp, or any ISO 8601 date string.
—
Current Unix time (milliseconds)—
About this tool
Unix Timestamp Converter
This converter translates between Unix timestamps and human-readable dates. A Unix timestamp counts the seconds (or milliseconds) since 1970-01-01 00:00:00 UTC — the convention most APIs and databases use to store a moment in time.
Paste a 10-digit seconds timestamp, a 13-digit milliseconds timestamp, or any ISO 8601 date string, and get the equivalent in every format at once: milliseconds, seconds, ISO 8601 UTC, local time, and a readable form.
Everything runs locally in your browser. There is no server, so nothing you paste is transmitted, and the tool works fully offline.
Where this earns its keep over a search-box conversion: log analysis. Incident timelines are a pile of timestamps in mixed formats — one service logs in seconds, its dependency in milliseconds, a third in ISO with a timezone offset, and correlating them by hand across UTC and local time is where reconstruction errors come from. Paste each value and read them all in one canonical UTC form; the live 'now' panel anchors your math when you're subtracting times in your head. There's a worked example of exactly this workflow in the incident-timeline post linked below.
Seconds or milliseconds? Count the digits. Today's Unix time in seconds has 10 digits (until November 2286); in milliseconds it has 13. JavaScript's Date.now() returns milliseconds, while most Unix tools, JWT claims such as exp and iat, and many APIs use seconds, so mixing the two is a classic bug: a seconds value read as milliseconds lands in January 1970, and a milliseconds value read as seconds lands tens of thousands of years in the future. This converter treats any whole number of 12 or more digits (an absolute value of 100,000,000,000 or higher) as milliseconds and anything smaller as seconds. It does not detect microsecond (16-digit) or nanosecond (19-digit) values; divide those by 1,000 or 1,000,000 first.
When to use it
Decode a timestamp from an API response
Paste the value an API returned and read it as a human-readable local date instead of a number.
Get a timestamp for a query or script
Type or paste a date and copy the seconds or milliseconds value to use in a filter, query parameter, or script.
Check the current Unix time
The live 'now' panel shows the current timestamp in seconds, updating every second.
Questions
What is a Unix timestamp?
It's a number counting seconds (or milliseconds) since January 1, 1970 00:00:00 UTC. 10 digits means seconds; 13 digits means milliseconds.
Are my values sent to a server?
No. All conversion happens locally in your browser. Nothing is uploaded, and the tool works offline.
Does it handle milliseconds?
Yes. A 13-digit input is interpreted as milliseconds, and the converter outputs both the seconds and milliseconds forms of any date.
How can I tell if a Unix timestamp is in seconds or milliseconds?
Count the digits. A current timestamp in seconds has 10 digits (for example 1788000000); in milliseconds it has 13 (1788000000000). This converter reads a whole number of 100,000,000,000 or more as milliseconds and anything smaller as seconds. If your value has 16 digits it is probably microseconds, and with 19 it is probably nanoseconds. Divide by 1,000 or 1,000,000 to get milliseconds before pasting.
What is the current Unix timestamp?
The live panel beside the input shows the current Unix time in both seconds and milliseconds, updating every second. It reads your device's clock, so it is only as accurate as that clock.
What date formats can I paste?
Any value JavaScript's Date can parse — including ISO 8601 strings like 2024-04-20T06:00:00Z, plus numeric Unix timestamps in seconds or milliseconds.
Is a Unix timestamp affected by time zones?
No — that's the point of the format. A timestamp is an absolute count of seconds since the epoch in UTC, so 1788000000 is the same instant everywhere on Earth. Time zones only appear when you render that instant as a local date string, which is why a timestamp pasted on two machines in different zones shows the same number but a different 'local time' readout.
How do I convert seconds to date (epoch time)?
Unix epoch time counts seconds since 1970-01-01 00:00:00 UTC. Paste a 10-digit value like 1788000000 and this converter renders the exact date and time in UTC and your local zone — the 'seconds to date' direction an epoch converter performs. The reverse works too: paste an ISO 8601 date string like 2026-09-01T12:00:00Z and read the epoch seconds and milliseconds off the same results panel. To get days between two dates, convert both to epoch seconds and divide the difference by 86,400 — the live 'now' panel anchors the subtraction.
What happens at the year 2038 problem?
Systems storing Unix time as a signed 32-bit integer overflow on 2038-01-19. Anything modern — JavaScript's Number, 64-bit databases, current APIs — counts well past that. If you're maintaining legacy C or embedded code that stores time_t as 32 bits, it's a real migration item; for web work it's a non-issue.
Related resources