Bidirectional conversion between timestamps and date time
Supported formats: YYYY-MM-DD HH:mm:ss, MM/DD/YYYY, DD/MM/YYYY, etc.
Professional timestamp conversion tool supporting various time format conversions
Easily convert between Unix/JavaScript timestamps and human-readable dates. Handles multiple formats and timezones in one place.
Bidirectional Conversion
Convert timestamps to dates and dates back to timestamps.
Multiple Format Support
Works with JavaScript milliseconds, Unix seconds, ISO 8601, and more.
Timezone Handling
Converts between local time and UTC automatically.
Custom Format
Define your own date-time output format.
Real-time Conversion
Results update as you type for a faster workflow.
Detailed Information
Shows year, month, day, hour, minute, second, and weekday at a glance.
Select conversion type: timestamp to date or date to timestamp
Enter timestamp or select date time
Choose custom format (optional)
Click convert button or wait for auto conversion
View conversion results and detailed information
Copy results to clipboard (optional)
A Unix timestamp is the number of seconds elapsed since 00:00:00 UTC on 1 January 1970, ignoring leap seconds. It is one integer, and it is the same integer everywhere on Earth at the same instant — which is precisely why databases and APIs store time this way.
Both qualifiers matter. It is UTC, not local time, so a timestamp carries no time zone of its own. And it skips leap seconds, so it is not strictly a count of physical seconds since 1970; the gap is around 27 seconds today and is deliberately ignored by almost everything.
The same instant appears as 1735689600 in seconds and 1735689600000 in milliseconds. Ten digits against thirteen. Pass a millisecond value to a function expecting seconds and you land some fifty thousand years in the future; go the other way and you land in 1970.
JavaScript is usually the culprit: Date.now() returns milliseconds, while most Unix documentation and most server-side languages count seconds. If a converted date looks absurd, count the digits before you debug anything else.
Because a timestamp is timezone-free, displaying it requires a zone to display it in. The same integer reads as 09:00 in Tokyo and 01:00 in Berlin. That is not a failure of the conversion — it is the conversion working, with the display making an assumption on your behalf.
This page renders in your device time zone. When you need the zone-free form, use the ISO string rather than the local rendering; the ISO form is the one that sorts correctly and compares correctly.
Systems that store Unix time in a signed 32-bit integer run out on 19 January 2038 at 03:14:07 UTC. The remedy is the same as it was for two-digit years — widen the field to 64 bits — and most modern systems have already done it, which is why the date will pass with far less alarm than 1999 did.
What remains is embedded hardware and long-lived formats: file systems, industrial controllers, anything with a fixed-width field nobody has revisited. Those are the places worth checking, not the web.
Nothing in the definition forbids negative numbers; they simply count backwards from the epoch. Minus 86400 is 31 December 1969. Some systems reject them anyway, usually because the field is unsigned, and that is worth knowing before you try to convert a historical date and get an error instead of a date.