Lotamyst / Everyday Tools / Epoch & Unix Timestamp Converter
Epoch & Unix Timestamp Converter
Timestamp to date, date to timestamp — with the unit detected for you. Everything runs in your browser.
The current Unix time—
—seconds
—milliseconds
—
Timestamp → date
Date → timestamp
How the unit is detected
The same instant is written four different ways depending on which system produced it, and they differ only by digit count. Auto-detect uses these ranges; if your number falls outside them, pick the unit yourself.
| Digits | Unit | Where it comes from |
|---|---|---|
| 10 | seconds | Unix time(), PHP, most databases, JWT exp |
| 13 | milliseconds | JavaScript Date.now(), Java, Kafka |
| 16 | microseconds | Python time.time_ns()/1000, Postgres internals |
| 19 | nanoseconds | Go UnixNano(), Prometheus, Rust |
Negative timestamps are valid and mean a date before 1970 — the tool handles them.
About this tool
A Unix timestamp counts seconds since 00:00:00 UTC on 1 January 1970. It carries no time zone and no daylight-saving rules, which is exactly why logs, databases and APIs store it: one number, one instant, no ambiguity.
The ambiguity arrives when you render it. The UTC line below is identical for everyone on Earth; the local line applies your machine's time zone and will read differently from a colleague's screen. When you are comparing a log line to a bug report, compare the UTC values.
Nothing here talks to a server — the conversion is a few lines of arithmetic and your browser's own time-zone database.
FAQ
What is a Unix timestamp?
The number of seconds elapsed since 00:00:00 UTC on 1 January 1970, known as the Unix epoch. It ignores time zones and daylight saving entirely, which is why it's the standard way to store an instant in databases, logs and APIs.
Is my timestamp in seconds or milliseconds?
Count the digits. A present-day timestamp in seconds has 10 digits, milliseconds has 13, microseconds 16 and nanoseconds 19. This tool detects the unit from the digit count and tells you which one it used — and you can override it with the dropdown.
Why does the same timestamp show a different clock time on another machine?
A timestamp is a single instant, not a wall-clock time. Rendering it as a date applies a time zone, so the same number reads as different local times around the world. The UTC line is the one that's the same everywhere.
What is the year 2038 problem?
Systems that store the timestamp in a signed 32-bit integer overflow at 2147483647 seconds — 03:14:07 UTC on 19 January 2038. Anything using 64-bit time, including JavaScript, is unaffected.
Does it handle dates before 1970?
Yes. A negative timestamp counts backwards from the epoch, so -86400 is 31 December 1969.