Unix Timestamp Converter
Convert between a Unix timestamp and a readable date, live as you type.
Type in either field — the other updates live. The date field uses your browser's local timezone; the ISO 8601 output above is always UTC. Runs entirely in your browser.
Need the opposite? MongoDB ObjectId ↔ Timestamp Converter
What is Unix Timestamp Converter?
Type a Unix timestamp (seconds since January 1, 1970 UTC) and see the equivalent date instantly, or go the other direction by picking a date and time in the datetime field. Both fields update each other live as you edit either one. The page loads pre-filled with the current time, so you always have a working example to start from. Log files, database records, and API responses often store timestamps as raw Unix seconds, and converting one by hand is error-prone, so this comes up as a common debugging need. An ISO 8601 (UTC) representation is shown alongside the local-time field so you can compare the two directly without doing the timezone math yourself. Everything runs entirely in your browser; nothing you enter is sent to a server.
Common Unix Timestamps
| Unix Timestamp | UTC Date/Time |
|---|---|
| 0 | 1970-01-01T00:00:00Z |
| 946684800 | 2000-01-01T00:00:00Z |
| 1000000000 | 2001-09-09T01:46:40Z |
| 1577836800 | 2020-01-01T00:00:00Z |
| 1700000000 | 2023-11-14T22:13:20Z |
| 2147483647 | 2038-01-19T03:14:07Z |
How to Use the Unix Timestamp Converter
- 1
Enter a Timestamp or Pick a Date: Type a Unix timestamp in seconds, or set a date and time in the datetime field.
- 2
Read the Converted Result Instantly: The other field, plus a UTC ISO 8601 view, updates automatically as you edit either one.
- 3
Copy the Result: Use the copy button to copy whichever value you need.
What Is a Unix Timestamp
A Unix timestamp is the number of seconds that have elapsed since January 1, 1970, 00:00:00 UTC, known as the "Unix epoch." It's a single number representing an exact moment in time, independent of timezone or calendar formatting, which is why it's the standard way most databases, log files, and APIs store dates internally. The value 2147483647 (shown in the table above) is notable as the maximum value a signed 32-bit integer can hold. That's the source of the "Year 2038 problem" for systems that still store timestamps in 32 bits.
Seconds vs. Milliseconds
This is the most common source of confusion when working with timestamps: Unix time is traditionally measured in seconds, but many programming languages and APIs, JavaScript's Date.now() and most JSON APIs among them, use milliseconds instead. The difference is a factor of 1000. A seconds-based timestamp for a recent date is typically a 10-digit number (like 1700000000); a milliseconds-based one is 13 digits (like 1700000000000). If a timestamp you're converting produces a date far in the future or a date around 1970 when it shouldn't, check whether you need to divide by 1000 (milliseconds → seconds) or multiply by 1000 (seconds → milliseconds) first.
Frequently Asked Questions
Common questions about Unix Timestamp Converter.