Unix Timestamp Converter: Epoch to Date and Date to Timestamp
Convert Unix timestamps in seconds, milliseconds, microseconds or nanoseconds to dates in any time zone, and dates back to timestamps, in your browser.
Current time
- Unix time (seconds)
-
– - Unix time (milliseconds)
-
– - UTC (ISO 8601)
-
– - Local time
- –
The clock is paused. The values above show the moment you paused it.
Timestamp to date
Enter a Unix timestamp to see the date and time.
- UTC (ISO 8601)
- Local time
- Selected time zone
- ISO 8601 with offset
- RFC 2822 / HTTP date
- Relative to now
- Day of the week (UTC)
- ISO week (UTC)
- Day of the year (UTC)
- Seconds
- Milliseconds
- Microseconds
- Nanoseconds
Date to timestamp
Accepted: ISO 8601 such as 2026-10-03T09:00:00+09:00, 2026-10-03T00:00:00Z or 2026-10-03 09:00, and RFC 2822 / HTTP dates such as Sat, 03 Oct 2026 00:00:00 GMT. A value without Z or an offset is read in the time zone selected below.
Enter a date and time to see the Unix timestamp.
- Unix time (seconds)
- Unix time (milliseconds)
- UTC (ISO 8601)
- Selected time zone
Batch conversion
Paste timestamps above to convert them all at once.
| Line | Input | Unit | UTC (ISO 8601) | Selected time zone |
|---|
Notes
- Unix time counts the seconds since 1970-01-01 00:00:00 UTC without leap seconds: in Unix time every day has 86,400 seconds. Negative values are moments before 1970.
- Auto-detection is a rule of thumb based on the size of the number (its absolute value): up to 100,000,000,000 (1e11) is read as seconds, up to 1e14 as milliseconds, up to 1e17 as microseconds, and larger values as nanoseconds. Check the unit, especially for dates far from today.
- Time zone offsets and daylight saving rules come from your browser's time zone database. They can differ between browsers and browser versions, especially for historical dates and for future dates in countries that change their rules.
- If a date and time does not exist in the chosen time zone because the clocks were moved forward, the later valid time is used. If it occurs twice because the clocks were moved back, the earlier occurrence is used. A note explains what happened.
- Dates from -271821-04-20 to +275760-09-13 UTC can be converted (±8,640,000,000,000,000 milliseconds, the range of JavaScript dates). Microsecond and nanosecond values are converted exactly; date and time outputs show up to nine decimal places.
- Systems that store Unix time as a signed 32-bit integer can count only up to 2,147,483,647, which is 2038-01-19 03:14:07 UTC. One second later the value overflows. 64-bit values do not have this limit in practice.
- Dates before 1582 are shown in the proleptic Gregorian calendar (the Gregorian rules extended backwards), as in ISO 8601, not in the Julian calendar used at the time.
- All conversions run in your browser. The values you enter are not sent to LeedyBox.
How to use
- To read a timestamp, enter it under "Timestamp to date". The unit is detected from the size of the number; choose the unit yourself if the guess is wrong.
- Choose a time zone to see the same moment there. Type part of a name, such as Seoul or New York, to filter the list.
- To get the timestamp of a date, enter the date and time under "Date to timestamp", select the time zone they belong to, and copy the seconds or milliseconds.
- To convert a string such as 2026-10-03T09:00:00+09:00, switch the input to "ISO 8601 text" and paste it.
- To convert many values, paste one timestamp per line under "Batch conversion" and copy the table as CSV.
Frequently asked questions
Is the data I enter sent anywhere?
No. The conversion runs in your browser with JavaScript, and the values you enter are not uploaded to LeedyBox.
How can I tell whether a timestamp is in seconds or milliseconds?
For dates between 2001 and 2286, Unix time has 10 digits in seconds, 13 in milliseconds, 16 in microseconds and 19 in nanoseconds. The tool guesses the unit from the size of the number and says which unit it used; select another unit if the guess is wrong.
Why does the same timestamp show a different date in another time zone?
A Unix timestamp is one moment in time and does not depend on a time zone. The calendar date and clock time at that moment do, so near midnight the date can differ by a day between zones.
Which dates can be converted, and how accurate are the time zones?
Any moment from -271821-04-20 to +275760-09-13 UTC, the range of JavaScript dates. Offsets and daylight saving rules come from your browser's time zone data, which may not match the rules that applied long ago or that will apply in the future.
What happens with times that are skipped or repeated when the clocks change?
A skipped time, such as 02:30 on the night the clocks go forward, is moved to the later valid time. A repeated time, when the clocks go back, uses the earlier occurrence, and the note also shows the timestamp of the later one.