Unix Timestamp Converter
Convert Unix timestamps (epoch time) to human-readable dates and back, instantly in your browser. Distinguish seconds from milliseconds, set an expiry timestamp for a token or cache entry, or compare log timestamps across time zones with no data leaving your device.
Usage examples
Checking a timestamp from an API response
Quickly see what actual date and time a Unix timestamp in a server log or API response corresponds to.
Generating a timestamp for testing
Use the 'Use current time' button to instantly get the timestamp for right now, without typing a date.
Not mixing up seconds and milliseconds
Since some systems use seconds and others milliseconds, switch the unit to compare how the same value is interpreted either way.
Setting an expiry timestamp for a cache or token
Start from the current time, then do the math for how far in the future an expiry should be (like now plus 3600 seconds for a 1-hour token), and verify the resulting timestamp converts back to the date you expect.
Comparing two log timestamps across time zones
Convert two Unix timestamps from logs collected in different regions to UTC, so you can tell which event actually happened first regardless of each server's local clock.
Quick reference
Notable timestamps
| Seconds | Milliseconds | UTC |
|---|---|---|
| -2147483648 | -2147483648000 | 1901-12-13 20:45:52 UTC |
| -1 | -1000 | 1969-12-31 23:59:59 UTC |
| 0 | 0 | 1970-01-01 00:00:00 UTC |
| 86400 | 86400000 | 1970-01-02 00:00:00 UTC |
| 1000000000 | 1000000000000 | 2001-09-09 01:46:40 UTC |
| 1234567890 | 1234567890000 | 2009-02-13 23:31:30 UTC |
| 1500000000 | 1500000000000 | 2017-07-14 02:40:00 UTC |
| 1700000000 | 1700000000000 | 2023-11-14 22:13:20 UTC |
| 2000000000 | 2000000000000 | 2033-05-18 03:33:20 UTC |
| 2147483647 | 2147483647000 | 2038-01-19 03:14:07 UTC |
| 4294967295 | 4294967295000 | 2106-02-07 06:28:15 UTC |
January 1, 00:00:00 UTC
| Seconds | Milliseconds | UTC |
|---|---|---|
| 315532800 | 315532800000 | 1980-01-01 00:00:00 UTC |
| 631152000 | 631152000000 | 1990-01-01 00:00:00 UTC |
| 946684800 | 946684800000 | 2000-01-01 00:00:00 UTC |
| 1262304000 | 1262304000000 | 2010-01-01 00:00:00 UTC |
| 1577836800 | 1577836800000 | 2020-01-01 00:00:00 UTC |
| 1609459200 | 1609459200000 | 2021-01-01 00:00:00 UTC |
| 1640995200 | 1640995200000 | 2022-01-01 00:00:00 UTC |
| 1672531200 | 1672531200000 | 2023-01-01 00:00:00 UTC |
| 1704067200 | 1704067200000 | 2024-01-01 00:00:00 UTC |
| 1735689600 | 1735689600000 | 2025-01-01 00:00:00 UTC |
| 1767225600 | 1767225600000 | 2026-01-01 00:00:00 UTC |
| 1798761600 | 1798761600000 | 2027-01-01 00:00:00 UTC |
| 1830297600 | 1830297600000 | 2028-01-01 00:00:00 UTC |
| 1861920000 | 1861920000000 | 2029-01-01 00:00:00 UTC |
| 1893456000 | 1893456000000 | 2030-01-01 00:00:00 UTC |
| 2145916800 | 2145916800000 | 2038-01-01 00:00:00 UTC |
Frequently asked questions
Is what I enter sent to a server?
No. All conversion happens entirely in your browser, and what you enter is never sent to a server.
Does it support negative timestamps?
Yes. Negative timestamps, which represent dates before January 1, 1970, are calculated correctly too.
How do I know if a value is in seconds or milliseconds?
It isn't auto-detected — choose the unit yourself using the tabs above. As a rule of thumb, a 10-digit number is usually seconds and a 13-digit number is usually milliseconds.
How is my local time zone determined?
It's shown using whatever time zone your current browser/device is set to, with no extra configuration needed.
Why is Unix time measured from January 1, 1970?
That date, known as the Unix epoch, was chosen somewhat arbitrarily by early Unix developers in the early 1970s as a convenient, recent reference point. It has since become the universal standard reference point across nearly all computing systems.
Will this tool still work correctly after the year 2038?
Yes. The so-called 'Year 2038 problem' only affects systems that store Unix time in a signed 32-bit integer, which overflows in January 2038. This tool performs its calculations using JavaScript's native number type, which comfortably handles timestamps far beyond that date.
Does this tool account for leap seconds?
No, and neither does the Unix timestamp standard itself. Unix time assumes every day has exactly 86,400 seconds and simply ignores the leap seconds occasionally added to UTC, which is why it's sometimes described as 'leap second smeared' rather than a perfectly accurate count of elapsed seconds.