| ISO 8601 | — | |
| UTC | — | |
| Your timezone | — | |
| Relative | — | |
| Unix · seconds | — | |
| Unix · milliseconds | — |
About this tool
A Unix timestamp counts seconds since January 1, 1970 UTC. It's how most systems store time internally — compact, timezone-free and easy to compare.
Use it to read raw timestamps from logs, databases and API payloads without doing epoch math in your head.
Milliseconds vs seconds: a 13-digit value is almost certainly milliseconds.
Frequently asked questions
How do I convert epoch time to a date?
Paste the epoch value above and it is converted instantly to a readable date in UTC, your local timezone and relative time. To go the other way, enter a date and copy the Unix timestamp back. Everything runs locally in your browser.
What is a Unix timestamp?
A Unix timestamp is the number of seconds elapsed since January 1, 1970 at 00:00 UTC (the "epoch"). It is a compact, timezone-free way to store an exact instant, which is why logs, databases and APIs use it. A 13-digit value is milliseconds, not seconds.
Seconds or milliseconds?
Unix time is classically seconds; JavaScript's Date.now() returns milliseconds. The tool detects the unit from digit count and lets you override it.
Is the timestamp timezone-dependent?
No — a timestamp is an absolute instant. Only its human-readable rendering depends on a timezone.
What is the year-2038 problem?
Signed 32-bit timestamps overflow on Jan 19, 2038. Modern 64-bit systems are unaffected.