Unix Timestamp Converter — ISO 8601, UTC, Local
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
|---|---|---|---|---|---|---|
31 | 1 | 2 | 3 | 4 | 5 | 6 |
7 | 8 | 9 | 10 | 11 | 12 | 13 |
14 | 15 | 16 | 17 | 18 | 19 | 20 |
21 | 22 | 23 | 24 | 25 | 26 | 27 |
28 | 29 | 30 | 1 | 2 | 3 | 4 |
How to Use
The tool initializes with the current time. Enter a Unix timestamp (seconds) or use the date-time picker to select a date. Both inputs are bidirectional — changing one updates the other. Click "Now" to reset to the current time. Use copy buttons to copy any format.
What Is a Unix Timestamp
A Unix timestamp (also called epoch time) represents the number of seconds elapsed since January 1, 1970, 00:00:00 UTC (the Unix epoch). It is widely used in programming, databases, and APIs as a universal way to represent points in time. Negative values represent dates before 1970.
Use Cases
- API date handling — convert timestamps returned by REST or GraphQL APIs into human-readable dates
- Database timestamp debugging — translate Unix times stored in your database to real dates for data verification
- Log analysis — convert epoch times in server and application logs to readable dates for timeline analysis
- Cron job scheduling — convert specific dates to Unix timestamps for schedule configuration and conditional logic
Known Issues
- Y2K38 problem — 32-bit signed integers overflow at 2,147,483,647 (January 19, 2038), causing failures on legacy systems
- Seconds vs. milliseconds — JavaScript's Date.now() returns milliseconds, but the Unix standard uses seconds. A 1000x difference is easy to miss
- Timezone pitfalls — Unix timestamps are always UTC, but when converting to local time, verify that timezone offsets are applied correctly
Notable Timestamps
- 0 → 1970-01-01 00:00:00 UTC — the Unix epoch (origin)
- 1000000000 → 2001-09-09 01:46:40 UTC — the 1-billion-second milestone
- 1234567890 → 2009-02-13 23:31:30 UTC — the sequential timestamp
- 2000000000 → 2033-05-18 03:33:20 UTC — the 2-billion-second milestone
- 2147483647 → 2038-01-19 03:14:07 UTC — 32-bit signed integer maximum (Y2K38)
Privacy
All conversion happens entirely in your browser. No data is sent to any server.
FAQ
Is the Unix timestamp in seconds or milliseconds?
The Unix standard uses seconds, but JavaScript's Date.now() returns milliseconds. That is a 1000x difference. This tool treats input as seconds — divide your value by 1000 if it is in milliseconds.
What is the Year 2038 problem (Y2K38)?
Systems that store Unix timestamps as 32-bit signed integers overflow after 2038-01-19 03:14:07 UTC. Legacy C programs and older databases are at risk; the standard fix is moving to 64-bit timestamps.
Does the result change depending on my time zone?
The Unix timestamp itself is always UTC, so the number never changes. The tool also displays your browser's local time alongside UTC and ISO 8601 so you can see both and avoid timezone confusion.
Can I enter negative timestamps?
Yes. Negative values represent dates before 1970-01-01. For example, -1000000000 maps to 1938-04-25. Useful for historical data, old records, and date math around the epoch.
What is the difference between ISO 8601 and UTC?
UTC is Coordinated Universal Time — the time reference itself. ISO 8601 is an international standard for representing a moment in time as a string (e.g., 2024-01-15T12:34:56Z). The tool shows both.