Unix Epoch Converter
Timestamps to dates and back, in seconds or milliseconds.
Runs entirely in your browser
Loading the tool…
Current Unix time: …
| Relative | — |
|---|---|
| Your local time | — |
| UTC | — |
| ISO 8601 | — |
| RFC 2822 | — |
| Readable | — |
| Seconds | — |
| Milliseconds | — |
| Day of year | — |
| ISO week | — |
| Leap year | — |
Unix time counts the seconds since 1 January 1970 UTC, ignoring leap seconds.
It is the timestamp in your database rows, your log lines and your JWT
exp claims. Ten digits means seconds; thirteen means milliseconds, and
this converter detects which you pasted.
Dates come back in UTC, in your local offset, as ISO 8601 and RFC 2822, plus a relative phrase like "3 days ago", which is usually the one that answers the question you actually had.
How to use it
- Paste a timestamp to see the date, or a date to get the timestamp.
- Both directions convert as you type; the current time is shown live.
- Copy whichever format you need.
Questions
Seconds or milliseconds: which do I have?
Ten digits is seconds (the Unix convention); thirteen is milliseconds (the JavaScript convention, from Date.now()). This page auto-detects, but check the returned year looks plausible.
What is the Year 2038 problem?
A signed 32-bit timestamp overflows on 19 January 2038. Anything storing time in a 32-bit int breaks then. 64-bit timestamps push the limit past the lifetime of the sun.
Why does my local time differ from UTC by an odd amount?
Not every zone is a whole hour from UTC. India is +5:30, Nepal +5:45, Chatham Island +12:45. The local row uses your device's current offset, daylight saving included.
Your data stays on your device
Everything above runs inside your browser as WebAssembly compiled from Rust. Nothing you type is uploaded, logged or stored on a server. There is no server. You can load this page once, go offline, and it still works.