Epoch Converter (Unix Timestamp)
Convert Unix seconds or milliseconds to readable dates and back. Your work stays on this device whenever possible.
How to use Epoch Converter (Unix Timestamp)
- Watch the "CURRENT LIVE UNIX TIMESTAMP" box at the top; press "Pause" to freeze it or "Copy Now" to copy the current seconds value.
- Enter a value in "Timestamp or Date String", which starts filled with the current second count.
- Set "Input Format" to Unix Seconds (10 digits), Milliseconds (13), Microseconds (16), Nanoseconds (19) or "Human Date String (YYYY-MM-DD HH:mm:ss)"; the unit is never guessed.
- Press "Convert Timestamp" for the UTC ISO 8601, local, RFC 2822 and relative lines, plus the "Global Timezones Matrix" of nine cities.
- Read the epoch block at the bottom for the same instant in seconds, milliseconds, microseconds and nanoseconds.
Worked example
Choose Unix Seconds and enter 1700000000. The result shows UTC ISO 8601 as 2023-11-14T22:13:20.000Z and RFC 2822 as Tue, 14 Nov 2023 22:13:20 GMT. In the matrix, the Karachi row reads Wednesday, November 15, 2023 at 3:13:20 AM GMT+5. The epoch block lists Milliseconds (ms) 1700000000000, and the relative line depends on today's date.
When to use this tool
- Turning a database created_at integer into a readable time while debugging a report.
- Working out what hour a scheduled job stamped in UTC means for a teammate in Karachi.
- Generating the current epoch value to paste into a test payload.
Important limitations
Timestamps contain no time zone and may use seconds or milliseconds. Leap seconds are not represented.
Frequently asked questions
Why did my 13-digit number land tens of thousands of years away?
Because the unit is chosen by you. A millisecond value read as seconds jumps far into the future. Switch "Input Format" to Milliseconds. Roughly, 10 digits means seconds, 13 milliseconds, 16 microseconds and 19 nanoseconds.
Is a typed date read as UTC or local time?
It goes through the browser's date parser. A date-only value such as 2024-01-15 is read as UTC, but "2024-01-15 10:30:00" without a Z or offset is read in your local zone. Both readings appear in the output so you can compare.
Does batch mode work?
Not properly. The checkbox expects one value per line, but the value field is a single-line input, so pasted line breaks are stripped and the numbers run together. Convert values one at a time for now.
How exact are the microsecond and nanosecond lines?
Input is turned into a JavaScript date with millisecond precision, so anything finer is discarded. Those two output lines are simply milliseconds multiplied by a thousand or a million and can lose exactness beyond 2^53.
Are leap seconds and other time zones covered?
Unix time ignores leap seconds, so every day counts as 86,400 seconds. The matrix lists UTC, New York, London, Paris, Dubai, Karachi, India, Tokyo and Sydney, following daylight saving through your browser's zone database.