Unix Timestamp Converter
Live epoch clock with two-way conversion between Unix time and readable UTC/local dates.
Convert Unix Timestamps to Readable Dates and Back
Unix time counts the seconds elapsed since 00:00:00 UTC on 1 January 1970, ignoring leap seconds. Because it is a single integer with no timezone attached, it is the standard way to store and transmit an instant in time across databases, APIs, log files and JWT expiry claims — and it is completely unreadable to a human being.
This converter runs both directions with a live epoch clock ticking at the top. Paste a timestamp in seconds or milliseconds and see it rendered in UTC, your local timezone, ISO 8601 and RFC 2822 — or pick a date and time and get the integer your API expects.
Key features
- Live epoch clock — the current Unix timestamp, updating every second, with a one-click copy.
- Automatic unit detection — recognises seconds, milliseconds and microseconds by magnitude.
- Four output formats — UTC, your local timezone, ISO 8601 and RFC 2822.
- Reverse conversion — pick any date and time and get the corresponding epoch value.
- Relative time — see how long ago, or how far ahead, a timestamp falls.
This tool runs entirely inside your browser using native Web APIs. Your files and text are never uploaded to a server, never logged and never shared with third parties.
How to use: Unix Timestamp Converter
- Read the live clock
The current Unix timestamp ticks at the top of the tool. Click it to copy the current value. - Paste a timestamp to decode
Enter a value in seconds or milliseconds — the unit is detected automatically from its magnitude. - Compare the formats
UTC, local time, ISO 8601 and RFC 2822 are shown together, along with how long ago the instant was. - Convert a date back to epoch
Use the date and time picker in the reverse panel to produce the integer your API or database expects.
Technical specifications
| Processing location | Entirely in your browser — no server round trip |
|---|---|
| Data uploaded | None. Files and text never leave your device |
| Price | Free — no account, no trial, no usage cap |
| Category | Security |
| Works offline | Yes, once the page has loaded |
| Browser support | Chrome 90+, Edge 90+, Firefox 90+, Safari 15+ |
| Interface languages | English, 中文, हिन्दी, Español, العربية |
Frequently asked questions
Is my timestamp in seconds or milliseconds?
Judge it by length. A current timestamp in seconds has 10 digits; in milliseconds it has 13. JavaScript’s Date.now() returns milliseconds, while most Unix tools, databases and APIs use seconds — mixing them up produces dates in 1970 or in the year 50,000.
What is the year 2038 problem?
A signed 32-bit integer holding seconds overflows on 19 January 2038, wrapping to a negative number and producing dates in 1901. Any system still storing time in a 32-bit signed field is affected; 64-bit storage pushes the limit roughly 292 billion years out.
Does Unix time account for leap seconds?
No. Unix time assumes every day has exactly 86,400 seconds, so it does not represent leap seconds at all. This keeps arithmetic simple at the cost of drifting slightly from true astronomical time.
Why does my timestamp show a different time than expected?
Almost always a timezone mismatch. A Unix timestamp is always UTC; your local rendering shifts it by your offset. Check whether the system you are comparing against displays UTC or local time before assuming there is a bug.