Computers often store time as a Unix timestamp, also called epoch time: the number of seconds since midnight UTC on 1 January 1970. It's compact, easy to compare and the same everywhere on Earth, which is why you'll find it in databases, log files, APIs, JWT tokens and spreadsheets exported from apps. The catch is that 1767225600 means nothing to a human. This free Unix timestamp converter translates in both directions. Paste a timestamp and it detects whether it's in seconds, milliseconds, microseconds or nanoseconds from its length, then shows the date and time in UTC, in your own time zone and in any other time zone you pick, along with ISO 8601 and RFC 2822 formats and a relative time like "3 days ago". Going the other way, choose a date and time and a time zone to get the epoch in seconds and milliseconds. At the top, a live clock shows the current timestamp ticking, with a one-click copy. All conversions use your browser's built-in time zone database, so daylight-saving changes are handled automatically. It's also a handy reminder of the Year 2038 problem: signed 32-bit timestamps run out on 19 January 2038. Nothing leaves your device.
Current Unix time
Timestamp → date
Date → timestamp
How to convert
- Paste a timestamp; the unit is detected automatically.
- Pick a time zone to see local time there.
- Or enter a date and time to get its timestamp in that zone.
Handy timestamps
| 0 | 1 Jan 1970 00:00 UTC |
| 1,000,000,000 | 9 Sep 2001 |
| 2,147,483,647 | 19 Jan 2038: 32-bit limit |
FAQ
Seconds or milliseconds?
Unix tools use seconds (10 digits today); JavaScript and Java use milliseconds (13 digits). We detect which from the length.
Does a Unix timestamp have a time zone?
No. It’s always counted from UTC; the time zone only affects how it’s displayed.
What about leap seconds?
Unix time ignores them, so every day is exactly 86,400 seconds.
Is anything sent to a server?
No. It all runs in your browser.
Comments
Post a Comment